Version 7.4.4
 —  Operations  —

Local Time Zone Change Support

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 Stamp Overview

Time stamps on WORK and PLOG are in machine time rather than local time. This means that:

Top of page

Activating the Local Time Zone Change

Start of instruction setTo activate the local time zone change:

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

  2. On z/OS and BS2000 systems, 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.
  3. On VM/ESA ore VSE/ESA systems, shut down and restart the Adabas nucleus.

Top of page