EYUCLnnnn messages

The following variables are used in EYUCLnnnn messages:

protocol
Identifies the communications protocol being used as one of the following:
CPI-C
Common Programming Interface Communications
LU6.2
CICS® intersystem communication
MRO
CICS/ESA Multiregion Operation
ESSS
CICSPlex® SM Environment Services System Services
task
Identifies a specific communications task. One or more of the following tasks are initiated, depending on the communications node involved and the type of protocol in use:
Receive Link Manager
Start of changeInitiated within a CMAS network node to manage a set of MAS CPI-C endpoint connections.End of change
Receive Link Task
Start of changeInitiated within a MAS endnode to form a controlled endpoint connection.End of change
Send Link Manager
Initiated within a CMAS network node to manage CPI-C and MRO logical connections.
Independent Receive Task
Start of changeInitiated within a CMAS network node to manage a single network connection.End of change
nodename
Identifies a communications node by its CMAS or MAS name.
EYUCL0001I
Protocol Services initialization complete
Explanation:

The protocol services subcomponent of the Communications component has been successfully initialized.

System action:

The Communications component continues to initialize its other subcomponents.

User response:

None.

Destination:

EYULOG

Module:

EYU0CLIN, EYU1CLIN

EYUCL0002I
protocol Initial Contact Transient initiated
Explanation:

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.

System action:

Initialization of the protocol services subcomponent continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0CLET, EYU0CLCT, EYU0CLMT, EYU0CLRT, EYU0CLST

EYUCL0003I
protocol task initiated
Explanation:

The specified protocol has successfully initiated a required task where protocol and task are as described in the introduction to the EYUCLnnnn messages.

System action:

Initialization of the protocol services subcomponent continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0CLER, EYU0CLEV, EYU0CLCS, EYU0CLCU, EYU0CLMS, EYU0CLRR, EYU0CLRS, EYU0CLRV, EYU0CLRW, EYU0CLSS, EYU0CLST, EYU0CLSV, EYU0CLSW

EYUCL0004I
protocol Initial Contact Transient terminated
Explanation:

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.

System action:

Termination of the protocol services subcomponent continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0CLET, EYU0CLCT, EYU0CLMT, EYU0CLRT, EYU0CLST

EYUCL0005I
protocol task terminated
Explanation:

A required task for the specified protocol has been terminated where protocol and task are as described in the introduction to the EYUCLnnnn messages.

System action:

Termination of the protocol services subcomponent continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0CLER, EYU0CLEV, EYU0CLCS, EYU0CLCU, EYU0CLMS, EYU0CLRR, EYU0CLRS, EYU0CLRV, EYU0CLRW, EYU0CLSS, EYU0CLST, EYU0CLSV, EYU0CLSW

EYUCL0006I
protocol link to nodename established
Explanation:

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.

System action:

This communications link is available for data transmission between the specified nodes.

User response:

None.

Destination:

EYULOG

Module:

EYU0CLER, EYU0CLEV, EYU0CLRT

EYUCL0007I
protocol link to nodename terminated
Explanation:

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.

System action:

This communications link is no longer available for data transmission between the specified nodes.

User response:

None.

Destination:

EYULOG

Module:

EYU0CLER, EYU0CLEV

EYUCL0008I
ESSS ICT entered for Attach to nodename
Explanation:

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.

System action:

The ICT Attach request is processed.

User response:

None.

Destination:

EYULOG

Module:

EYU0CLET

EYUCL0009I
ESSS ICT entered for Detach from nodename
Explanation:

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.

System action:

The ICT Detach request is processed.

User response:

None.

Destination:

EYULOG

Module:

EYU0CLET

EYUCL0010I
Protocol Services termination complete
Explanation:

The protocol services subcomponent of the Communications component has been terminated.

System action:

Termination of the Communications component continues. Because protocol services is not active, data can no longer be transmitted between CICSPlex SM address spaces.

User response:

None.

Destination:

EYULOG

Module:

EYU0CLTM

EYUCL0012I
Connection of nodename to nodename complete.
Explanation:

