The following variables are used in EYUCLnnnn messages:
The protocol services subcomponent of the Communications component has been successfully initialized.
The Communications component continues to initialize its other subcomponents.
None.
EYULOG
EYU0CLIN, EYU1CLIN
The Initial Contact Transient for the specified protocol has been started where protocol is as described in the introduction to the EYUCLnnnn messages. The necessary data structures are built in preparation for initial contact from the First Speaker Node.
Initialization of the protocol services subcomponent continues.
None.
EYULOG
EYU0CLET, EYU0CLCT, EYU0CLMT, EYU0CLRT, EYU0CLST
The specified protocol has successfully initiated a required task where protocol and task are as described in the introduction to the EYUCLnnnn messages.
Initialization of the protocol services subcomponent continues.
None.
EYULOG
EYU0CLER, EYU0CLEV, EYU0CLCS, EYU0CLCU, EYU0CLMS, EYU0CLRR, EYU0CLRS, EYU0CLRV, EYU0CLRW, EYU0CLSS, EYU0CLST, EYU0CLSV, EYU0CLSW
The Initial Contact Transient (ICT) for the specified protocol has been terminated where protocol is as described in the introduction to the EYUCLnnnn messages. Other nodes may no longer establish contact with the current node. All previously created data structures are destroyed.
Termination of the protocol services subcomponent continues.
None.
EYULOG
EYU0CLET, EYU0CLCT, EYU0CLMT, EYU0CLRT, EYU0CLST
A required task for the specified protocol has been terminated where protocol and task are as described in the introduction to the EYUCLnnnn messages.
Termination of the protocol services subcomponent continues.
None.
EYULOG
EYU0CLER, EYU0CLEV, EYU0CLCS, EYU0CLCU, EYU0CLMS, EYU0CLRR, EYU0CLRS, EYU0CLRV, EYU0CLRW, EYU0CLSS, EYU0CLST, EYU0CLSV, EYU0CLSW
A link between the current node and the specified node has been established using the specified protocol where protocol and nodename are as described in the introduction to the EYUCLnnnn messages.
This communications link is available for data transmission between the specified nodes.
None.
EYULOG
EYU0CLER, EYU0CLEV, EYU0CLRT
The link between the current node and the specified node, using the specified protocol, has been terminated where protocol and nodename are as described in the introduction to the EYUCLnnnn messages.
This communications link is no longer available for data transmission between the specified nodes.
None.
EYULOG
EYU0CLER, EYU0CLEV
The ESSS ICT was entered for a local MAS request to establish a communications link to the specified node where nodename is as described in the introduction to the EYUCLnnnn messages.
The ICT Attach request is processed.
None.
EYULOG
EYU0CLET
The ESSS ICT was entered for a local MAS request to terminate the communications link between the current node and the specified node where nodename is as described in the introduction to the EYUCLnnnn messages.
The ICT Detach request is processed.
None.
EYULOG
EYU0CLET
The protocol services subcomponent of the Communications component has been terminated.
Termination of the Communications component continues. Because protocol services is not active, data can no longer be transmitted between CICSPlex SM address spaces.
None.
EYULOG
EYU0CLTM
The process of connecting the specified nodes is complete where nodename is as described in the introduction to the EYUCLnnnn messages.
The status of this connection is set to active. The specified nodes and their connection can now be managed using the end-user interface.
None.
Console, job log, EYULOG
EYU0CLCS, EYU0CLMS, EYU1CLRW
A link buffer shortage that was detected by the protocol services subcomponent has been successfully relieved. A new pool of link buffers has been acquired.
Protocol services processing continues.
None.
EYULOG
EYU0CLBL, EYU0CLBE
In an attempt to establish a link between the current node and the specified node, a receive task using the specified protocol has been started where task, protocol, and nodename are as described in the introduction to the EYUCLnnnn messages, and where:
Connection Services continues initializing the link to the specified node.
None.
EYULOG
EYU0CLCS, EYU0CLCT, EYU0CLMS, EYU0CLMT, EYU0CLRR, EYU0CLRS, EYU0CLRV, EYU0CLRW, EYU0CLSS, EYU0CLST, EYU0CLSV, EYU0CLSW, EYU1CLRV, EYU1CLRW
The link between the current node and the specified node, using the specified protocol, is being terminated normally where task, protocol, and nodename are as described in the introduction to the EYUCLnnnn messages, and where:
The task for this link is terminated. Protocol services is notified that the link is no longer available.
None.
Console, job log, EYULOG
EYU0CLCS, EYU0CLCV, EYU0CLMS, EYU0CLMV, EYU0CLRR, EYU0CLRS, EYU0CLRV, EYU0CLRW, EYU0CLSS, EYU0CLST, EYU0CLSV, EYU0CLSW, EYU1CLRV, EYU1CLRW
The Send Link Manager task, which manages the sending of generic alerts from a CMAS to NetView®, was successfully initiated. This task can be initiated as part of CMAS initialization or as a result of a user request to activate the NetView interface in a running CMAS.
NetView interface processing continues.
None.
EYULOG
EYU0CLNW
The Send Link Manager task was successfully terminated. This task can be terminated as part of CMAS termination or as a result of a user request to deactivate the NetView interface in a running CMAS.
The NetView interface is no longer available.
None.
EYULOG
EYU0CLNW
The communications buffer long running task (LRT) has been termianted.
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 EYUCL0121E preceding this message), CICSPlex SM should be shut down and restarted.
EYULOG
EYU0CSGT
The MVS image is running in workload management goal mode but the CMAS is not defined to the MVS service class, SYSSTC. For goal mode the CMASs should not be run as servers, but should be defined to SYSSTC as exempt from server transaction response time management. Started tasks in SYSSTC are assigned a high dispatching priority.
The CMAS issues this warning message and continues processing. However, CICSPlex SM may experience severe performance problems.
It is important that the CMAS have the ability to process data with a higher priority than the MAS it manages. Therefore, when the MVS image is running in workload management goal mode, the CMAS should be defined to the MVS service class, SYSSTC. See the CICS Transaction Server for z/OS® Installation Guide.
Console, job log, EYULOG
EYU0CLET
When the MVS image is running in workload management compatibility mode, the dispatching priority of the CMAS should be greater than or equal to the dispatching priority of the connecting MAS to ensure optimal performance.
nn is the hexadecimal dispatching priority.
The CMAS issues this warning message and continues processing. However, CICSPlex SM may experience severe performance problems.
It is important that the CMAS have the ability to process data with a higher priority than the MAS it manages. Therefore, when the MVS image is running in workload management compatibility mode, the CMAS's dispatching priority should be greater than or equal to the dispatching priority of the connecting MAS. See the CICS Transaction Server for z/OS Installation Guide.
Console, job log, EYULOG
EYUOCLET
The protocol services subcomponent of the Communications component could not be initialized.
The impact on system processing depends on what type of address space was being initialized:
Examine the exception trace records, and any messages issued before this one, to determine the cause of the problem.
Console, job log, EYULOG
EYU0CLIN, EYU1CLIN
An attempt to initialize the Initial Contact Transient (ICT) for the specified protocol in the CMAS has failed where protocol is as described in the introduction to the EYUCLnnnn messages.
Communications initialization fails causing the CMAS to terminate. CICSPlex SM takes an SVC dump with a dump code of EYUXL001.
Verify that the appropriate ICT transaction ID is defined for program EYU9XLOP. Examine the trace records generated by EYU0CLIN and, if the ICT transaction ID was not found, use kernel linkage to determine the cause of the problem.
Console, job log, EYULOG
EYU0CLIN
An attempt to initiate a required task for the specified protocol has failed where protocol and task are as described in the introduction to the EYUCLnnnn messages.
If the task was started from the Initial Contact Transient (ICT), the ICT terminates, which prevents links from being established with the current node.
If the task was started from protocol services initialization, the impact on system processing depends on what type of address space was being initialized:
Verify that the appropriate transaction ID is defined for program EYU9XLOP. Examine the trace records generated by any of the issuing modules to determine the cause of the problem.
Console, job log, EYULOG
EYU0CLET, EYU0CLIN, EYU0CLCT, EYU0CLMT, EYU0CLRT, EYU0CLST
The Initial Contact Transient (ICT) for the specified protocol terminated abnormally due to an error condition where protocol is as described in the introduction to the EYUCLnnnn messages.
The ICT task terminates, which prevents nodes using the named protocol from establishing communications links.
Examine the exception trace records, and any messages issued before this one, to determine the cause of the problem.
Console, job log, EYULOG
EYU0CLET
A required task for the specified protocol has terminated due to an error condition where protocol and task are as described in the introduction to the EYUCLnnnn messages.
The link conversation state is set to inactive, which prevents SENDs or RECEIVEs between the current node and other nodes.
Examine the exception trace records, and any messages issued before this one, to determine the cause of the problem.
Console, job log, EYULOG
EYU0CLER, EYU0CLEV, EYU0CLCS, EYU0CLCU, EYU0CLMS, EYU0CLRR, EYU0CLRS, EYU0CLRV, EYU0CLRW, EYU0CLSS, EYU0CLST, EYU0CLSV, EYU0CLSW
A link between the current node and the specified node has terminated due to an error condition where protocol and nodename are as described in the introduction to the EYUCLnnnn messages.
The link conversation state is set to inactive, which prevents SENDs or RECEIVEs between the two nodes.
Examine the exception trace records, and any messages issued before this one, to determine the cause of the problem.
Console, job log, EYULOG
EYU0CLER, EYU0CLEV, EYU0CLCS, EYU0CLCU, EYU0CLMS, EYU0CLRR, EYU0CLRS, EYU0CLRV, EYU0CLRW, EYU0CLSS, EYU0CLST, EYU0CLSV, EYU0CLSW
The Initial Contact Transient (ICT) Attach request made by the MAS to establish a communications link has failed where protocol and nodename are as described in the introduction to the EYUCLnnnn messages, and where reason indicates the cause of the failure.
The ICT Attach request is denied. Initialization of the local MAS terminates. A user trace record is written to the CICS trace data set.
Response depends on the reason given for the failure as follows:
Console, job log, EYULOG
EYU0CLET, EYU0CLRT, EYU0CLST
The Initial Contact Transient (ICT) Detach request made by the local MAS to terminate an ESSS communications link has failed where nodename is as described in the introduction to the EYUCLnnnn messages.
The ICT Detach request is denied.
Examine the exception trace records issued by EYU0CLET and any messages issued before this one, to determine the cause of the problem.
Console, job log, EYULOG
EYU0CLET
An error occurred during an attempting to terminate the Protocol Services subcomponent of the Communications component.
All other Communications subcomponents attempt an orderly shutdown. 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
EYU0CLTM
An Environment Services System Services (ESSS) Initial Contact Transient (ICT) to establish a link between the current CICSPlex SM address space (CMAS) and the specified nodename has failed where nodename is as described in the introduction to the EYUCLnnnn messages.
Initialization of the MAS terminates.
Make sure the name of the MAS used in the startup JCL is one that is in the CMAS data repository. Examine the user trace records in the CICS trace data set to determine the cause of the problem.
Console, job log, EYULOG
EYU0CLET
A link buffer shortage detected by the protocol services subcomponent could not be relieved. There was not enough virtual storage available to acquire a new pool of link buffers.
The Communications component terminates.
Make more virtual storage available and then restart CICSPlex SM.
Console, job log, EYULOG
EYU0CLBL
During initialization of a CMAS or MAS, the protocol services subcomponent was unable to complete the specified action, where action identifies the action that could not be completed as one of the following:
Initialization of the CMAS or MAS terminates.
Examine the exception trace records, and any messages issued before this one, to determine the cause of the problem.
Console, job log, EYULOG
EYU0CLIN
An abnormal condition caused the link between the current node and the specified node to be terminated where task, protocol, and nodename are as described in the introduction to the EYUCLnnnn messages, and where:
Protocol services is notified that the link is no longer available. A user trace record is written to the CICS trace data set.
If the specified node terminated abnormally, this message is to be expected. Determine why the node terminated and then reestablish the communication link, if possible.
If the node appears to be active and available, collect the exception trace records, and any messages issued before this one, and contact your IBM Support Center.
Console, job log, EYULOG
EYU0CLCS, EYU0CLCV, EYU0CLMS, EYU0CLMV, EYU0CLRR, EYU0CLRS, EYU0CLRV, EYU0CLRW, EYU0CLSS, EYU0CLST, EYU0CLSV, EYU0CLSW.
The Send Link Manager task, which manages the sending of generic alerts from a CMAS to NetView, could not be initiated.
The NetView interface is not available. A user trace record is written to the CICS trace data set.
Collect the exception trace records and contact your IBM Support Center.
Console, job log, EYULOG
EYU0CLNW
An abnormal condition caused the Send Link Manager task to terminate.
The NetView interface is no longer available. A user trace record is written to the CICS trace data set.
Collect the exception trace records and contact your IBM Support Center.
Console, job log, EYULOG
EYU0CLNW
There is not enough ECDSA storage available to successfully expand the link buffer pool to meet a use request.
CICSPlex SM terminates. A user trace record is written to the CICS trace data set.
Rerun the CICS with a larger ECDSA storage area allocation.
Console, job log, EYULOG
EYU0CLBL
While two CMASs were attempting to connect to each other, one of the CMASs determined that their connection definitions are inconsistent, where:
The attempt to connect the two CMASs fails. No communication is possible between the CMASs.
Use the CMTCMDEF view to correct the inconsistencies in the definitions of the specified CMASs.
Console, job log, EYULOG
EYU0CLCT
While attempting to activate a CICSPlex SM connection between this CMAS and another CMAS, a failure has occured, where:
The connection is not completed.
Collect all job output and AUXTRACE datasets from both CMASs. After a timeout period in the other CMAS, the connection attempt should automatically be retried. If the problem persists, contact your IBM Support Center.
Console, job log, EYULOG
EYU0CLCT, EYU0CLMT
The protocol services subcomponent of the communications component was not able to start the communications buffer 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 LSGT and program EYU9XLOP are defined. If the definitions are correct, collect the exception trace records and the job log and contact your IBM support center.
Console, job log, EYULOG
EYU0CLIN
The communications buffer 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/ESA dump output, if available, and contact your IBM support center.
Console, job log, EYULOG
EYU0CSGT
A shortage of MAS communication buffers has been detected by a CMAS or one of its local MASes. This message is issued the first time a shortage occurs during the execution of the CMAS.
The CMAS or MAS will issue this message, request an SVCdump, and then issue an exception trace. Execution of the CMAS or MAS then continues.
Collect the CICS auxtrace data sets, the SVC dump, and the job output from the CMAS or MAS. If the requesting system is a MAS, also collect the CICS auxtrace data sets and job output from the CMAS to which the MAS connects. Contact your IBM Support Center with the documentation collected.
Console, job log, EYULOG
EYU0CTBT
The ESSS ICT was entered for a local MAS request to terminate communications from the CMAS to the specified node: where nodename is as described in the introduction to the EYUCLnnnn messages.
The ICT STOPCOM request is processed. No messages are sent from the CMAS to the specified node until the node reconnects to the CMAS.
Check for error messages in the job log for the specified node and follow the instructions for those messages.
Console, job log, EYULOG
EYU0C
While attempting to activate a CICSPlex SM connection between this LMAS and a CMAS, a failure has occured, where:
The connection is not completed.
Refer to the job output of the CMAS for messages that provide more details of the failure.
Console, job log
EYU0CLIN
During CMAS termination, EYU0CLET encountered an error while attempting to disconnect active local MASes.
A dump is requested, this message is issued, and CMAS termination continues. The title of the dump will be similar to the following:
EYU0XZSD Dump,cmasjobn,cmasname,lpar,CMAS,LEEI,tasknum,TRAC,
EYU0CLET,mm/dd/yy,hh:mm:ss
Collect the dump, the auxtrace data sets, and the complete job output from the CMAS and contact your IBM support center.
Console, job log, EYULOG
EYU0CLET
A request by MAS nodename to establish a communications link has failed because MAS nodename is running at a later version than the CMAS where:
The capability of a CMAS or MAS is determined by its service level or CICSPlex SM release and version.
This message might be followed by mesage EYUCL0131E which can give more information.
The request to establish a communications link is denied. Initialization of the MAS terminates.
Correct the startup JCL for MAS nodename so that its service level or CICSPlex SM release and version is not later than that of the CMAS that issued this message.
Console, job log, EYULOG
EYU0CLET, EYU0CLRT, EYU0CLST
MAS nodename has a version of resource table objname that does not match the version in use by this CMAS where:
This message can be issued for up to two resource table types.
See message EYUCL0130E for more information.
See message EYUCL0130E for more information.
Console, job log, EYULOG
EYU0CLET, EYU0CLRT, EYU0CLST
The protocol services subcomponent has determined that there are no link buffers left in the link buffer pool.
CICSPlex SM attempts to acquire a new pool of link buffers. This message is followed by another message that indicates whether the shortage could be relieved: EYUCL0013I indicates the shortage was relieved; EYUCL0111E indicates it was not.
None.
EYULOG
EYU0CLBL, EYU0CLBE