Resolution:
PROBLEM:

Will TIBCO Object Service Broker for z/OS (OSB) Journal timestamps be affected by Daylight Saving Time switch?


ENVIRONMENT:

TIBCO Object Service Broker for z/OS (OSB) usage in locations that observe Daylight Saving Time


SOLUTION:    
    
For spring, when the clocks go 1-hour ahead, there is nothing that is an issue for OSB.
                                                                                                
Daylight savings time only causes a problem when you are using LOCAL timestamping and revert back to standard time in the fall.  
If you are using LOCAL timestamping on journal records, then you should shut down OSB for 1 hour  when you revert back to standard time; otherwise, when you sort and consolidate your journal records for continuous backup, you could be ending up with an invalid backup since images could sort out of chronological sequence. This would be a problem if you had to use the continuous backup for a restore.                                                                                                            
This problem is eliminated in OSB 4.1.0 (GA) and later releases as you can define your journal timestamp as OFFSET=UTC. The default however remains LOCAL.  When you specify OFFSET=UTC, all timestamps are in UTC format and are, therefore, monotonically increasing regardless of local daylight saving or standard time.

Please review section DBGEN in the "TIBCO Object Service Broker for z/OS Installation and Operations" manual, for further information on OFFSET parameter.