ASG-TMON™
Notes on Time Change



Considerations and Possible Procedures Regarding TCP/IP (Communications Server for Z/OS) and ASG-TMON for TCP/IP when Changing the GMT Adjustment Factor

There are two groups of common scenarios based on setting the GMT adjustment factor forward or backward.

Setting the GMT adjustment factor forward (Standard Time):

Case 1: I cannot recycle either TCP/IP or ASG-TMON for TCP/IP
  1. Disconnect ASG-TMON for TCP/IP from all monitored hosts, using the DIS (disconnect) line command on Option 8.3..
  2. Set Clock forward
  3. Reconnect ASG-TMON for TCP/IP to all monitored hosts, using the CON (connect) line command on Option 8.3.


    4. Data Considerations: No data considerations.
Case 2: I cannot recycle TCP/IP; I will recycle ASG-TMON for TCP/IP
  1. Stop ASG-TMON for TCP/IP and LFS
  2. Set Clock forward
  3. Start ASG-TMON for TCP/IP and LFS


    4. Data Considerations: No data considerations.
Case 3: I will recycle TCP/IP; I cannot recycle ASG-TMON for TCP/IP
  1. Shutdown the TCP/IP address space(s)..
  2. Set Clock forward.
  3. Startup TCP/IP address space(s).


    4. Data Considerations: No data considerations.
Case 4: I will recycle both TCP/IP and ASG-TMON for TCP/IP
  1. Shutdown the TCP/IP address space(s).
  2. Shutdown ASG-TMON for TCP/IP.
  3. Set Clock forward
  4. Start TCP/IP.
  5. Start ASG TMON for TCP/IP.


    6. Data Considerations: No data considerations.
Setting the GMT adjustment factor backward (Daylight Saving Time):

Case 1: I cannot recycle either TCP/IP or ASG-TMON for TCP/IP
  1. Disconnect ASG-TMON for TCP/IP from all monitored hosts, using the DIS (disconnect) line command on Option 8.3.
  2. Set Clock backward.
  3. If possible, wait until no time overlap exists before reconnecting to the monitored hosts, using the CON (connect) line command on Option 8.3.


    4. Data Considerations: If you reconnect to the hosts with a time overlap then you may have invalid summary data for this time interval. Also batch reports from Report Writer may show increased in statistics for a particular hour if collection of data started immediately after setting the clock backward.
Case 2: I cannot to recycle TCP/IP; I will recycle ASG-TMON for TCP/IP
  1. Stop ASG-TMON for TCP/IP and LFS.
  2. Set Clock backward.
  3. If possible, wait until no time overlap exists.
  4. Start ASG-TMON for TCP/IP and LFS.


    5. Data Considerations: If you restart ASG-TMON for TCP/IP and LFS with a time overlap then you may have invalid summary data for this time interval. Also batch reports from Report Writer may show increased in statistics for a particular hour if collection of data started immediately after setting the clock backward.
Case 3: I will recycle TCP/IP; I cannot recycle ASG-TMON for TCP/IP
  1. Shutdown the TCP/IP address space(s).
  2. Set Clock backward.
  3. If possible, wait until no time overlap exists.
  4. Start the TCP/IP address space(s).


    5. Data Considerations: If you restart the TCP/IP address space(s) with a time overlap then you may have invalid summary data for this time interval. Also batch reports from Report Writer may show increased in statistics for a particular hour if collection of data started immediately after setting the clock backward.
Case 4: I will recycle both TCP/IP and ASG-TMON for TCP/IP
  1. Shutdown the TCP/IP address space(s).
  2. Shutdown ASG-TMON for TCP/IP and LFS.
  3. Set Clock backward.
  4. If possible, wait until no time overlap exists.
  5. Start the TCP/IP address space(s).
  6. Start ASG TMON for TCP/IP and LFS.


    7. Data Considerations: If you restart ASG-TMON for TCP/IP and LFS with a time overlap then you may have invalid summary data for this time interval. Also batch reports from Report Writer may show increased in statistics for a particular hour if collection of data started immediately after setting the clock backward.
For more information on Adjusting the System Clock, please review Chapter 5 of the System Administrator's Guide