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.

This document covers the following topics:

• Time Stamp Overview

• Activating the Local Time Zone Change

---

Time Stamp Overview

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.

Activating the Local Time Zone Change

To activate the local time zone change:

1. Change the local time zone in the operating system.

2. On z/OS, issue any command (for example DSTAT) from the operator console to the Adabas nucleus.

   Notes:

   1. The ADADBS OPERCOM function may not be used to activate the local time zone change. The command must be issued from the operator console.
   2. If commands were being logged on the CLOG when the local time zone was changed, Software AG recommends that you use the FEOFCL command from the operator console to activate the change. In this way, the same dual CLOG will not contain time stamps from before the change as well as after its activation.