Understanding system time

The system time can be changed while CICS® Transaction Gateway is running. If you do this, active processes respond to the changed time and not to the elapsed time.

When setting clocks forward or back, the behavior of timeout settings will change. When the clock is set back the elapsed time for a timeout might be increased. When the clock is set forward a timeout might expire earlier. The maximum elapsed time for a timeout will be the original timeout value plus the value of the change in time. For example, if the current time is 19:00, and a timeout is set to expire 5 minutes from now; the effect of setting the clock back by 1 hour is to increase the value of the timeout by 1 hour. The total elapsed time for the timeout is 1 hour and 5 minutes.

The following timeouts are effected by this change:
  • Gateway daemon close
  • Gateway daemon idle
  • Gateway daemon ping
  • Server idle times
  • Worker thread available thread
Note: Absolute times provided by the statistics APIs and request monitoring exits, and timestamps written to logs and traces, are obtained from the operating system.