IXG371E
ZAI LOGSTREAM CLIENT MANAGER UNAVAILABLE REASON: reason

Explanation

The z/OS® IBM zAware (ZAI) log stream client manager (controller task) is unavailable for the stated condition. It either could not be established or was established and then became unavailable.

In the message text:
reason
Is one of the following:
Start of changeZAI SERVER(NONE) SPECIFIED IN LOGGER PARMS.End of change
Start of changeLogger parameter specification ZAI SERVER(NONE) indicates no z/OS IBM zAware (ZAI) log stream client communications (re: IXGCNFxx parmlib).End of change
ZAI CLIENT ENVIRONMENT ERROR.
An error was encountered that impacted all the z/OS IBM zAware (ZAI) log stream clients on this z/OS image.
OMVS NOT INITIALIZED OR IS UNAVAILABLE.
OMVS has not been initialized or z/OS UNIX System Services (USS) are not available.
OMVS SEGMENT FAILURE FOR IXGLOGR.
System logger has determined the IXGLOGR address space does not have the appropriate security permission for z/OS UNIX System Services. The user security profile is either missing, incomplete, or the OMVS segment is not defined for the user.
OMVS BPX-SERVICE ERROR.
An error was encountered on a BPX-service request.
SETLOGR COMMAND REQUEST.
A ZAIQUIESCE,ALL request was issued on the SETLOGR FORCE command.

System action

System logger cannot establish or maintain z/OS IBM zAware log stream client connections with the IBM zAware server, so no log stream data can be sent to the IBM zAware server. The issue identified in the reason text of this message could mean that system logger will not be able to establish any z/OS IBM zAware log stream clients.

For the SETLOGR FORCE,ZAIQUIESCE,ALL request case, system logger has quiesced connection activity to the IBM zAware server for z/OS IBM zAware one or more log stream clients on the target z/OS image. See message IXG382I to identify the impacted log streams. These log streams will be marked as "QUIESCED", and will be disconnected from the IBM zAware server if connected. No z/OS IBM zAware log stream client data will be maintained for the log stream while in the quiesced (socket disconnected) state, meaning the buffers holding the log data for this purpose will be released (freed). In addition, the z/OS IBM zAware log stream client manager state will be set as "NOT AVAILABLE". Any log streams subsequently connected on this system with the ZAI=YES specification will also be placed in the "QUIESCED" state.

When the z/OS IBM zAware log stream client manager state changes to "AVAILABLE", as a result of a SETLOGR FORCE,ZAICONNECT command, then any log streams that are newly connected to the z/OS image with the ZAI=YES specification will be allowed to attempt z/OS IBM zAware log stream client connections with the IBM zAware server.

However, any log streams that were affected by the ZAIQUIESCE,ALL command will not be allowed to connect to the IBM zAware server until the appropriate SETLOGR FORCE,ZAICONNECT command is issued for these log stream(s), or the log stream is disconnected from the z/OS image and is then newly connected after the z/OS IBM zAware log stream client manager state has been set to "AVAILABLE".

Start of changeFor the ZAI SERVER(NONE) reason, message IXG371E is issued for operations awareness, then the message is immediately DOMed since this condition normally means not expecting communications with IBM zAware server on this system.End of change

Operator response

Notify the System Programmer.

System programmer response

Start of changeSee Preparing for z/OS IBM zAware log stream client usage in z/OS MVS Setting Up a Sysplex for more information on the z/OS IBM zAware log stream client.End of change

Do one of the following, depending on the text of this message:
  • Start of changeWhen the IBM zAware server location information is not specified in the logger parameters, either update the IXGCNFxx parmlib statement as needed or update the log stream definition to specify ZAI(NO).End of change
  • For a z/OS IBM zAware client environment error condition, check for related messages IXG373I, IXG382I and/or IXG384I, and make any necessary corrections.
  • When OMVS is not initialized or available, ensure OMVS is started.
  • When an OMVS segment failure occurred, fix the security profile and verify that IXGLOGR has permissions to an OMVS segment and the security product is running.
  • For a BPX-service error case, check for related error message IXG372I, and correct any error conditions.

Use the D LOGGER,IXGCNF[,ZAI] and D LOGGER,STatus,ZAI commands to display the details on the system logger view of the IBM zAware server and any potential z/OS IBM zAware log stream client socket connections.

You might need to check on the IBM zAware server level and location to be certain it is installed and running where expected. Ensure the IXGCNFxx parmlib member ZAI SERVER and PORT information correctly identifies the IBM zAware server location and that communication is allowed (such as sockets connections being allowed over any firewalls).

Then take action to get the desired z/OS IBM zAware log stream client connected, for example, see command SETLOGR FORCE,ZAICONNECT.

User response

None.

Programmer response

None.

Source

System logger (SCLOG)

Module

IXGWZACC

Routing code

2,10

Descriptor code

3