EYUCSnnnn messages

The following variables are used in EYUCSnnnn messages:

Start of changemodeEnd of change
Start of changeIdentifies the communications mode that is used on the communications connection as either Standard or Enhanced. The communications mode is determined automatically by the link set services subcomponent and cannot be controlled by the user.End of change
Start of changetextEnd of change
Start of changeA message received from a partner system. Consult theMessages and Codes manual for a description of this message.End of change
type
Identifies the type of communications connection that has been assigned as one of the following:
Start of change
CPI-C network
CMAS-to-CMAS connection using CPI-C (LU6.2) transmission protocol
MRO network
CMAS-to-CMAS connection using MRO transmission protocol
Netview endpoint
CMAS-to-Netview connection using the Netview PPI link
End of change
name
The name of the communications partner.
EYUCS0001I
Link Set Services initialization complete
Explanation:

The link set 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:

EYU0CSIN

EYUCS0002I
Communications long-running task initialization has started
Explanation:

The Communications long running task (LRT) is being initialized.

System action:

Initialization of the Communications LRT continues.

User response:

None

Destination:

EYULOG

Module:

EYU0CSLT

EYUCS0003I
Communications long-running task initialization complete
Explanation:

The Communications long running task (LRT) has been successfully initialized.

System action:

The Communications component continues to initialize its other subcomponents.

User response:

None

Destination:

EYULOG

Module:

EYU0CSLT

EYUCS0004I
Communications long-running task termination has started
Explanation:

The Communications long running task (LRT) is being terminated.

System action:

Termination of the Communications LRT continues.

User response:

None

Destination:

EYULOG

Module:

EYU0CSLT

EYUCS0005I
Communications long-running task termination complete
Explanation:

The Communications long running task (LRT) has been terminated.

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 EYUCS0104E preceding this message), CICSPlex SM should be shut down and restarted.

Destination:

EYULOG

Module:

EYU0CSLT

EYUCS0006I
type connection name assigned to link set
Explanation:

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.

System action:

The connection becomes available to other CICSPlex SM communications processes.

User response:

None.

Destination:

EYULOG

Module:

EYU0CSAC

EYUCS0007I
type connection name unassigned from link set
Explanation:

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.

System action:

The connection is no longer available to other CICSPlex SM communications processes.

User response:

None.

Destination:

EYULOG

Module:

EYU0CSUC

EYUCS0008I
Service request block element shortage relieved
Explanation:

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.

System action:

Any communications processes waiting for an element are dispatched and permitted to acquire one.

User response:

None.

Destination:

EYULOG

Module:

EYU0CSES

Start of change
EYUCS0009I
Message received from CMAS name : text
Explanation:

An message had been received from the partner CMAS during the connection initialization process. See EYUCSnnnn messagesfor the meaning of name and text.

System action:

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.

User response:

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

Destination:

EYULOG

Module:

EYU0CLCS, EYU0CLMS

End of change
Start of change
EYUCS0010I
mode type to CMAS name being initialized
Explanation:

A communications connection between the local CMAS and a partner CMAS is starting. See EYUCSnnnn messages for the meaning of mode, type and name.

System action:

The communications connection continues to initialize.

User response:

None

Destination:

EYULOG

Module:

EYU0CLCS, EYU0CLMS

End of change
Start of change
EYUCS0011W
The value of EYUPARM parmname was specified less than 10 seconds. This value has been set to 10 seconds for this execution of the CMAS.
Explanation:

The indicated EYUPARM was set to a non-zero value less than 10 seconds.

System action:

The value for the indicated EYUPARM is set to 10 seconds and CMAS initialization continues.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0CSLT

End of change
Start of change
EYUCS0012W
Request timeout EYUPARM eyuparm has been set less than timeout polling EYUPARM TOPOLLINT
Explanation:

The indicated EYUPARM has been given a value that is less than the TOPOLLINT EYUPARM. While this is allowed, it is not efficient.

System action:

CMAS initialization continues.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0CSLT

End of change
EYUCS0101E
Link Set Services initialization failed
Explanation:

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

System action:

CICSPlex SM initialization terminates abnormally. 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:

EYU0CSIN

EYUCS0102E
Unable to create Link Set Pending Connections List
Explanation:

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.

System action:

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

User response:

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

Destination:

Console, job log, EYULOG

Module:

EYU0CSLT

EYUCS0103E
Unable to start Communications long-running task
Explanation:

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

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

Destination:

Console, job log, EYULOG

Module:

EYU0CSIN

EYUCS0104E
Communications long-running task terminating due to nonrecoverable error
Explanation:

The Communications 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™ dump output, if available, and contact your IBM Support Center.

Destination:

Console, job log, EYULOG

Module:

EYU0CSLT

EYUCS0105E
Unable to assign link set for type connection name
Explanation:

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.

System action:

CICSPlex SM attempts to assign the connection again at periodic intervals.

User response:

If the problem persists, collect any exception trace records and the job log and contact your IBM Support Center.

Destination:

Console, job log, EYULOG

Module:

EYU0CSAC

EYUCS0106E
Unable to unassign link set for type connection name
Explanation:

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.

System action:

The connection cannot be used by other CICSPlex SM communications processes. A user trace record is written to the CICS trace data set.

User response:

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

Destination:

Console, job log, EYULOG

Module:

EYU0CSUC

EYUCS0107E
Service request block element shortage could not be relieved
Explanation:

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.

System action:

Any communications processes waiting for an element receive an indication of the failure.

User response:

Allocate additional storage to the CICS extended dynamic storage area (EDSA).

Destination:

Console, job log, EYULOG

Module:

EYU0CSES

Start of change
EYUCS0108E
The initialization wait for CMAS connections to complete has terminated before all connections have completed
Explanation:

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.

System action:

CMAS initialization continues after a system dump is requested and an exception trace record is written to the CICS trace data set.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0CSLT

End of change
EYUCS0201W
NetView PPI module could not be loaded - NetView support unavailable
Explanation:

The Communications long running task (LRT) was not able to load the NetView® PPI module, CNMNETV.

System action:

CICSPlex SM continues running with NetView support disabled.

User response:

Determine why CNMNETV could not be loaded and correct the problem.

Destination:

Console, job log, EYULOG

Module:

EYU0CSLT

EYUCS0202W
NetView release incompatible - NetView support unavailable
Explanation:

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.

System action:

CICSPlex SM continues running with NetView support disabled.

User response:

Review the CICSPlex SM installation requirements and install a supported release of NetView on the system.

Destination:

Console, job log, EYULOG

Module:

EYU0CSLT

EYUCS0203W
Service request block element shortage detected
Explanation:

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.

System action:

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.

User response:

None.

Destination:

Console, job log, EYULOG

Module:

EYU0CSES

EYUCS0204W
A timeout has occurred with CMAS cmasname
Explanation:

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.

System action:

The communications link between the local CMAS and the specified CMAS is terminated.

User response:

Check the job log of the specified CMAS for messages that may indicate the cause of the problem.

Destination:

Console, job log, EYULOG

Module:

EYU0CSLT

Start of change
EYUCS0205W
Connection to CMAS name being retried due to : reason
Explanation:

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:

Initialization version reset
This occurs when an enhanced connection is attempted by the first speaker, but the partner system has responded in such a manner that indicates that it will accept only the standard connection method.
Session Allocation failure
This may occur only on a CPI-C connection. The CPI-C protocol services have returned a response to the initial connection allocation request that implies that, although a failure has occurred, it is not necessarily severe and may be retried. The CICSPlex SM connection process may retry the CPI-C allocate up to fifteen times before it considers the connection unserviceable.
Partner System request
This may occur when either of the CMAS partners recognize a temporary processing issue that cannot be resolved at the point of execution (that is, a resource lock required by the local connection process has been withheld). In these situations, the local system may reject the connection request with an indication that it may be retried after a short period of time (typically two minutes). The partner CMAS issues the message and then waits for the instructed period before retrying the connection.
System action:

The CMAS-to-CMAS connection is retried.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0CLCS, EYU0CLMS

End of change
Start of change
EYUCS0206W
Exception trace issued: Point Id=tracepoint, Debug text=debug
Explanation:

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.

System action:

The CMAS terminates the connection to the partner system.

User response:

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.

Destination:

EYULOG via message EYUCS0009I

Module:

EYU0CLCT, EYU0CLMT

End of change
Start of change
EYUCS0207I
Connected MAS masname is not responding - APPLID(masappl) CICSplex(plexname)
Explanation:

The CMAS has determined that the connected MAS specified is not responding to requests sent to it by the CMAS.

System action:

This message is issued and processing continues.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0CSLT

End of change
Start of change
EYUCS0208I
Connected MAS masname is now responding - APPLID(masappl) CICSplex(plexname)
Explanation:

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.

System action:

This message is issued and processing continues.

User response:

None.

Destination:

Console, job log, EYULOG

Module:

EYU0CSLT

End of change [[ Contents Previous Page | Next Page Index ]]