CSL OM audit trail

An OM audit trail reflects the input and output of commands that are processed through the OM API. You can log: a point of command origin, what a particular command processed, and the result of that processing.

OM can write log records to a z/OS® System Logger log stream, creating an audit trail of command input, associated command output, and unsolicited message output. Before using the OM audit trail function, the log stream needs to be created. Definitions for z/OS System Logger and coupling facility structures are required. To write OM log records to a z/OS log stream, specify the AUDITLOG= parameter of the IMSPLEX() keyword on the CSLOIxxx PROCLIB member.

In the following scenarios, no data is lost in the OM audit trail when the log stream becomes available because OM logs its work:

• If the connection to the log stream fails at startup, the initialization continues. Connection is set up after the log stream becomes available.
• If writing to the log stream fails for OM, OM waits for the log stream to become available and performs the writing process again.

If an individual command or command response plus its associated control data is longer than 32,760 bytes, it is split across multiple log records. These log records include control data that log formatting utilities can use to reassemble the log records into a single command or command response.