EYUXSnnnn messages

EYUXS0001I
Common Services initialization complete
Explanation:

The Common Services subcomponent has been successfully initialized.

System action:

CICSPlex® SM initialization continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0XSIN, EYU3XSIN

EYUXS0002I
Common Services termination complete
Explanation:

The Common Services subcomponent has been terminated.

System action:

CICSPlex SM termination continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0XSTM, EYU3XSTM

EYUXS0003E
Common Services CEDA Failure: reason
Explanation:

An attempt to dynamically add or remove CICS/ESA resource definitions to the CMAS CSD file has failed, where:

reason
Returns one or more CEDA diagnostic messages that describe the problem.
System action:

Common Services processing terminates and a trace record is written to the CICS® trace data set.

User response:

Follow the instructions provided for the CEDA diagnostic messages.

Destination:

Console, job log, EYULOG

Module:

EYU0XSCS

EYUXS0004E
Journaling was requested however, Journal 25 is not allocated
Explanation:

One or all of the journaling EYUPARM parameters were specified which caused the CMAS to make an attempt to open the journal file. CICS returned responses which indicated that the journal file was not allocated.

System action:

initialization continues. Another attempt will be made to open the journal file when a journal record is about to be written.

User response:

Start of changeEnsure that a JOURNALMODEL definition has been created for Journal 25.End of change

Destination:

EYULOG, console

Module:

EYU0XSIN

EYUXS0005E
Common Services was unable to successfully action Journal 25, Resp1=response1 Resp2=response2
Explanation:

One or all of the journaling EYUPARM parameters were specified which caused the CMAS to make an attempt to perform the indicated action against the journal.

System action:

Processing continues.

User response:

Look up the responses from CICS in the Application reference manual to determine the problem.

Destination:

EYULOG, console

Module:

EYU0XSIN

EYUXS0006W
Common Service was unable to successfully action Journal 25, Resp1=response1 Resp2=response2 Journaling data has been lost
Explanation:

One or all of the journaling EYUPARM parameters were specified which caused the CMAS to make an attempt to perform the indicated action against the journal. Journaling data has been lost as a result of this error.

System action:

Processing continues.

User response:

Look up the responses from CICS in the Application reference manual to determine the problem.

Destination:

EYULOG, console

Module:

EYU0XSJW

Start of change
EYUXS0007E
Extract for exit EYU9XSTR failed, RESP=nn, EIBRCODE=xxxxxxxxxxxx
Explanation:

An error occurred in a CMAS or local MAS while attempting to extract the address of the global area for the CICSPlex SM task recovery task related user exit (TRUE), where:

nn
Is the CICS numeric RESP value
xxxxxxxxxxxx
Is the CICS hexadecimal EIBRCODE
System action:

CICSPlex SM Common Services initialization fails. If the system is a CMAS, an EYUXL001 system dump will be taken, CMAS initialization will fail, and the CMAS will terminate. If the region is a local MAS, an EYUI transaction dump will be taken and the MAS agent initialization will fail.

User response:

Verify that the exit program, EYU9XSTR, is defined and installed in the CMAS or local MAS, and that it resides in a DFHRPL library being used by the CMAS or local MAS. If the error continues after the above is verified, collect as much of the following as possible and contact your IBM Support Center:

Destination:

Console, job log, EYULOG

Module:

EYU0XSIN

End of change
EYUXS0101E
Common Services initialization failed
Explanation:

The Common Services subcomponent could not be initialized.

System action:

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

EYU0XSIN

EYUXS0102W
Common Services termination failed
Explanation:

An error occurred while attempting to terminate the Common Services subcomponent.

System action:

CICSPlex SM termination continues. 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:

EYU0XSTM

Start of change
EYUXS0910I
dump title
Explanation:

This message indicates that an SDUMP has been requested by the CICSPlex SM task recovery exit, EYU9XSTR, executing in a CMAS or local MAS, where:

dump title
Is the title string passed to the system dump routine
System action:

An SVC dump has been requested, containing the current region and the ESSS address space.

User response:

Collect as much of the following as possible and contact your IBM Support Center:

Destination:

Console, job log

Module:

EYU9XSTR

End of change
EYUXS1001I
Interval Timing initialization has started
Explanation:

The Interval Timing subcomponent is being initialized.

System action:

Interval Timing initialization continues.

User response:

None.

Destination:

Console, job log

Module:

EYU9XSTC

EYUXS1002I
Interval Timing initialization complete
Explanation:

The Interval Timing subcomponent has been successfully initialized.

System action:

CICSPlex SM initialization continues.

User response:

None.

Destination:

Console, job log

Module:

EYU9XSTC

EYUXS1003S
Interval Timing unable to attach CICS initialization program
Explanation:

