ZONE

The syntax is ZONE(n) or ZONE=n.

This provides a way to override your local CPU time zone setting and convert CMF, DB2®, MQ, and System Logger clock fields to a different time zone. It is only useful if the data you are reporting was generated by a system running with a different time zone.

CMF, DB2, MQ, and Logger records have clock fields in STCK format based on Greenwich Mean Time (GMT). CMF records have conversion factors that enable the clock fields to be converted to local time. However, if you are running the DB2, MQ, or System Logger reports against records from a system with a different time zone, then you must specify the time zone option.

Specify the time zone as an integer from -12 to +12 to represent the number of hours that local time is west or east of GMT. For example, specify -5 for New York, 10 for Sydney. CICS PA will then convert GMT STCK values to the required local time for all record types.

CICS PA JCL generation translates this field to the ZONE operand.

The default is blank (not specified). In this case, when the time zone is not specified, CICS PA does the following:
  • For CMF records, the conversion factors SMFMNLSO (Leap Second Offset) and SMFMNDTO (Date/Time Offset) in the CMF record are used.
  • For DB2, MQ, and Logger records, the conversion factors CVTLSO (Leap Second Offset) and CVTLDTO (Date/Time Offset) in the CVT are used, that is, the reporting system's time zone is used.
Example 1:
CICSPA ZONE(-5),
       LIST,
       SUMMARY
This example shows ZONE applied to multiple reports. Both the Performance List and Performance Summary reports are produced as if the input data came from the zone 5 hours west of GMT (for example, Toronto, New York, Lima).
Example 2:
CICSPA ZONE(8),
       LIST,
       SUMMARY
Both the Performance List and Performance Summary reports are produced as if the input data came from the zone 8 hours east of GMT (for example, Singapore, Perth).