Attribute definitions
Three attributes facilitate timing services.
- Time Zone
- CICSPlex SM uses
the international standard for time zones. This consists of 24 zones
around the world, separated in time by 60 minutes each. The standard
for these zones is the prime meridian, and time at the prime meridian
is referred to as Greenwich Mean Time (GMT).
The area having Greenwich Mean Time is referred to as time zone Z. The next time zone to the east, where time is 60 minutes (one hour) ahead of GMT, is time zone B. When GMT is 12:00 noon, the time in time-zone B is 13:00. The next time zone to the east, 120 minutes (two hours) ahead of GMT, is time zone C. For each time zone to the east, time advances one hour, until time zone M, where local time is 12 hours ahead of GMT. Time zone M is at the international date line.
The next time zone east, time zone N, is (like time zone M) separated from GMT by 12 hours. However, because it is considered to be on the opposite side of the international date line from time zone M, it is 12 hours behind GMT. Similarly, the next time zone east, time zone O, is 11 hours behind GMT. When GMT is 12:00 noon, the time in time zone O is 01:00. For each time zone to the east, one hour is subtracted, until time zone Y, which is one hour behind GMT.
Note that there is no time zone A.
- Time Zone Adjustment
- Some locations around the world have implemented times that are different from GMT by times that are not 60 minute multiples. For situations such as these, CICSPlex SM uses a time zone adjustment. To define the time zone of such a location to CICSPlex SM, the time zone of the next lowest 60 minute multiple is used, and the difference, in minutes, between the 60 minute multiple and the location's time is entered as the Time Zone Adjustment. For example, when the time is 13:00 in London, England (this is GMT, or time zone Z), it is 22:00 in Tokyo, Japan (time zone J), and 22:30 in Adelaide, Australia. To define Adelaide's location to CICSPlex SM, the time zone is specified as time zone J, and the time zone adjustment is specified as 30 (to indicate that the time in Adelaide has 30 minutes added to the time in the adjacent time zone to the west).
- Daylight saving
- Some locations around the world modify their time offset from
GMT twice a year. Usually, the first change occurs in March or April,
when local standard time (LST) is moved ahead by one hour,
creating local daylight saving time (LDST). For locations in time
zones Z through M, LDST is one hour farther ahead of GMT. For locations
in time zones N through Y, LDST is one hour closer to GMT. In October
or November, locations that use LDST usually change back to LST. Time
in these locations then reverts to the standard difference from GMT.
For operation of CICSPlex SM, sites in locations that make use of LDST must modify all CMASs and MASs twice a year. This means indicating YES to daylight saving when LDST is in effect, and NO when LST is in effect. When the daylight saving indicator is NO, CICSPlex SM considers an entity in that time zone to be the normal number of hours from GMT. When the daylight saving indicator is YES, CICSPlex SM considers that entity to be one hour further ahead of GMT (than during standard time) for time zones Z through M, and one hour closer to GMT for time zones N through Y.
To change the LDST for a CMAS, set the DAYLIGHT attribute in the CMAS operation resource table. This change updates the current execution of the CMAS and is propagated to the CMASDEF definition resource table for the CMAS so that the LDST change is effective on subsequent restarts of the CMAS.
If a MAS inherits the time zone attributes from its controlling CMAS, that is, the TMEZONE, TMEZONEO, and DAYLGHTSV attributes in the CSYSDEF definition resource table for the MAS specify INHERIT, the LDST for a MAS is automatically updated when the LDST is updated for the CMAS to which the MAS is connected. Otherwise, you must update the LDST for the MAS.
To change the LDST for a MAS, set the DAYLGHTSV attribute in the CSYSDEF definition resource table. This change takes effect the next time the CICS region or the MAS agent in the CICS region is restarted, and is effective for all subsequent restarts. If a MAS is active when its CSYSDEF definition resource table is updated, the CSYSDEF change is not effective on the active MAS. If you want to change the LDST for an active MAS without restart, you must set the DAYLGHTSV attribute in the MAS operation resource table.
For details, see Handling daylight saving time changes for CMAS.
Note: After changing the system time to adjust for LDST, all CMAS must synchronize with the change. If the CICS system initialization parameter AUTORESETTIME takes the default value IMMEDIATE or is set to IMMEDIATE, the synchronization automatically takes place when the next task is attached in the CMAS. Otherwise, you need to issue the PERFORM RESETTIME command in the CMAS. For more information about the AUTORESETTIME parameter, see Effect of daylight saving time changes.