Compliance Manager alert messages resolve %TIME%, %TIME_SYSTEM%, and %TIME_UTC% variables to the incorrect values with time zone

Products

• Compliance Manager for z/OS

Issue/Introduction

Compliance Manager alert messages resolve %TIME%, %TIME_SYSTEM%, and %TIME_UTC% variables to incorrect values for your time zone. How do you fix this?

 

Resolution

The Compliance Manager Monitor and Alert component alert messages provide variables that a site 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. A site can specify either %TIME% or %TIME_UTC% to get the UTC timestamp for the event; or, specify %TIME_SYSTEM% to get the system’s (local) timestamp for the event.  

Incorrect timestamps may been seen on 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 timestamp should be 18:48:42 and 13:48:42, respectively.

This error occurs because a CEEOPTS DD statement is not supplied, the time conversion routines may not process the timestamp correctly for your time zone. To resolve this issue, follow these steps:

1. Add the following DD statements to your Compliance Manager Alert and Monitor component started tasks:
   
   //CEEOPTS   DD   DISP=SHR,DSN=YOUR.PARMLIB(CMGRCEEO)
   //CEEVARS   DD   DISP=SHR,DSN=YOUR.PARMLIB(CMGRCEEV)
   
   
2. Change “YOUR.PARMLIB” to the parameter library.  This value can be the same library that you use for the SYSIN statements in your procs.
   
   
3. Add the CMGRCEEO and CMGRCEEV members to the parameter library that you specified for YOUR.PARMLIB.
   
   
4. Add the following lines to the CMGRCEEO member:
   
   TRAP(OFF),POSIX(ON)
   ENVAR(“_CEE_ENVFILE_S=DD:CEEVARS”)
   
   

Add the following lines to the CMGRCEEV member:

* AXIS2C_CERT_KEYFILE=yourKEYRINGPATH/keyring.file
* AXIS2C_CERT_LABEL=yourLABEL                         

1.    * AXIS2C_CERT_PASSWRD=yourPASS                        
   * GSK_TRACE=0xffff                                    
   * GSK_TRACE_FILE=/your/trace/directory/file.name      
   * CMGR_TRACE_MODULES=NONE                             
   * CMGR_TRACE_EVENTS=NONE                              
   
   Do not modify these lines unless:

• • If implementing SSL for Chorus for Security and Compliance Management discipline; then, only modify the AXIS2C lines.
  • If instructed by Broadcom Support to turn on tracing options; then, only modify the lines as instructed by Broadcom Support.

2. Verify that the system’s /etc/profile global profile script has the appropriate time zone set.

3. Restart the Alert and Monitor started tasks.

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