The z/OS® IBM zAware (ZAI) log stream client manager was unable to send to the IBM zAware server all the intended log stream data. Logger used all the storage available for buffering the data. The amount of storage available for buffers is provided on the logger ZAI LOGBUFMAX policy specification in parmlib member IXGCNFxx. Also see message IXG375E, which was issued prior to IXG376E.
System logger will take the action as indicated in the ZAI LOGBUFFULL parmlib policy specification.
When the LOGBUFFULL designation is "MSG", then logger continues processing the log data for one or more z/OS IBM zAware log stream clients. However, each z/OS IBM zAware log stream client will keep a count of the number of log blocks (one per IXGWRITE request) for that log stream. When the buffer full condition clears, message IXG383I will be issued indicating the number of skipped log blocks.
When the LOGBUFFULL designation is "QUIESCE", then logger stops processing the log data for one or more z/OS IBM zAware log stream clients by quiescing (disconnecting) all the z/OS IBM zAware log stream client connections from the IBM zAware server. The socket connection will remain disconnected until either a SETLOGR comand (for example, SETLOGR FORCE,ZAICONNECT,ALL) or SET IXGCNF command that has specifications to connect to the IBM zAware server. No z/OS IBM zAware log stream client data will be maintained while in the quiesced state, meaning the buffers holding the log data for this purpose will be released (freed).
Notify the System Programmer.
Verify the z/OS IBM zAware log stream client status is as expected using the D LOGGER,STatus,ZAI and D LOGGER,IXGCNF,ZAI commands. Check for messages IXG371E and IXG372I or other related z/OS IBM zAware client messages and make any necessary corrections if necessary.
None.
None.
System logger (SCLOG)
IXGF2WRT, IXGWZACC
2,10
3