Can CA OPS/MVS record in the OPSLOG DIV VSAM files for processing via AOF rules the "early" NIP system messages produced at IPL?

Document ID : KB000027747
Last Modified Date : 14/02/2018
Show Technical Document Details

Introduction:

Prior to the Console Restructure in z/OS 1.4.2 (FMID JBB7727), in cases where CAOPS/MVS was started using the SUB=MSTR parameter and before the primary JES subsystem was started, the "early" messages would be extracted from the in-storage console buffers and recorded to the OPSLOG DIV VSAM file. With the Console Restructure, these buffers are no longer accessible. With APAR OA10401, IBM added a new dynamic exit, named CNZ_MSGTOSYSLOG, which is given control every time a message is written to the SYSLOG we are taking advantage of it. The PTFs in support of APAR OA10401 and the new exit are available for all z/OS systems at version 1.4.2 and above. By implementing this dynamic exit, CA OPS/MVS is once again able to make these "early" NIP messages available in the OPSLOG DIV VSAM file.

Answer:

If your z/OS operating system is at version 1.4.2 or higher and you have a supported release of CA OPS/MVS installed, perform the following steps to ensure that the "early" NIP system messages are recorded in the OPSLOG DIV VSAM file:

1.- Contact IBM and install all the applicable IBM PTFs for your version of z/OS as described in APAR OA10401.
2.- Make sure that SYSLOG is specified on the HARDCOPY DEVNUM statement in the active logical parmlib member CONSOLxx. For example:

HARDCOPY DEVNUM(SYSLOG)

3.- The CNZ_MSGTOSYSLOG exit is given control only when SYSLOG is active.

There are a number of differences between the "old" and "new" support for "early" NIP messages as far as OPSLOG is concerned:

Prior to z/OS 1.4.2 z/OS 1.4.2 (or higher) with APAR OA10401
"Early" messages appear in OPSLOG soon after Unicenter CA-OPS/MVS starts."Early" messages appear in the OPSLOG after the primary JES is started and SYSLOG processing starts.
Look for these "early" messages in the OPSLOG following the message:
IEE041I THE SYSTEM LOG IS NOW ACTIVE
All "early" messages have a message ID of NIPMSG."Early" messages have "normal" message IDs, which are extracted from the message text.
The values in the DATE and TIME columns are the same for all "early" messages and are the date and time that the message extraction process started.The DATE and TIME columns indicate the date and time each message is processed by the Unicenter CA-OPS/MVS CNZ_MSGTOSYSLOG exit.
The "early" messages contain partial information.The "early" messages contain complete information.

The following have not changed:

  1. You can still identify a NIP message by looking at the EXITTYPE column in OPSLOG, which still contains the text string NIP.
  2. The TIMESTMP column indicates the original time the NIP message was issued. Expect the TIMESTMP value to be earlier than the value in the TIME column.

Note that once the early messages have been processed, there is no need for CA OPS/MVS to keep the CNZ_MSGTOSYSLOG exit active. Sometime soon after these messages have been processed you will see the following message:

OPS0310I DYNAMIC EXIT MODULE OPMVSLEX DELETED FROM EXIT POINT CNZ_MSGTOSYSLOG

This indicates that the dynamic exit has been deleted.

One of the advantages of processing these "early" messages after CA OPS/MVS has been initialized is that it is possible to write AOF message rules to process these "early" NIP message events. CA OPS/MVS parameter AOFNIPMESSAGES allows you to specify whether or not the NIP "early" messages should be processed by AOF message rules. These messages will be processed asynchronously to their issuance making you able to detect that condition programmatically in the SOF rules.

Additional Information:

You can find additional information at our website: CA Technologies Documentation