The following variables are used in EYUCSnnnn messages:
The link set services subcomponent of the Communications component has been successfully initialized.
The Communications component continues to initialize its other subcomponents.
None
EYULOG
EYU0CSIN
The Communications long running task (LRT) is being initialized.
Initialization of the Communications LRT continues.
None
EYULOG
EYU0CSLT
The Communications long running task (LRT) has been successfully initialized.
The Communications component continues to initialize its other subcomponents.
None
EYULOG
EYU0CSLT
The Communications long running task (LRT) is being terminated.
Termination of the Communications LRT continues.
None
EYULOG
EYU0CSLT
The Communications long running task (LRT) has been terminated.
If the LRT was terminated as the result of a normal shutdown, the CICSPlex® SM shutdown continues. If the LRT terminated because of an abnormal condition, a message preceding this one describes the condition that caused the termination. CICSPlex SM may continue running without the services of the LRT.
If a normal CICSPlex SM shutdown is in progress, no action is required. If the LRT terminated because of an abnormal condition (as indicated by message EYUCS0104E preceding this message), CICSPlex SM should be shut down and restarted.
EYULOG
EYU0CSLT
The specified communications connection has been successfully assigned to a CICSPlex SM link set where type and name are as described in the introduction to the EYUCSnnnn messages. Link sets are the means by which CICSPlex SM optimizes processing to be performed for connections with similar attributes. Once a connection has been assigned to a link set, CICSPlex SM can transmit data to, and receive data from, its communications partner.
The connection becomes available to other CICSPlex SM communications processes.
None.
EYULOG
EYU0CSAC
The specified communications connection has been successfully unassigned from a CICSPlex SM link set. Link sets are the means by which CICSPlex SM optimizes processing to be performed for connections with similar attributes where type and name are as described in the introduction to the EYUCSnnnn messages. Once a connection has been unassigned from a link set, CICSPlex SM can no longer transmit data to, or receive data from, its communications partner.
The connection is no longer available to other CICSPlex SM communications processes.
None.
EYULOG
EYU0CSUC
A shortage of service request block elements for a communications long running task (LRT) has been successfully relieved by allocating additional elements. Service request block elements are the means by which CICSPlex SM communications processes direct requests to the LRT.
Any communications processes waiting for an element are dispatched and permitted to acquire one.
None.
EYULOG
EYU0CSES
An message had been received from the partner CMAS during the connection initialization process. See EYUCSnnnn messagesfor the meaning of name and text.
Depending on the severity of the message text, either the CMAS to CMAS connection completes successfully, or the connection terminates and other supporting messages are issued.
If the connection has failed to complete successfully, retain the EYULOG, JOBLOG and exception trace records from both CMASes and contact your IBM® support center
EYULOG
EYU0CLCS, EYU0CLMS
A communications connection between the local CMAS and a partner CMAS is starting. See EYUCSnnnn messages for the meaning of mode, type and name.
The communications connection continues to initialize.
None
EYULOG
EYU0CLCS, EYU0CLMS
The indicated EYUPARM was set to a non-zero value less than 10 seconds.
The value for the indicated EYUPARM is set to 10 seconds and CMAS initialization continues.
If a value greater than 10 seconds is desired, modify the indicated EYUPARM and restart the CMAS. If a value of 10 seconds is desired, no user response is required for the current execution of the CMAS. However, to avoid this message for future executions of the CMAS, modify the indicated EYUPARM to 10 before the CMAS is restarted.
Console, job log, EYULOG
EYU0CSLT
The indicated EYUPARM has been given a value that is less than the TOPOLLINT EYUPARM. While this is allowed, it is not efficient.
CMAS initialization continues.
Since polling is used to determine when to time out a request, specifying a lower value for time out than for polling will most likely result in the request being timed out later than specified. If this is not desired, modify the EYUPARMs so that TOPOLLINT is less than or equal to the indicated EYUPARM and restart the CMAS.
Console, job log, EYULOG
EYU0CSLT
The link set services subcomponent of the Communications component could not be initialized.
CICSPlex SM initialization terminates abnormally. A user trace record is written to the CICS® trace data set.
Examine the exception trace records, and any messages issued before this one, to determine the cause of the problem.
Console, job log, EYULOG
EYU0CSIN
The Communications long running task (LRT) was not able to create the link set pending connections list. This list is used to store information about communications connections whose status is to be monitored.
CICSPlex SM terminates abnormally. A user trace record is written to the CICS trace data set.
Collect the exception trace records and the job log and contact your IBM Support Center.
Console, job log, EYULOG
EYU0CSLT
The link set services subcomponent of the Communications component was not able to start the Communications long running task (LRT) for a CICSPlex SM address space (CMAS).
CICSPlex SM terminates abnormally. A user trace record is written to the CICS trace data set.
Examine the CICS CSD to verify that transaction CSLT and program EYU9XLOP are defined. If the definitions appear to be correct, collect the exception trace records and the job log and contact your IBM Support Center.
Console, job log, EYULOG
EYU0CSIN
The Communications long running task (LRT) encountered an error from which it could not recover.
The LRT terminates. CICSPlex SM may continue running without the services of the LRT.
Examine any messages issued before this one to determine the cause of the problem. Collect any exception trace records, the job log, and CICS or MVS™ dump output, if available, and contact your IBM Support Center.
Console, job log, EYULOG
EYU0CSLT
The specified communications connection could not be assigned to a CICSPlex SM link set where type and name are as described in the introduction to the EYUCSnnnn messages. Link sets are the means by which CICSPlex SM optimizes processing to be performed for connections with similar attributes. Until a connection has been assigned to a link set, CICSPlex SM cannot transmit data to, or receive data from, its communications partner.
CICSPlex SM attempts to assign the connection again at periodic intervals.
If the problem persists, collect any exception trace records and the job log and contact your IBM Support Center.
Console, job log, EYULOG
EYU0CSAC
The specified communications connection could not be unassigned from a CICSPlex SM link set where type and name are as described in the introduction to the EYUCSnnnn messages. Link sets are the means by which CICSPlex SM optimizes processing to be performed for connections with similar attributes.
The connection cannot be used by other CICSPlex SM communications processes. A user trace record is written to the CICS trace data set.
Collect the exception trace records and the job log and contact your IBM Support Center.
Console, job log, EYULOG
EYU0CSUC
A shortage of service request block elements for a communications long running task (LRT) could not be relieved because there was insufficient storage to allocate additional elements. Service request block elements are the means by which CICSPlex SM communications processes direct requests to the LRT.
Any communications processes waiting for an element receive an indication of the failure.
Allocate additional storage to the CICS extended dynamic storage area (EDSA).
Console, job log, EYULOG
EYU0CSES
During CMAS initialization, the local CMAS is waiting for other active CMASes to initiate a CMAS to CMAS connection. At least one partner CMAS has failed to do this in the allotted five minute time frame.
CMAS initialization continues after a system dump is requested and an exception trace record is written to the CICS trace data set.
This situation can occur if CICS communications problems exist or if a CMAS to CMAS definition (CMTCMDEF) was removed from a partner CMAS without COLD starting the CMAS. If these causes can be ruled out, collect the system dump, the auxtrace data sets, and the complete job output from the CMAS and contact your IBM support center.
Console, job log, EYULOG
EYU0CSLT
The Communications long running task (LRT) was not able to load the NetView® PPI module, CNMNETV.
CICSPlex SM continues running with NetView support disabled.
Determine why CNMNETV could not be loaded and correct the problem.
Console, job log, EYULOG
EYU0CSLT
The Communications long running task (LRT) determined that the release of NetView installed on the system does not provide the required level of PPI support.
CICSPlex SM continues running with NetView support disabled.
Review the CICSPlex SM installation requirements and install a supported release of NetView on the system.
Console, job log, EYULOG
EYU0CSLT
A Communications long running task (LRT) service request block element shortage has been detected. Service request block elements are the means by which CICSPlex SM communications processes direct requests to the LRT.
Any communications processes waiting for an element are suspended. CICSPlex SM attempts to allocate additional elements. This message is followed by another message that indicates whether the shortage could be relieved: EYUCS0008I indicates the shortage was relieved; EYUCS0107E indicates it was not.
None.
Console, job log, EYULOG
EYU0CSES
Data records have not been received by or have not been able to be sent to the specified CMAS for an internally-defined period of time.
The communications link between the local CMAS and the specified CMAS is terminated.
Check the job log of the specified CMAS for messages that may indicate the cause of the problem.
Console, job log, EYULOG
EYU0CSLT
An unexpected condition was found when the local CMAS attempted to initiate a communications connection. See EYUCSnnnn messages for the meaning of name. reason is one of the following values:
The CMAS-to-CMAS connection is retried.
If the connection establishes itself properly, no further action is required. If the connection fails to complete, retain the EYULOG, JOBLOG and exception trace records from the CMAS and contact your IBM support center.
Console, job log, EYULOG
EYU0CLCS, EYU0CLMS
A communications method has written an exception trace record where tracepoint is the trace point identifier and debug is the debug text. This message is imbedded in message EYUCS0009I. The tracepoint and debug information is for use by IBM support.
The CMAS terminates the connection to the partner system.
This message occurs with other communication error messages. If the connection remains inactive, collect the job log, EYULOG and exception trace records from both CMASes and contact your IBM support center.
EYULOG via message EYUCS0009I
EYU0CLCT, EYU0CLMT
The CMAS has determined that the connected MAS specified is not responding to requests sent to it by the CMAS.
This message is issued and processing continues.
Investigate the MAS to determine whether it should be stopped to alleviate the problem, because a non-responsive MAS can cause the CMAS to experience problems with other MAS and CMAS connections.
Console, job log, EYULOG
EYU0CSLT
The CMAS has determined that a MAS that has not been responding to requests sent to it by the CMAS is now responding to those requests.
This message is issued and processing continues.
None.
Console, job log, EYULOG
EYU0CSLT