OPSVIEW OPSLOG Option › Overview of the OPSVIEW OPSLOG Option (Option 1) › The OPSLOG and Early Messages
The OPSLOG and Early Messages
When CA OPS/MVS is started through SUB=MSTR before JES is started, the early messages-including NIP messages-are copied into the OPSLOG to provide a more complete log of events.
Prior to z/OS 1.4.2, the following applies:
- NIP messages do not execute AOF rules.
- NIP messages may not be available on systems that use OPERLOG as the hard copy medium, since they are purged before CA OPS/MVS can copy them.
- NIP messages are identified in the OPSLOG with a unique exit type of NIP, and the character string NIPMSG always appears in the message ID column. Since NIP messages are captured after they were actually issued, some related data columns in the OPSLOG might not contain valid data.
For z/OS operating environments 1.4.2 and higher that have applied the required fixes to support APAR OA10401, the following applies:
- The AOFNIPMESSAGES parameter determines whether NIP messages can execute AOF rules.
- After the primary JES has started and SYSLOG processing is active, NIP messages appear in the OPSLOG as standard messages.
- NIP messages are identified in the OPSLOG with a unique exit type of NIP.
Note: You cannot capture NIP messages if you have not applied the required fixes for your operating environment to support APAR OA10401.
