Compliance Manager alert messages resolve %TIME%, %TIME_SYSTEM%, and %TIME_UTC% variables to the incorrect values for my time zone; how do I fix this?

Article Id:33650

Status:Published

Updated On:14-02-2018 08:20

Legacy Id:TEC1976828

Products:

CA Compliance Manager for z/OS

Issue/Introduction:

Problem:

Compliance Manager alert messages resolve %TIME%, %TIME_SYSTEM%, and %TIME_UTC% variables to the incorrect values for my time zone; how do I fix this?

Symptoms:

The CA Compliance Manager Monitor and Alert component alert messages provide variables that you can supply to substitute certain information about the event into the alert message. One of these variables is the timestamp for when the event occurred. You can specify either %TIME% or %TIME_UTC% to get the UTC timestamp for the event; or, you can specify %TIME_SYSTEM% to get the system’s (local) timestamp for the event.

You might see incorrect timestamps on your alerts. For example, an event that occurs at 13:48:42 Eastern (UTC-5) might display the UTC time as 13:48:42 and the local time as 08:48:42 when the timeshtap should be 18:48:42 and 13:48:42, respectively.

This error occurs because if you do not supply a CEEOPTS DD statement, the time conversion routines may not process the timestamp correctly for your time zone.

Resolution:

To resolve this issue, follow these steps:

1.Add the following DD statements to your CA Compliance Manager Alert and Monitor component started tasks:

After you complete these steps, CA Compliance Manager alert message processing will use the time zone environment variable set in your /etc/profile global profile script when it performs timestamp conversions.