The Adabas nucleus reflects dynamic changes made in the operating system to the local time zone (relative to machine or STCK time) without being shut down and restarted. The change becomes effective when the next operator command is issued from the console.
Although this applies to all mainframe platforms, a local time zone change on VM/ESA ore VSE/ESA is still reflected only after a shut down and restart of the Adabas nucleus.
This document covers the following topics:
Time stamps on WORK and PLOG are in machine time rather than local time. This means that:
Time stamps passed to user exit 2 as the second and third parameters are in machine time rather than local time. User exits that display the time stamps on the console or otherwise process the time stamps are thus affected.
Note:
The sample user exit 2 delivered by Software AG does not
display or otherwise process these time stamps.
Time stamps in PLOG records written WITH LOGINFO by the ADASEL utility to a DDEXPAn (or EXPAn) output data set are in machine time rather than local time.
All other time stamps in Adabas data sets (for example, in save data sets, checkpoints, FCBs, the CLOG) are in local time.
To activate the local time zone change:
Change the local time zone in the operating system.
On z/OS and BS2000 systems, issue any command (for example DSTAT) from the operator console to the Adabas nucleus.
Notes:
On VM/ESA ore VSE/ESA systems, shut down and restart the Adabas nucleus.
