EYUXMnnnn messages

EYUXM0001I
Message Service initialization complete
Explanation:

The Message Services component has been successfully initialized.

System action:

CICSPlex® SM initialization continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0XMIN, EYU3XMIN

EYUXM0002I
Caller method Compid compid SubCompid subcompid Message Number msgnum
Explanation:

A CICSPlex SM method requested a message to be sent, but Message Services was not able to complete the request, where:

method
Identifies the method that called Message Services.
compid
Identifies the component that tried to issue the message.
subcompid
Identifies the subcomponent that tried to issue the message.
msgnum
Is the number of the message that could not be issued.
System action:

The requested message is either not created or not directed to its destination.

User response:

Refer to the related messages issued before this one, including EYUXM0502E, to determine the cause of the problem.

Destination:

EYULOG

Module:

EYU0XMSM

EYUXM0003I
Variable varnum vardata
Explanation:

A CICSPlex SM method requested a message to be sent, but Message Services was not able to complete the request, where:

varnum
Is the number of the message variable.
vardata
Is the data for the message variable.
System action:

The requested message is either not created or not directed to its destination.

User response:

Refer to the related messages issued before this one, including EYUXM0502E, to determine the cause of the problem.

Destination:

EYULOG

Module:

EYU0XMSM

EYUXM0004I
Message Services termination complete
Explanation:

The Message Services component has been terminated.

System action:

The Message Services component is no longer available to issue messages.

User response:

None.

Destination:

Console, job log

Module:

EYU0XMTM, EYU3XMTM

EYUXM0010E
Message Services termination failed
Explanation:

An error occurred while attempting to terminate the Message Services component.

System action:

The Message Services component is no longer available to issue messages. A user trace record is written to the CICS® trace data set.

User response:

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

Destination:

Console, job log

Module:

EYU0XMTM

Start of change
EYUXM0020W
Consolidated message log queue not allocated
Explanation:

During initialization of a MAS, a failure occurred while retrieving the message queue ID for the CMAS to which the MAS is connecting.

System action:

MAS initialization continues.

User response:

Verify that the CMAS is running with the PTF for APAR PK25020. If the PTF is on, then collect the AUXTRACE datasets from the CMAS and the complete JOB output from the CMAS and the MAS and contact your IBM support center.

Destination:

Console, job log, EYULOG

Module:

EYU0XMIN

End of change
Start of change
EYUXM0100I
Consolidated message log long running task started
Explanation:

The EYULOG writing task, XMLT, has successfully started in the CMAS.

System action:

CMAS initialization continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0XMLT

End of change
Start of change
EYUXM0101I
Consolidated message log long running task terminated
Explanation:

The EYULOG writing task, XMLT, has terminated normally in the CMAS.

System action:

CMAS termination continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0XMLT

End of change
Start of change
EYUXM0110W
Consolidated message log not available
Explanation:

During initialization of the EYULOG writing task XMLT, a failure occurred attempting to access the EYULOG.

System action:

CMAS initialization continues. No messages will be written to the EYULOG.

User response:

Collect the AUXTRACE datasets and the complete JOB output from the CMAS and contact your IBM support center.

Destination:

Console, job log, EYULOG

Module:

EYU0XMLT

End of change
Start of change
EYUXM0120E
Consolidated message log long running task terminated abnormally
Explanation:

The EYULOG writing task, XMLT, has terminated abnormally in the CMAS.

System action:

CMAS initialization continues.

User response:

Collect the AUXTRACE datasets and the complete JOB output from the CMAS and contact your IBM support center.

Destination:

Console, job log, EYULOG

Module:

EYU0XMLT

End of change
EYUXM0500E
Component inactive
Explanation:

A CICSPlex SM method requested a message to be sent, but the component to which the message belongs is not active. The component is identified in message EYUXM0002I, which is issued following this message.

System action:

Message Services fails the request.

User response:

Refer to the related messages issued with this one to determine the cause of the problem.

Destination:

Console, job log, EYULOG

Module:

EYU0XMSM

EYUXM0501E
Component message prototype table does not exist for Compid compnum
Explanation:

A CICSPlex SM method requested a message to be sent, but the component to which the message belongs did not register a message table, where compnum is the internal numeric identifier of the component.

System action:

Message Services fails the request.

User response:

Refer to the related messages issued with this one to determine the cause of the problem.

Destination:

Console, job log, EYULOG

Module:

EYU0XMSM

EYUXM0502E
Caller method has issued a message with a type value not defined
Explanation:

A CICSPlex SM method issued a message and a required piece of information was not defined, where:

type
Identifies the required information as one of the following:
Compid
component identifier
SubCompid
subcomponent identifier
Message Number
Numeric message identifier
Class
Destination class
value
Is the supplied value that could not be found.
System action:

The requested message is either not created or not directed to its destination.

User response:

Refer to the related messages issued with this one to determine the cause of the problem.

Destination:

Console, job log, EYULOG

Module:

EYU0XMSM

EYUXM0503E
Stack Overflow. Message text not completed.
Explanation:

A Message Services internal stack was exhausted and the requested message could not be created.

System action:

The message is not sent. Message Services processing continues.

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:

EYU0XMSM

EYUXM0504E
Premature UnStack issued. Message text not completed.
Explanation:

A request was made to save a Message Services internal stack and the stack was empty. The requested message could not be created.

System action:

The message is not sent. Message Services processing continues.

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:

EYU0XMSM

[[ Contents Previous Page | Next Page Index ]]