An attempt by the Interval Timing subcomponent to attach DFHSIP, the CICS initialization program, as a subtask was unsuccessful.

System action:

CMAS execution is terminated.

User response:

Check the system log for MVS™ Contents Supervisor messages, which begin with the prefix CSVnnn; these messages should explain the cause of the problem. If the cause of the problem is not apparent, collect the MVS system log and the CMAS job log and contact your IBM Support Center.

Destination:

Console, job log

Module:

EYU9XSTC

EYUXS1004W
Interval Timing queue element shortage detected
Explanation:

The Interval Timing subcomponent has exhausted the queue elements that it uses to receive requests from other components.

System action:

Interval Timing attempts to allocate additional queue elements.

User response:

If the shortage can be relieved, this message is followed by message EYUXS1005I and no user action is required. If the shortage cannot be relieved, report the problem to your IBM Support Center.

Destination:

Console, job log

Module:

EYU9XSTC

EYUXS1005I
Interval Timing queue element shortage relieved
Explanation:

The Interval Timing subcomponent has successfully handled a queue element shortage.

System action:

Processing continues.

User response:

None.

Destination:

Console, job log

Module:

EYU9XSTC

EYUXS1006I
Interval Timing has intercepted abnormal termination
Explanation:

An abnormal termination has occurred in the Interval Timing subcomponent.

System action:

Interval Timing recovery processing is initiated.

User response:

None.

Destination:

Console, job log

Module:

EYU9XSTC

EYUXS1007I
Interval Timing recovery has started
Explanation:

The Interval Timing subcomponent has initiated its recovery processing in response to an abnormal termination.

System action:

Interval Timing takes an SVC dump and attempts to recover from the error.

User response:

None.

Destination:

Console, job log

Module:

EYU9XSTC

EYUXS1008I
Interval Timing recovery complete
Explanation:

The Interval Timing subcomponent has successfully recovered from an abnormal termination.

System action:

Processing continues.

User response:

If an SVC dump was produced by Interval Timing, notify your IBM Support Center.

Destination:

Console, job log

Module:

EYU9XSTC

EYUXS1009S
Interval Timing recovery impossible - control task is terminated
Explanation:

The Interval Timing subcomponent was unable to recover from an abnormal termination.

System action:

Interval Timing takes an SVC dump. CMAS execution is terminated.

User response:

Collect the SVC dump and contact your IBM Support Center.

Destination:

Console, job log

Module:

EYU9XSTC

EYUXS1010S
Interval Timing has detected possible recursive error condition
Explanation:

The Interval Timing recovery routine detected an error condition from which recovery is not possible.

System action:

Interval Timing takes an SVC dump. CMAS execution is terminated.

User response:

Collect the SVC dump and contact your IBM Support Center.

Destination:

Console, job log

Module:

EYU9XSTC

EYUXS1011W
applid Interval Timing could not load the external security manager interface
Explanation:

During initialization, the Interval Timing subcomponent could not load the EYU9XSEC external security manager (ESM) interface, where:

applid
Is the VTAM® application ID of the CMAS.
System action:

Interval Timing initialization continues.

User response:

If you want security to be active in the CMAS, make sure the EYU9XSEC module is contained in the CMAS STEPLIB, the MVS linklist, or the LPA library concatenation.

Destination:

Console, job log

Module:

EYU9XSTC

EYUXS1012S
applid Interval Timing unable to attach the external security manager interface
Explanation:

During initialization, the Interval Timing subcomponent attempted to use an MVS/ESA ATTACH command to start the external security manager (ESM) task and the ATTACH failed, where:

applid
Is the VTAM application ID of the CMAS.
System action:

Interval Timing initialization terminates. CMAS initialization terminates.

User response:

Check the system log for MVS/ESA Contents Supervisor messages, which begin with the prefix CSVnnn; these messages should explain the cause of the problem. If the cause of the problem is not apparent, collect the MVS system log and the CMAS job log and contact your IBM Support Center.

Destination:

Console, job log

Module:

EYU9XSTC

Start of change
EYUXS1013I
Interval Timing detached the external security manager interface
Explanation:

The interval timing subcomponent has quiesced the external security manager interface. CICSPlex SM security services are now no longer available.

System action:

Processing continues.

User response:

None

Destination:

Console, job log

Module:

EYU9XSTC

End of change
Start of change
EYUXS1014I
Task recovery starting for task nnnnn transaction cccc
Explanation:

The CICSPlex SM task recovery TRUE, EYU9XSTR, executing in a CMAS or local MAS, encountered a terminating task that did not go through CICSPlex SM cleanup processing, where:

nnnnn
Is the task number
cccc
Is the transaction ID for the task
System action:

