Explanation
System logger was unable to complete
the initial socket connection to the IBM zAware for a z/OS® IBM zAware log stream
client, but will retry periodically. All the required services to
establish the socket connection are not yet available (initialized)
or there may be network issues preventing the connection from completing.
- When "OMVS" is included in the message text, the condition can occur following a system IPL or restart of system logger address space, and when OMVS has not yet fully initialized.
- When "TCPIP OR NETWORK FLOW" is included in the message text, TCPIP might not have completed initialization. Or the successful socket connection could be inhibited by a network issue or from network congestion.
- logstream
- Identifies the log stream name.
- service
- One of the following:
- OMVS
- TCPIP OR NETWORK FLOW
System action
System logger continues retrying to establish the socket connection to the IBM zAware server for a period of time.
- When "OMVS" is included in the message text, the retry period
will continue until the logger IXGCNFxx parameter options LOGBUFMAX
and LOGBUFFULL come into effect. When the buffers become full:
- and LOGBUFFULL(QUIESCE) is specified, then system logger will quiesce the zai client at that point.
- and LOGBUFFULL(MSG) is specified (or defaulted), then system logger will continue retrying for an additional period. If a successful socket connection does not occur after 20 more minutes, the zai client will be quiesced.
- When "TCPIP OR NETWORK FLOW" is included in the message text, system logger periodically continues retrying to establish the socket connection for approximately 20 minutes after the initial issuance of message IXG385I for this condition.
During the retry periods, when log data is
written to the specified log stream, system logger will buffer the
log data for this z/OS IBM zAware log stream
client. If a successful socket connection is established with the IBM zAware server,
then logger will cause the buffered log data to be sent to the IBM zAware server
for analysis. For additional information, refer to system logger message
IXG380I.
If after the retry period expires and
a successful socket connection did not occur, then the z/OS IBM zAware log stream
client could not be established and the buffered log data is discarded
since the zai client is quiesced. Refer to messages IXG382I and IXG384I.
Operator response
Notify the System Programmer.
System programmer response
Ensure OMVS, z/OS Communication Server and TCPIP services are initialized and available on the system. Verify the z/OS IBM zAware log stream client status and logger parameters are as expected using the D LOGGER,Status,ZAI and D LOGGER,IXGCNF,ZAI commands.
Check for messages IXG380I, IXG382I or IXG384I and IXG372I , and take any necessary actions.
When "TCPIP OR NETWORK FLOW" is included in the message
text, confirm the IXGCNFxx SERVER and PORT values correctly specify
the IBM zAware location.
Verify the network communications between the z/OS image and the IBM zAware server
location.
User response
None.
Programmer response
None.
Source
System logger (SCLOG)
Module
IXGWZASC
Routing code
2,10
Descriptor code
4