The process of connecting the specified nodes is complete where nodename is as described in the introduction to the EYUCLnnnn messages.

System action:

The status of this connection is set to active. The specified nodes and their connection can now be managed using the end-user interface.

User response:

None.

Destination:

Start of changeConsole, job log, EYULOGEnd of change

Module:

EYU0CLCS, EYU0CLMS, EYU1CLRW

EYUCL0013I
Link Buffer Pool element shortage relieved
Explanation:

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.

System action:

Protocol services processing continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0CLBL, EYU0CLBE

EYUCL0015I
task initiated for protocol connection with type nodename
Explanation:

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:

type
Start of changeIdentifies the node being connected to as a CMAS.End of change
System action:

Connection Services continues initializing the link to the specified node.

User response:

None.

Destination:

Start of changeEYULOGEnd of change

Module:

EYU0CLCS, EYU0CLCT, EYU0CLMS, EYU0CLMT, EYU0CLRR, EYU0CLRS, EYU0CLRV, EYU0CLRW, EYU0CLSS, EYU0CLST, EYU0CLSV, EYU0CLSW, EYU1CLRV, EYU1CLRW

EYUCL0016I
task terminated for protocol connection with type nodename
Explanation:

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:

type
Start of changeIdentifies the node to which the link is being terminated as a CMAS.End of change
System action:

The task for this link is terminated. Protocol services is notified that the link is no longer available.

User response:

None.

Destination:

Start of changeConsole, job log, EYULOGEnd of change

Module:

EYU0CLCS, EYU0CLCV, EYU0CLMS, EYU0CLMV, EYU0CLRR, EYU0CLRS, EYU0CLRV, EYU0CLRW, EYU0CLSS, EYU0CLST, EYU0CLSV, EYU0CLSW, EYU1CLRV, EYU1CLRW

EYUCL0017I
Send Link Manager initiated for NetView
Explanation:

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.

System action:

NetView interface processing continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0CLNW

EYUCL0018I
Send Link Manager terminated for NetView
Explanation:

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.

System action:

The NetView interface is no longer available.

User response:

None.

Destination:

EYULOG

Module:

EYU0CLNW

Start of change
EYUCL0022I
Communications buffer long-running task termination complete.
Explanation:

The communications buffer long running task (LRT) has been termianted.

System action:

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.

User response:

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.

Destination:

EYULOG

Module:

EYU0CSGT

End of change
Start of change
EYUCL0023W
The MVS image is running in workload management goal mode but the CMAS is not defined to the service class, SYSSTC.
Explanation:

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.

System action:

The CMAS issues this warning message and continues processing. However, CICSPlex SM may experience severe performance problems.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0CLET

End of change
Start of change
EYUCL0024W
The MVS image is running in workload management compatibility mode and the dispatching priority (X'nn') of the connecting MAS (nodename) is higher than the dispatching priority (X'nn') of the CMAS.
Explanation:

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.

System action:

The CMAS issues this warning message and continues processing. However, CICSPlex SM may experience severe performance problems.

User response:

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.

Note:
The minimum required level of operating system for CICS Transaction Server for z/OS, Version 2 Release 3 is z/OS Version 1 Release 4. Beginning with z/OS V1 R3 WLM compatibility mode is no longer available. Therefore, this message will not be issued in CICS Transaction Server for z/OS Version 2 Release 3. The message remains in the documentation for reference purposes.
Destination:

Console, job log, EYULOG

Module:

EYUOCLET

End of change
EYUCL0101E
Protocol Services initialization failed
Explanation:

The protocol services subcomponent of the Communications component could not be initialized.

System action:

The impact on system processing depends on what type of address space was being initialized:

CMAS
The CMAS is terminated. CICSPlex SM takes an SVC dump with a dump code of EYUXL001.
MAS
The MAS is terminated. CICSPlex SM takes a transaction dump with a dump code of EYUI and returns control to CICS.
User response:

Examine the exception trace records, and any messages issued before this one, to determine the cause of the problem.

Destination:

Start of changeConsole, job log, EYULOGEnd of change

Module:

EYU0CLIN, EYU1CLIN