CICSPlex SM cleanup processing will be attempted for the task. The results of this recovery processing will be reported after recovery is complete by message EYUXS1015I or EYUXS1016E.

User response:

The most common causes for a CICSPlex SM task to not go through cleanup processing is if a monitor, interactive debugger, or EYU9WRAM program is being used to "KILL" tasks, either automatically or on demand, or otherwise cause an abnormal termination that does not go through normal CICS HANDLE ABEND processing (for example, issues EXEC CICS ABEND with the CANCEL option). If this message occurs without the benefit of one of the above, or if there is no subsequent EYUXS1015I or EYUXS1016E message to pair with this EYUXS1014I message, then collect as much of the following as possible and contact your IBM Support Center:

Destination:

Console, job log

Module:

EYU9XSTR

End of change
Start of change
EYUXS1015I
Task recovery complete for task nnnnn flags 12345678
Explanation:

The CICSPlex SM task recovery TRUE, EYU9XSTR, executing in a CMAS or local MAS, completed task recovery for a terminating task where:

nnnnn
Is the task number
1
Is Y if recovery successfully unchained the task's CICSPlex SM task work area, N if it did not.
2
Is Y if recovery successfully completed global lock recovery for the task, N if it did not.
3
Is Y if recovery successfully freed a global lock holder element for the task, N if it did not. If ? is displayed for this flag, the ESSS address space was not restarted after applying the PTF for APAR PQ79290.
4
Is Y if recovery successfully freed a global lock waiter element for the task, N if it did not. If ? is displayed for this flag, the ESSS address space was not restarted after applying the PTF for APAR PQ79290.
5
Is Y if recovery successfully completed local lock recovery for the task, N if it did not.
6
Is Y if recovery successfully freed a local lock holder element for the task, N if it did not.
7
Is Y if recovery successfully freed a local lock waiter element for the task, N if it did not.
8
Is N (recovery was successful so no SVC dump was taken for this task).
System action:

CICSPlex SM cleanup processing has completed for the task. The start of this recovery processing has been reported by a previous EYUXS1014I message.

User response:

Please refer to the documentation for partner message EYUXS1014I to determine whether or not the issuing of these messages should be reported to IBM support.

Destination:

Console, job log

Module:

EYU9XSTR

End of change
Start of change
EYUXS1016E
Task recovery in error for task nnnnn flags 12345678
Explanation:

The CICSPlex SM task recovery TRUE, EYU9XSTR, executing in a CMAS or local MAS, encountered at least one error while performing task recovery for a terminated task, where:

nnnnn
Is the task number
1
Is Y if recovery successfully unchained the task's CICSPlex SM task work area, N if it did not.
2
Is Y if recovery successfully completed global lock recovery for the task, N if it did not, or E if the address space was not connected to the ESSS.
3
Is Y if recovery successfully freed a global lock holder element for the task, N if it did not. If ? is displayed for this flag, the ESSS address space was not restarted after applying the PTF for APAR PQ79290.
4
Is Y if recovery successfully freed a global lock waiter element for the task, N if it did not. If ? is displayed for this flag, the ESSS address space was not restarted after applying the PTF for APAR PQ79290.
5
Is Y if recovery successfully completed local lock recovery for the task, N if it did not.
6
Is Y if recovery successfully freed a local lock holder element for the task, N if it did not.
7
Is Y if recovery successfully freed a local lock waiter element for the task, N if it did not.
8
Is Y if a dump was taken because of errors during recovery for the task, S if a dump was requested but suppressed (because a previous dump was taken for this execution of the CMAS or MAS), E if the CMAS or MAS is not connected to the ESSS, or F if a failure occurred taking the dump.
System action:

CICSPlex SM cleanup processing has completed for the task. The first time this message occurs during the execution of the CMAS or MAS, an SVC dump will be requested, along with message EYUXS0910I.

User response:

Collect as much of the following as possible and contact your IBM Support Center:

Destination:

Console, job log

Module:

EYU9XSTR

End of change
Start of change
EYUXS1017E
The controlling task for this region, transaction cccc, is terminating abnormally.
Explanation:

The CICSPlex SM task recovery TRUE, EYU9XSTR, executing in a CMAS or local MAS, determined that the terminating task for which cleanup processing is being performed is the CICSPlex SM controlling task in the region where:

cccc
Is the transaction ID for the task
System action:

An SVC dump will be requested, along with message EYUXS0910I, if one has not already been requested for this task. If the region is a CMAS, it will be cancelled. If the region is a local MAS, it will be disconnected from the ESSS and a restart of the region will be required in order for it to reconnect.

Note:
This message will be preceded by message EYUXS1014I and will be followed by message EYUXS1015I or EYUXS1016E.
User response:

Refer to the documentation for the accompanying EYUXS1015I or EYUXS1016E message, and then restart the region.

Note:
Additional errors (for example, abends) may occur in the region as a result of the cancel (CMAS) or ESSS disconnection (local MAS). These errors are to be expected and should be ignored.
Destination:

Console, job log

Module:

EYU9XSTR

End of change
Start of change
EYUXS1018E
ESSS disconnect failed, RESP nnn.
Explanation:

The CICSPlex SM task recovery TRUE, EYU9XSTR, executing in a local MAS, encountered an invalid return code when requesting that the MAS be disconnected from the ESSS where:

nnn
Is the invalid return code
System action:

Processing continues.

Note:
This message is preceded by message EYUXS1017E.
User response:

Collect as much of the following as possible and contact your IBM Support Center:

Then restart the local MAS.

Destination:

Console, job log

Module:

EYU9XSTR

End of change
Start of change
EYUXS1019W
API resources allocated for task nnnnn, may be orphaned.
Explanation:

The CICSPlex SM task recovery TRUE, EYU9XSTR, executing in a local MAS, is performing cleanup for a task that allocated CICSPlex SM API resources which have not been freed where:

nnnnn
Is the task number
System action:

CICSPlex SM cleanup processing continues. This message will be preceded by message EYUXS1014I and followed by message EYUXS1015I or EYUXS1016E.

User response:

The API resources orphaned reside in the local MAS and in the CMAS to which it is connected. If this message occurs frequently, the local MAS receiving the message and the CMAS to which it is connected should be restarted to release the orphaned resources.

Destination:

Console, job log

Module:

EYU9XSTR

End of change
Start of change
EYUXS1020E
Terminating the MAS agent due to the termination of the task for transaction cccc.
Explanation:

The CICSPlex SM task recovery TRUE, EYU9XSTR, executing in a local MAS, determined that the terminating task for which cleanup processing is being performed is the receive task (transaction COI0) or the status task (transaction COIE), where:

cccc
Is the transaction ID for the task
System action:

An SVC dump will be requested, along with message EYUXS0910I, if one has not already been requested for this task. The MAS agent is then terminated.

User response:

Refer to the documentation for the accompanying EYUXS1015I or EYUXS1016E message, and then restart the region or issue the COLM transaction to restart the MAS agent.

Destination:

Console, job log

Module:

EYU9XSTR

End of change
EYUXS1026E
Security Interface has intercepted abnormal termination CNNNN
Explanation:

An abnormal termination has occurred in the External Security subcomponent, where:

C
is S for a System abend or U for a User abend
NNNN
is the System or User abend code.
System action:

External Security recovery processing is attempted.

User response:

None.

Destination:

Console, job log

Module:

EYU9XSEC

EYUXS1027I
Security Interface recovery has started
Explanation:

The External Security subcomponent has initiated its recovery processing in response to an abnormal termination.

System action:

The External Security Interface takes an SVC dump and attempts to recover from the error.

User response:

None.

Destination:

Console, job log

Module:

EYU9XSEC

EYUXS1028I
Security Interface recovery complete
Explanation:

The External Security subcomponent has successfully recovered from an abnormal termination.

System action:

Processing continues.

User response:

If an SVC dump was produced by the External Security subcomponent, notify your IBM Support Center.

Destination:

Console, job log

Module:

EYU9XSEC

EYUXS1029S
Security Interface recovery impossible. Attempting CMAS termination
Explanation:

The External Security subcomponent was unable to recover from an abnormal termination.

System action:

The External Security subcomponent requests an SVC dump and terminates the CMAS.

User response:

If an SVC dump was produced by the External Security subcomponent, notify your IBM Support Center.

Destination:

Console, job log

Module:

eEYU9XSEC

EYUXS1030S
Security Interface Abend limit reached
Explanation:

The External Security subcomponent detected a possible recursive abnormal termination condition.

System action:

The External Security subcomponent requests an SVC dump and terminates the CMAS.

User response:

If an SVC dump was produced by the External Security subcomponent, notify yourIBM Support Center.

Destination:

Console, job log

Module:

eEYU9XSEC

EYUXS1101I
Interval Timing termination has started
Explanation:

The Interval Timing subcomponent is being terminated.

System action:

Termination of the Interval Timing subcomponent continues.

User response:

None.

Destination:

Console, job log

Module:

EYU9XSTC

EYUXS1102I
Interval Timing termination complete
Explanation:

The Interval Timing subcomponent has been terminated.

System action:

CICSPlex SM termination continues.

User response:

None.

Destination:

Console, job log

Module:

EYU9XSTC

[[ Contents Previous Page | Next Page Index ]]