|
|
|
Reason:
This message is issued as a message ID for all responses to commands issued through the LXCMD interface.
System Action:
None.
User Action:
None.
Reason:
This message is issued as a message ID for all error responses to commands issued through the LXCMD interface.
System Action:
None.
User Action:
None.
Reason:
When you issue an LXCMD command to a Linux system, you must identify the system with the following parameter: ADDR=ip_address or NAME=name, and optionally NODE=vm_host.
System Action:
The command is rejected.
User Action:
Correct and retry the command.
Reason:
A command was issued to the Linux system, but the system was not registered with Linux Connector.
P1 identifies the Linux system.
System Action:
The command is rejected.
User Action:
Wait until the Linux system has connected, and retry the command.
Reason:
The LXCMD command is invoked with WRITEPARM=YES.
P1 is the parameter string passed to the COMMANDS server from the Linux agent upon connection.
System Action:
None.
User Action:
None.
Reason:
An LXCMD command was issued without the CMD= parameter.
System Action:
The command is rejected.
User Action:
Correct and retry the command.
Reason:
The COMMANDS server for a client was terminated by the client.
P1 identifies the client.
System Action:
The server terminates.
User Action:
None.
Reason:
A connection to the COMMANDS server for a Linux system did not receive the standard parameter string that is part of the protocol for connecting to the Linux agent running on that system.
P1 identifies the Linux system where a Linux agent is running.
System Action:
The connection is terminated.
User Action:
Ensure that the Linux agent has been installed and configured correctly.
For assistance, contact CA Support.
Reason:
A connection to the COMMANDS server for a Linux system received an unexpected record type for P2.
P1 identifies the Linux system.
P2 is either a parameter string or the shell prompt.
P3 (optional) provides more information.
System Action:
The message is ignored.
User Action:
None.
Reason:
A connection to the COMMANDS server for a Linux system timed out while waiting for the shell prompt.
P1 identifies the Linux system.
System Action:
The connection is terminated.
User Action:
None.
Reason:
This message is the last response to commands issued through the LXCMD interface.
System Action:
None.
User Action:
None.
Reason:
This message is a normalized unsolicited message from a z/VM agent.
P1 identifies the z/VM system.
P2 is the user ID.
P3 is the event type.
P4 is the event class.
P5 is the event data.
System Action:
None.
User Action:
None.
Reason:
The Linux Connector has begun initializing.
System Action:
Linux Connector initialization continues.
User Action:
None.
Reason:
The Linux Connector initialization has reached a status of p1, which has the following possible values:
System Action:
Linux Connector initialization continues to the next stage.
User Action:
None.
Reason:
The Linux Connector initialization has ended.
System Action:
Linux Connector initialization has finished.
User Action:
None.
Reason:
This Linux Connector region has started a Telnet Server.
p1 is the server IP address.
p2 is the server port number.
System Action:
Linux Connector region initialization continues.
User Action:
None.
Reason:
The Linux Connector has detected an invalid parameter name-value pair in its parmlib.
System Action:
The Linux Connector terminates. All parameters must be valid.
User Action:
Correct the erroneous parameter name-value pairs, and restart the Linux Connector.
Reason:
The Linux Connector could not start a Telnet server.
System Action:
The Linux Connector region initialization continues, but no Telnet access is available.
User Action:
None.
Reason:
Linux Connector initialization has determined that a required value is not specified.
Stack Type must be specified. The value must be one of IBM, IBMV4, IBMV6, or TCPAXS.
If Stack Type is IBM*, then Stack Name must be specified and must be the name of a running TCP/IP stack.
If Stack Type is TCPAXS, then Stack SSID must be specified.
System Action:
The Linux Connector terminates.
User Action:
Specify valid values for STACKTYPE, and STACKNAME or STACKSSID in the Linux Connector LNXPARMS member, and restart the Linux Connector.
Reason:
The Linux Connector initialization has not been able to start its TCP/IP interface. The most likely cause is that the TCP/IP stack is not running. The Linux Connector will regularly retry the start command.
System Action:
The Linux Connector regularly retries the TCP/IP start command.
User Action:
Reason:
The Linux Connector initialization is documenting its TCP/IP parameters.
System Action:
Linux Connector initialization continues.
User Action:
None.
Reason:
The Linux Connector encountered an error while trying to load its parameters. The Linux Connector cannot proceed with invalid or no parameters.
System Action:
The Linux Connector will terminate. All parameters must be valid.
User Action:
Reason:
The Linux Connector has encountered a duplicate parameter specification in its parmlib. The later value overrides the earlier value.
System Action:
The Linux Connector overrides the earlier value specified with the later value.
User Action:
Edit your Linux Connector parmlib and remove all duplicate parameters before restarting the Linux Connector.
Reason:
The data set allocated to the SYSTCPD ddname is not valid. The data set allocated to this ddname must be the name of the TCPIP.DATA data set used for the z/OS Communications Server. This name is found in the SYSTCPD DD statement of the stack started task JCL member.
p1 can be one of the following values:
Indicates that a partitioned data set was allocated to SYSTCPD but a member name was not specified. A member name must be specified when SYSTCPD is allocated as a partitioned data set, for example:
//SYSTCPD DISP=SHR,DSN=TCPIP.DATA(TCPIP1)
Indicates that the data set allocated to SYSTCPD is not of the PS (physical sequential) organization. The data set allocated to SYSTCPD must be have a data set organization of PS (or PO if a member is specified).
Is the error message returned while attempting to access the SYSTCPD data set. Review the online help for this specific error message.
System Action:
The Linux Connector terminates.
User Action:
Change the data set name specified for the SYSTCPD ddname in the Linux Connector JCL member to the same data set name specified for the SYSTCPD ddname in the z/OS Communications Server stack started task JCL member. Ensure that the correct member name is also specified if the data set is a partitioned data set (the member must also match that specified in the started task JCL member for the stack).
Reason:
The Linux Connector is documenting its initialization parameters.
System Action:
The Linux Connector continues initializing.
User Action:
None.
Reason:
Linux Connector attempted to read its initialization parameters from the parmlib member but no data was returned.
System Action:
Linux Connector terminates because it cannot continue initializing with no parameters.
User Action:
Reason:
This message is a normalized unsolicited alert message from a Linux syslog daemon.
p1 identifies the Linux system.
p2 identifies the hosting z/VM system.
p3 is the message text appended by the Linux facility and timestamp in the following format: message_text { facility mmm-dd hh:mm:ss }
System Action:
None.
User Action:
None.
Reason:
This message is a normalized unsolicited critical message from a Linux syslog daemon.
p1 identifies the Linux system.
p2 identifies the hosting z/VM system.
p3 is the message text appended by the Linux facility and timestamp in the following format: message_text { facility mmm-dd hh:mm:ss }
System Action:
None.
User Action:
None.
Reason:
This message is a normalized unsolicited debug message from a Linux syslog daemon.
p1 identifies the Linux system.
p2 identifies the hosting z/VM system.
p3 is the message text appended by the Linux facility and timestamp in the following format: message_text { facility mmm-dd hh:mm:ss }
System Action:
None.
User Action:
None.
Reason:
This message is a normalized unsolicited error message from a Linux syslog daemon.
p1 identifies the Linux system.
p2 identifies the hosting z/VM system.
p3 is the message text appended by the Linux facility and timestamp in the following format: message_text { facility mmm-dd hh:mm:ss }
System Action:
None.
User Action:
None.
Reason:
This message is a normalized unsolicited informational message from a Linux syslog daemon.
p1 identifies the Linux system.
p2 identifies the hosting z/VM system.
p3 is the message text appended by the Linux facility and timestamp in the following format: message_text { facility mmm-dd hh:mm:ss }
System Action:
None.
User Action:
None.
Reason:
This message is a normalized unsolicited emergency message from a Linux syslog daemon.
p1 identifies the Linux system.
p2 identifies the hosting z/VM system.
p3 is the message text appended by the Linux facility and timestamp in the following format: message_text { facility mmm-dd hh:mm:ss }
System Action:
None.
User Action:
None.
Reason:
This message is a normalized unsolicited notice message from a Linux syslog daemon.
p1 identifies the Linux system.
p2 identifies the hosting z/VM system.
p3 is the message text appended by the Linux facility and timestamp in the following format: message_text { facility mmm-dd hh:mm:ss }
System Action:
None.
User Action:
None.
Reason:
This message is a normalized unsolicited warning message from a Linux syslog daemon.
p1 identifies the Linux system.
p2 identifies the hosting z/VM system.
p3 is the message text appended by the Linux facility and timestamp in the following format: message_text { facility mmm-dd hh:mm:ss }
System Action:
None.
User Action:
None.
Reason:
The syslog-ng daemon issued a command through LXCMD but did not receive the expected message.
P1 is the expected message.
P2 is the received message.
System Action:
The specific connection is closed.
User Action:
Check the log for other errors.
For assistance, contact CA Support.
Reason:
A connection to the syslog-ng daemon on a Linux system was terminated by the daemon.
p1 identifies the Linux system.
System Action:
None.
User Action:
None.
Reason:
The SYSLOGNG server for a Linux system encountered a problem while waiting for system activity.
p1 identifies the Linux system.
p2 is the system feedback.
p3 is the error message if available.
System Action:
The server terminates. The syslog-ng daemon retries the connection and processing should continue as normal.
User Action:
For assistance, contact CA Support.
Reason:
A z/VM agent has connected.
p1 identifies the z/VM system where the agent is running.
p2 and p3 show the time zone offset in hours and minutes.
System Action:
None.
User Action:
None.
Reason:
A z/VM agent has connected; however, the correct protocol was not observed. The first record sent by the agent must be the NODEINFO record identifying the z/VM system.
System Action:
The connection is terminated.
User Action:
Confirm that a z/VM agent is trying to connect. You may have misconfigured a Linux agent to connect to the z/VM server port.
Reason:
A z/VM server is terminating the connection to a z/VM agent.
p1 identifies the system where the agent is running.
System Action:
The connection is terminated.
User Action:
None.
Reason:
A connection to the z/VM server for a system has been terminated by the z/VM agent on that system.
p1 identifies the system where the agent is running.
System Action:
The connection is terminated.
User Action:
None.
Reason:
A connection to the z/VM server for a system received an unsupported message type.
p1 identifies the system.
p2 is the message type.
System Action:
The message is ignored.
User Action:
None.
Reason:
This message is a normalized unsolicited asynchronous CP message from a z/VM agent.
p1 identifies the z/VM system.
p2 is the user ID.
p3 is the message text.
System Action:
None.
User Action:
None.
Reason:
This message is a normalized unsolicited Single Console Image Facility (SCIF) message from a z/VM agent.
p1 identifies the z/VM system.
p2 is the user ID.
p3 is the message text.
System Action:
None.
User Action:
None.
Reason:
This message is a normalized unsolicited CP error message (EMSG) from a z/VM agent.
p1 identifies the z/VM system.
p2 is the user ID.
p3 is the message text.
System Action:
None.
User Action:
None.
Reason:
This message is a normalized unsolicited informational message for CP (IMSG) from a z/VM agent.
p1 identifies the z/VM system.
p2 is the user ID.
p3 is the message text.
System Action:
None.
User Action:
None.
Reason:
This message is a normalized unsolicited CP message (MSG or MSGNOH) from a z/VM agent.
p1 identifies the z/VM system.
p2 is the user ID.
p3 is the message text.
System Action:
None.
User Action:
None.
Reason:
This message is a normalized unsolicited special message (SMSG) from a z/VM agent.
p1 identifies the z/VM system.
p2 is the user ID.
p3 is the message text.
System Action:
None.
User Action:
None.
Reason:
This message is a normalized unsolicited message directed to the virtual console by the virtual machine from a z/VM agent.
p1 identifies the z/VM system.
p2 is the user ID.
p3 is the message text.
System Action:
None.
User Action:
None.
Reason:
This message is a normalized unsolicited CP warning message (WNG) from a z/VM agent.
p1 identifies the z/VM system.
p2 is the user ID.
p3 is the message text.
System Action:
None.
User Action:
None.
Reason:
This message indicates whether the agent is being traced.
p1 indicates the tracing status, either ON or OFF .
System Action:
None.
User Action:
None.
Reason:
An unsolicited message traffic client has successfully connected to the Linux Connector Unsolicited Message Server.
p1 is the job name of the client.
p2 is the IP address of the client.
System Action:
None.
User Action:
None.
Reason:
A connection to the UNSOLMSG server for a client was terminated by the client.
p1 identifies the client.
System Action:
None.
User Action:
None.
Reason:
An unsolicited message traffic client has successfully connected to the Linux Connector Unsolicited Message Server; however, the client did not follow the correct connection protocol. Instead of sending HELLO, the client sent p1.
System Action:
The connection is terminated.
User Action:
For assistance, contact CA Support.
Reason:
Linux Connector can operate in single or multiclient mode.
An unsolicited message server multiclient handler was started when the Linux Connector region was not in multiclient mode.
System Action:
The multiclient handler is terminated.
User Action:
To run Linux Connector in multiclient mode, update the LNXPARMS member to set the MULTICLIENT parameter to YES.
Reason:
Linux Connector can operate in single client or multiclient mode.
Linux Connector is currently in single client mode, and a request was received from a second client.
p1 is the name the client attempting to connect.
p2 is the IP address of the client attempting to connect.
p3 is the client that is already connected.
System Action:
The second client connection is terminated.
User Action:
To run Linux Connector in multiclient mode, update the LNXPARMS member to set the MULTICLIENT parameter to YES.
| Copyright © 2011 CA. All rights reserved. | Tell Technical Publications how we can improve this information |