EYUCL0102E
protocol Initial Contact Transient initiation failed
Explanation:

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.

System action:

Communications initialization fails causing the CMAS to terminate. CICSPlex SM takes an SVC dump with a dump code of EYUXL001.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0CLIN

EYUCL0103E
protocol task initiation failed
Explanation:

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.

System action:

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:

CMAS
The CMAS is terminated. CICSPlex SM takes an SVC dump with a dump code of EYUXL001.
MAS
The MAS is terminated. CICSPlex SM takes a transaction dump with a dump code of EYUI and returns control to CICS.
User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0CLET, EYU0CLIN, EYU0CLCT, EYU0CLMT, EYU0CLRT, EYU0CLST

EYUCL0104E
protocol Initial Contact Transient terminated abnormally
Explanation:

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.

System action:

The ICT task terminates, which prevents nodes using the named protocol from establishing communications links.

User response:

Examine the exception trace records, and any messages issued before this one, to determine the cause of the problem.

Destination:

Console, job log, EYULOG

Module:

EYU0CLET

EYUCL0105E
protocol task terminated abnormally
Explanation:

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.

System action:

The link conversation state is set to inactive, which prevents SENDs or RECEIVEs between the current node and other nodes.

User response:

Examine the exception trace records, and any messages issued before this one, to determine the cause of the problem.

Destination:

Console, job log, EYULOG

Module:

EYU0CLER, EYU0CLEV, EYU0CLCS, EYU0CLCU, EYU0CLMS, EYU0CLRR, EYU0CLRS, EYU0CLRV, EYU0CLRW, EYU0CLSS, EYU0CLST, EYU0CLSV, EYU0CLSW

EYUCL0106E
protocol link to nodename terminated abnormally
Explanation:

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.

System action:

The link conversation state is set to inactive, which prevents SENDs or RECEIVEs between the two nodes.

User response:

Examine the exception trace records, and any messages issued before this one, to determine the cause of the problem.

Destination:

Console, job log, EYULOG

Module:

EYU0CLER, EYU0CLEV, EYU0CLCS, EYU0CLCU, EYU0CLMS, EYU0CLRR, EYU0CLRS, EYU0CLRV, EYU0CLRW, EYU0CLSS, EYU0CLST, EYU0CLSV, EYU0CLSW

EYUCL0107E
protocol ICT attach to nodename failed, reason
Explanation:

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.

System action:

The ICT Attach request is denied. Initialization of the local MAS terminates. A user trace record is written to the CICS trace data set.

User response:

Response depends on the reason given for the failure as follows:

MAS already exists
No action is required. However, some invalid records may remain in the data repository. If you want to clean up the data repository, you should stop and restart the CMAS to which the MAS was trying to connect.
MAS name is invalid
Check the MAS startup job to make sure the CICS system and CICSplex names are correctly specified. If the MAS startup job is correct, then use the CICSSYS and CMASPLEX views to make sure the CICS system and CICSplex have been defined to the data repository.
query parameters
Collect the exception trace records and contact your IBM® Support Center.
Link Conversation Block shortages
Collect the exception trace records and CMAS or MAS job logs and contact your IBM Support Center.
Start of changeadd capability failedEnd of change
Start of changeCollect the exception trace records, CMAS and MAS job logs and contact your IBM Support Center.End of change
Start of changecheck capability failedEnd of change
Start of changeCollect the exception trace records, CMAS and MAS job logs and contact your IBM Support Center.End of change
Start of changeCICS release not supportedEnd of change
Start of changeUpgrade the MAS to a supported version of CICS.End of change
Destination:

Console, job log, EYULOG

Module:

EYU0CLET, EYU0CLRT, EYU0CLST

EYUCL0108E
ESSS ICT detach from nodename failed
Explanation:

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.

System action:

The ICT Detach request is denied.

User response:

Examine the exception trace records issued by EYU0CLET and any messages issued before this one, to determine the cause of the problem.

Destination:

Console, job log, EYULOG

Module:

EYU0CLET

EYUCL0109E
Protocol Services termination failed
Explanation:

An error occurred during an attempting to terminate the Protocol Services subcomponent of the Communications component.

System action:

All other Communications subcomponents attempt an orderly shutdown. A user trace record is written to the CICS trace data set.

User response:

Examine the exception trace records, and any messages issued before this one, to determine the cause of the problem.

Destination:

Console, job log, EYULOG

Module:

EYU0CLTM

EYUCL0110E
ESSS ICT link activation for nodename failed
Explanation:

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.

System action:

Initialization of the MAS terminates.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0CLET

EYUCL0111E
Link Buffer Pool element shortage could not be relieved
Explanation:

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.

System action:

The Communications component terminates.

User response:

Make more virtual storage available and then restart CICSPlex SM.

Destination:

Console, job log, EYULOG

Module:

EYU0CLBL

EYUCL0112E
Protocol Services initialization unable to action
Explanation:

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:

acquire storage
An attempt to acquire CICS/ESA storage was unsuccessful.
query parameters
An attempt to query the Parameter Services subcomponent was unsuccessful.
post ICT ECB
An attempt to post the CMAS Initial Contact Transient (ICT) event control block (ECB) was unsuccessful.
wait on ICT ECB
An attempt to wait on the MAS ECB for ICT processing to finish was unsuccessful.
perform ICT Attach
An attempt to connect the MAS to the CMAS using the Environment Services System Services (ESSS) ICT was unsuccessful.
obtain Initial Contact Element
An attempt to connect the MAS to the CMAS using the Environment Services System Services (ESSS) was unsuccessful due to an Initial Contact Element (EICE) shortage.
System action:

Initialization of the CMAS or MAS terminates.

User response:

Examine the exception trace records, and any messages issued before this one, to determine the cause of the problem.

Destination:

Console, job log, EYULOG

Module:

EYU0CLIN

EYUCL0113E
task terminated abnormally for protocol connection with type nodename
Explanation:

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:

type
Start of changeIdentifies the node to which the link was terminated as a CMAS.End of change
System action:

Protocol services is notified that the link is no longer available. A user trace record is written to the CICS trace data set.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0CLCS, EYU0CLCV, EYU0CLMS, EYU0CLMV, EYU0CLRR, EYU0CLRS, EYU0CLRV, EYU0CLRW, EYU0CLSS, EYU0CLST, EYU0CLSV, EYU0CLSW.

EYUCL0114E
Send Link Manager initiation failed for NetView
Explanation:

The Send Link Manager task, which manages the sending of generic alerts from a CMAS to NetView, could not be initiated.

System action:

The NetView interface is not available. A user trace record is written to the CICS trace data set.

User response:

Collect the exception trace records and contact your IBM Support Center.

Destination:

Console, job log, EYULOG

Module:

EYU0CLNW

EYUCL0115E
Send Link Manager abnormally terminated for NetView
Explanation:

An abnormal condition caused the Send Link Manager task to terminate.

System action:

The NetView interface is no longer available. A user trace record is written to the CICS trace data set.

User response:

Collect the exception trace records and contact your IBM Support Center.

Destination:

Console, job log, EYULOG

Module:

EYU0CLNW

EYUCL0117E
Insufficient ECDSA storage to expand link buffer pool
Explanation:

There is not enough ECDSA storage available to successfully expand the link buffer pool to meet a use request.

System action:

CICSPlex SM terminates. A user trace record is written to the CICS trace data set.

User response:

Rerun the CICS with a larger ECDSA storage area allocation.

Destination:

Console, job log, EYULOG

Module:

EYU0CLBL

EYUCL0118E
Inconsistent CMAS-CMAS definition. Expected cmastype idtype id1, found cmastype idtype id2
Explanation:

While two CMASs were attempting to connect to each other, one of the CMASs determined that their connection definitions are inconsistent, where:

cmastype
Identifies the CMAS that has the inconsistency as either the TARGET or SOURCE of the connection attempt. Either CMAS in the connection attempt can identify and report an inconsistency.
idtype
Indicates whether the inconsistency was in the CICS system ID (SYSID) or the CMAS name (CMAS).
id1
Is the system ID or CMAS name that was expected.
id2
Is the system ID or CMAS name that was found.
System action:

The attempt to connect the two CMASs fails. No communication is possible between the CMASs.

User response:

Use the CMTCMDEF view to correct the inconsistencies in the definitions of the specified CMASs.

Destination:

Console, job log, EYULOG

Module:

EYU0CLCT

EYUCL0119E
A failure occurred while attempting to connect to CMAS cmasname
Explanation:

While attempting to activate a CICSPlex SM connection between this CMAS and another CMAS, a failure has occured, where:

cmasname
Is the name of the other CMAS.
System action:

The connection is not completed.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0CLCT, EYU0CLMT

Start of changeEYUCL0120EEnd of change
Unable to start Communications buffer long-running task
Explanation:

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).

System action:

CICSPlex SM terminates abnormally. A user trace record is written to the CICS trace data set.

User response:

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.

Start of change
Destination:

Console, job log, EYULOG

End of change
Start of change
Module:

EYU0CLIN

End of change
Start of changeEYUCL0121EEnd of change
Communications buffer long-running task terminating due to nonrecoverable error
Explanation:

The communications buffer long running task (LRT) encountered an error from which it could not recover.

System action:

The LRT terminates. CICSPlex SM may continue running without the services of the LRT.

User response:

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.

Start of change
Destination:

Console, job log, EYULOG

End of change
Start of change
Module:

EYU0CSGT

End of change
EYUCL0122E
MAS communications buffer shortage has been detected
Explanation:

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.

System action:

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.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0CTBT

Start of changeEYUCL0123EEnd of change
ESSS ICT entered for STOPCOM from nodename
Explanation:

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.

System action:

The ICT STOPCOM request is processed. No messages are sent from the CMAS to the specified node until the node reconnects to the CMAS.

User response:

Check for error messages in the job log for the specified node and follow the instructions for those messages.

Destination:

Console, job log, EYULOG

Module:

EYU0C

Start of change
EYUCL0124E
A failure occurred while attempting to connect to CMAS cmasname
Explanation:

While attempting to activate a CICSPlex SM connection between this LMAS and a CMAS, a failure has occured, where:

cmasname
Is the name of the CMAS.
System action:

The connection is not completed.

User response:

Refer to the job output of the CMAS for messages that provide more details of the failure.

Destination:

Console, job log

Module:

EYU0CLIN

End of change
Start of change
EYUCL0125E
ESSS ICT encountered an error during CMAS termination
Explanation:

During CMAS termination, EYU0CLET encountered an error while attempting to disconnect active local MASes.

System action:

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    
User response:

Collect the dump, the auxtrace data sets, and the complete job output from the CMAS and contact your IBM support center.

Destination:

Console, job log, EYULOG

Module:

EYU0CLET

End of change
Start of change
EYUCL0130E
Capability of MAS nodename is not lower or equal.
Explanation:

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:

nodename
is the MAS name of a communications node.

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.

System action:

The request to establish a communications link is denied. Initialization of the MAS terminates.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0CLET, EYU0CLRT, EYU0CLST

End of change
Start of change
EYUCL0131E
Resource type mismatch n with MAS nodename is objname
Explanation:

MAS nodename has a version of resource table objname that does not match the version in use by this CMAS where:

nodename
is the MAS name of a communications node.
objname
is the name of a resource table in use by MAS nodename which is at an earlier or later release than that in use by this CMAS.
n
is the number of mismatches detected.

This message can be issued for up to two resource table types.

System action:

See message EYUCL0130E for more information.

User response:

See message EYUCL0130E for more information.

Destination:

Console, job log, EYULOG

Module:

EYU0CLET, EYU0CLRT, EYU0CLST

End of change
Start of changeEYUCL0201IEnd of change
Link Buffer Pool element shortage detected
Explanation:

The protocol services subcomponent has determined that there are no link buffers left in the link buffer pool.

System action:

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.

User response:

None.

Start of change
Destination:

EYULOG

End of change
Module:

EYU0CLBL, EYU0CLBE

[[ Contents Previous Page | Next Page Index ]]