EYUNXnnnn messages

The following variables are used in EYUNXnnnn messages:

eibrcode
The EIBRCODE= value as returned by CICS®.
respcode
The RESP= value as returned by CICS.
resp2code
The RESP2= value as returned by CICS.

Each message that uses these variables identifies the CICS command that returned them. For descriptions of the values for a particular CICS command, refer to the CICS/ESA System Programming Reference.

EYUNX0001I
addspace PLTPI program starting
Explanation:

The Program List Table Processing Initialization (PLTPI) program for a MAS is being started, where:

addspace
Start of changeIdentifies the MAS as a local (LMAS).End of change
System action:

CICS passes control to the MAS PLTPI program and processing continues.

User response:

None.

Destination:

Console, job log

Module:

EYU9NXSM

Module:

EYU9NXSM, EYU1NXRM

EYUNX0012E
addspace initialization failed
Explanation:

Initialization of a MAS failed in the PLTPI program, where:

addspace
Start of changeIdentifies the MAS as a local (LMAS).End of change
System action:

Control returns to CICS. The CICS system continues to initialize, but it is not known to CICSPlex® SM.

User response:

Refer to the messages preceding this one for details on the cause of the problem.

Destination:

Console, job log, terminal user

Module:

EYU9NXSM, EYU1NXRM

EYUNX0015E
addspace initialization transaction not found
Explanation:

The initialization transaction used on the EXEC CICS START command for a MAS is not defined to the CICS system, where:

addspace
Start of changeIdentifies the MAS as a local (LMAS).End of change
System action:

MAS initialization terminates and control returns to CICS. The CICS system continues to initialize, but it is not known to CICSPlex SM.

User response:

Make sure the transaction and program for the MAS long running task (LRT) are defined in the CSD for this CICS system. The transaction is CONL; the program is EYU9XLEV.

Destination:

Console, job log

Module:

EYU9NXSM, EYU1NXRM

EYUNX0016E
addspace PLTPI program abended
Explanation:

The Program List Table Processing Initialization (PLTPI) program for a MAS terminated abnormally, where:

addspace
Start of changeIdentifies the MAS as a local (LMAS).End of change
System action:

A system dump is taken with a dump code of EYUN and control returns to CICS. The CICS system continues to initialize, but it is not known to CICSPlex SM.

User response:

Refer to the messages preceding this one for details on the cause of the problem.

Destination:

Console, job log

Module:

EYU9NXSM, EYU1NXRM

EYUNX0017E
addspace PLTPI program - CICS error
Explanation:

The Program List Table Processing Initialization (PLTPI) program for a MAS terminated abnormally due to a CICS error.

System action:

Control returns to the CICS HANDLE ABEND routine. A system dump is taken with the dump code assigned by CICS. The CICS system continues to initialize, but it is not known to CICSPlex SM.

User response:

Collect the dump and contact your IBM® Support Center.

Destination:

Console, job log

Module:

EYU9NXSM, EYU1NXRM

EYUNX0018E
Enable Program prgmid failed, EIBRCODE=code
Explanation:

An EXEC CICS ENABLE command was issued to enable the specified program, and it returned an abnormal response, where:

prgmid
Identifies the program that could not be enabled.
code
Value is as returned by CICS.
System action:

A system dump is taken with a dump code of EYUN and control returns to CICS. The CICS system continues to initialize, but it is not known to CICSPlex SM.

User response:

Follow the instructions associated with the EIBRCODE= value for the EXEC CICS ENABLE PROGRAM command. If the problem persists, collect the dump and contact your IBM Support Center.

Destination:

Console, job log

Module:

EYU9NXSM

EYUNX0019E
Extract Exit prgmid failed, EIBRCODE=code
Explanation:

An EXEC CICS EXTRACT EXIT command was issued to obtain the global work area address for the specified program, and it returned an abnormal response. prgmid identifies the program for which an address was requested. The EIBRCODE= value is as returned by CICS.

System action:

A system dump is taken with a dump code of EYUN and control returns to CICS. The CICS system continues to initialize, but it is not known to CICSPlex SM.

User response:

Follow the instructions associated with the EIBRCODE= value for the EXEC CICS EXTRACT EXIT command. If the problem persists, collect the dump and contact your IBM Support Center.

Destination:

Console, job log

Module:

EYU9NXSM, EYU9NXSD

EYUNX0020E
START failed: RESP=respcode RESP2=resp2code
Explanation:

An EXEC CICS START command was issued to start the MAS long running task (LRT), and it returned an abnormal response. The respcode and resp2code values are as returned by CICS.

System action:

A system dump is taken with a dump code of EYUN and control returns to CICS. The CICS system continues to initialize, but it is not known to CICSPlex SM.

User response:

Follow the instructions associated with the respcode and resp2code values for the EXEC CICS START command. If the problem persists, collect the dump and contact your IBM Support Center.

Destination:

Console, job log

Module:

EYU9NXSM, EYU1NXRM

EYUNX0021E
addspace global work area size is larger than 32K
Explanation:

The size of a global work area requested for a MAS is too large, where:

addspace
Start of changeIdentifies the MAS as a local (LMAS).End of change
System action:

A system dump is taken with a dump code of EYUN and control returns to CICS. The CICS system continues to initialize, but it is not known to CICSPlex SM.

User response:

Collect the dump and contact your IBM Support Center.

Destination:

Console, job log

Module:

EYU9NXSM

EYUNX0022E
INQUIRE failed: RESP=respcode RESP2=resp2code
Explanation:

An EXEC CICS INQUIRE SYSTEM command was issued to obtain the CICS release level, and it returned an abnormal response. The respcode and resp2code values are as returned by CICS.

System action:

A system dump is taken with a dump code of EYUN and control returns to CICS. The CICS system continues to initialize, but it is not known to CICSPlex SM.

User response:

Follow the instructions associated with the respcode and resp2code values for the EXEC CICS INQUIRE SYSTEM command. If the problem persists, collect the dump and contact your IBM Support Center.

Destination:

Console, job log

Module:

EYU9NXSM, EYU9NXSD, EYU1NXRM

EYUNX0023E
CICS release cicsrel is not supported
Explanation:

The MAS subcomponent can not be initialized because the version of CICS that is installed is not supported by CICSPlex SM, where cicsrel identifies the release of CICS that was encountered.

System action:

MAS initialization terminates. The CICS system continues to run normally, but it is not known to CICSPlex SM.

User response:

Review the CICSPlex SM installation requirements and install a supported release of CICS.

Destination:

Console, job log

Module:

EYU9NXSM, EYU1NXRM

EYUNX0024E
ASSIGN failed, RESP=respcode RESP2=resp2code
Explanation:

An EXEC CICS ASSIGN command was issued to obtain the CICS SYSID, APPLID, and TERMCODE; it returned an abnormal response. The respcode and resp2code values are as returned by CICS.

System action:

MAS initialization terminates.

User response:

Follow the instructions associated with the respcode and resp2code values for the EXEC CICS ASSIGN command.

Destination:

Console, job log

Module:

EYU9NXSM, EYU1NXRM

EYUNX0026E
WAIT EXTERNAL failed, RESP=respcode RESP2=resp2code
Explanation:

An EXEC CICS WAIT EXTERNAL was issued to delay PLT processing until the MAS initializes and POSTs the ECB. The EXEC CICS WAIT EXTERNAL command failed. The respcode and the resp2code values are returned by CICS.

System action:

MAS PLT processing completes and control is returned to CICS. PLT processing continues while MAS initialization continues.

User response:

Follow the instructions associated with the respcode and resp2code values for the EXEC CICS ATTACH command. If BAS is being used to define and install resources, it is possible that resources may not be available when needed by the various applications. If the problem persists, contact your IBM Support Center.

Destination:

Console, job log

Module:

EYU9NXSM

EYUNX0030I
addspace successfully initiated from terminal termid
Explanation:

A MAS has been successfully started by an operator at the specified terminal, where:

addspace
Start of changeIdentifies the MAS as a local (LMAS).End of change
termid
Identifies the terminal from which the MAS was started.
System action:

MAS initialization continues.

User response:

None.

Destination:

Console, job log, terminal user

Module:

EYU9NXSM, EYU1NXRM

EYUNX0031I
MAS is already initialized
Explanation:

An attempt was made to start a MAS that is already initialized.

System action:

None.

User response:

None.

Destination:

Console, job log, terminal user

Module:

EYU9NXSM, EYU1NXRM

EYUNX0032E
LOAD Program EYU9XLEV failed, RESP2=resp2code
Explanation:

An EXEC CICS LOAD command was issued for the specified program to determine if a CICSPlex SM environment could be established. The LOAD command returned an abnormal response, where:

resp2code
Value is as returned by CICS.
Note:
For systems running CICS/MVS™ 2.1.2, the RESP2 value is the RESP value.
System action:

MAS initialization terminates.

User response:

Follow the instructions associated with the resp2code value for the EXEC CICS LOAD command.

Destination:

Console, job log

Module:

EYU9NXSM

EYUNX0033I
RELEASE Program EYU9XLEV failed, RESP2=resp2code
Explanation:

An EXEC CICS RELEASE command was issued to release the specified program. The RELEASE command returned an abnormal response, where:

resp2code
Value is as returned by CICS.
Note:
For systems running CICS/MVS 2.1.2, the RESP2 value is the RESP value.
System action:

MAS initialization continues.

User response:

None.

Destination:

Console, job log

Module:

EYU9NXSM

Start of change
EYUNX0034I
Name Token Services call failed. RC=code
Explanation:

The MAS agent has attempted to invoke the MVS name token service IEANTRT, but the request has failed with (decimal) return code code.

System action:

MAS agent initialization terminates.

User response:

Check for previous messages to identify the cause of the abend or error that caused the failure. If you cannot identify the cause of the problem, collect the complete job log from the MAS, any dumps that may have been captured, and contact your IBM support center.

Destination:

Console, job log

Module:

EYU9NXSM

End of change
Start of change
EYUNX0035I
Startup aborted. Previous LRT abnormal termination failure.
Explanation:

An attempt was made to initialize the MAS agent in an execution of CICS that previously had a MAS agent that failed to terminate correctly.

System action:

MAS agent initialization terminates.

User response:

The CICS region must be restarted before the MAS agent will initialize.

See the User Response of messages EYUNL0903E and EYUNL0904E, which should precede this message.

Destination:

Console, job log

Module:

EYU9NXSM

End of change
EYUNX0040I
applid Termination task initiated
Explanation:

A request was issued to shut down the specified CICS system. The shutdown transaction has received control and the shutdown process has begun.

System action:

The MAS and CICS system termination processes are begun.

User response:

None.

Destination:

Console, job log

Module:

EYU9NPS2, EYU1NPS2

EYUNX0041E
applid RETRIEVE failed: RESP=respcode, RESP2=resp2code
Explanation:

An EXEC CICS RETRIEVE command was issued to obtain data from the communications area for shutdown of the specified CICS system; the command returned an abnormal response. The respcode and resp2code values are as returned by CICS.

System action:

The shutdown task returns control to CICS. Shutdown of the CICS system is not initiated.

User response:

Follow the instructions associated with the respcode and resp2code values for the EXEC CICS RETRIEVE command.

Destination:

Console, job log

Module:

EYU9NPS2, EYU1NPS2

EYUNX0042E
applid LINK failed: RESP=respcode, RESP2=resp2code
Explanation:

Under CICS/MVS 2.1.2, an EXEC CICS LINK command was issued to pass control for shutdown of the specified CICS system to the CEMT interface; the command returned an abnormal response. The respcode and resp2code values are as returned by CICS.

System action:

The shutdown task returns control to CICS. Shutdown of the CICS system is not initiated.

User response:

Follow the instructions associated with the respcode and resp2code values for the EXEC CICS LINK command.

Destination:

Console, job log

Module:

EYU9NPS2

EYUNX0043E
applid CEMT returned severity level of sevcode
Explanation:

Under CICS/MVS 2.1.2, an EXEC CICS LINK to CEMT for the specified CICS system was successful, but the CEMT command returned the specified severity level code.

System action:

The shutdown task returns control to CICS. Shutdown of the CICS system is not initiated.

User response:

Refer to the discussion of the CEMT programmable interface in the CICS/MVS 2.1.2 Customization Guide for a description of the severity level codes.

Destination:

Console, job log

Module:

EYU9NPS2

EYUNX0044E
applid PERFORM SHUTDOWN failed: RESP=respcode RESP2=resp2code
Explanation:

A PERFORM SHUTDOWN command was issued for the specified CICS system, and it returned an abnormal response. The respcode and resp2code values are as returned by CICS. For CICS/MVS 2.1.2 systems, the resp2code value is zero.

System action:

The shutdown task returns control to CICS. Shutdown of the CICS system is not initiated.

User response:

Follow the instructions associated with the respcode and resp2code values for CEMT PERFORM SHUTDOWN (CICS/MVS 2.1.2) or EXEC CICS PERFORM SHUTDOWN (CICS/ESA 3.3 or later).

Destination:

Console, job log

Module:

EYU9NPS2, EYU1NPS2

EYUNX0045E
applid Shutdown task bad branch value - value
Explanation:

The shutdown task for the specified CICS system received a bad branch value and could not determine what command to execute.

System action:

The shutdown task returns control to CICS. Shutdown of the CICS system is not initiated.

User response:

Collect the job log and contact your IBM Support Center.

Destination:

Console, job log

Module:

EYU9NPS2

Start of change
EYUNX0047E
EXTRACT EXIT failed: RESP=nnnnnn, EIBRCODE=hhhhhh
Explanation:

During processing of an EUI, API, or WUI MAS termination request, module EYU9NPS2 encountered an error when issuing an EXEC CICS EXTRACT command.

System action:

CICS termination is aborted.

User response:

Collect the complete job output and the auxtrace data sets from the MAS and the CMAS it connects to and contact your IBM support center. To terminate the MAS, use CEMT PERFORM SHUTDOWN.

Destination:

Console, job log

Module:

EYU9NPS2

End of change
EYUNX0051I
addspace termination initiated
Explanation:

The MAS shutdown task has been given control by a CICS system that is terminating, where:

addspace
Start of changeIdentifies the MAS as a local (LMAS).End of change
System action:

MAS termination begins and control returns to CICS.

User response:

None.

Destination:

Console, job log

Module:

EYU9NXSD, EYU1NXTM

EYUNX0052I
compid termination ECB posted
Explanation:

The termination ECB for the specified component has been posted; its task will be terminated, where:

compid
Identifies the component as either Kernel Linkage (KNL) or managed application system (MAS).
System action:

MAS termination continues.

User response:

None.

Destination:

Console, job log

Module:

EYU9NXSD, EYU1NXTM

EYUNX0053W
Global area address is zero or invalid
Explanation:

The global work area address that was passed to the MAS shutdown program was zero or invalid.

System action:

The MAS, if active, cannot terminate normally. Control returns to CICS and termination continues.

User response:

If MAS tasks remain active, the CICS system must be either terminated with the IMMEDIATE operand or canceled.

Destination:

Console, job log

Module:

EYU9NXSD

EYUNX0054W
XLWA address is zero or invalid
Explanation:

The Kernel Linkage work area address that was passed to the MAS shutdown program was zero or invalid.

System action:

The MAS, if active, cannot terminate normally. Control returns to CICS and termination continues.

User response:

If MAS tasks remain active, the CICS system must be either terminated with the IMMEDIATE operand or canceled.

Destination:

Console, job log

Module:

EYU9NXSD, EYU1NXTM

EYUNX0055W
MODB list address is zero
Explanation:

The address of the list of major object descriptor block (MODB) addresses that was passed to the MAS shutdown program was zero.

System action:

The MAS, if active, cannot terminate normally. Control returns to CICS and termination continues.

User response:

If MAS tasks remain active, the CICS system must be either terminated with the IMMEDIATE operand or canceled.

Destination:

Console, job log

Module:

EYU9NXSD

EYUNX0058W
ASSIGN failed: RESP=respcode RESP2=respcode2
Explanation:

An EXEC CICS ASSIGN TERMINAL command was issued to obtain the type of terminal associated with the task and it returned an abnormal response. The respcode and resp2code values are as returned by CICS.

System action:

The MAS agent shutdown task returns control to CICS. The MAS agent code will not be terminated.

User response:

The MAS agent code may be stopped by issuing the STOP action from the MAS EUI view or from a CICSPlex SM API program.

Destination:

Console, job log

Module:

EYU9NXTM

EYUNX0060W
compid MODB address is zero or invalid
Explanation:

The major object descriptor block (MODB) address for the specified component is zero or invalid, where compid identifies the component as either Kernel Linkage (KNL) or managed application system (MAS).

System action:

The component tasks are not terminated. Control returns to CICS and termination continues.

User response:

If MAS tasks remain active, the CICS system must be either terminated with the IMMEDIATE operand or canceled.

Destination:

Console, job log

Module:

EYU9NXSD

EYUNX0061W
compid OPB address is zero or invalid.
Explanation:

The major object descriptor block (MODB) for the specified component has an Object Process Block (OPB) address that is zero or invalid, where compid identifies the component as either Kernel Linkage (KNL) or managed application system (MAS).

System action:

The component tasks are not terminated. Control returns to CICS and termination continues.

User response:

If MAS tasks remain active, the CICS system must be either terminated with the IMMEDIATE operand or canceled.

Destination:

Console, job log

Module:

EYU9NXSD

EYUNX0062W
compid ECB address is zero
Explanation:

The Object Process Block (OPB) for the specified component has a termination ECB address that is zero; the ECB cannot be posted, where compid identifies the component as either Kernel Linkage (KNL) or managed application system (MAS).

System action:

The component tasks are not terminated. Control returns to CICS and termination continues.

User response:

If MAS tasks remain active, the CICS system must be either terminated with the IMMEDIATE operand or canceled.

Destination:

Console, job log

Module:

EYU9NXSD

EYUNX0070I
XLWA termination ECB posted
Explanation:

The ECB in the Kernel Linkage (KNL) work area has been posted to indicate that the CICS system is terminating and the MAS is not to be restarted.

System action:

Control returns to CICS and termination of the CICS system and the MAS continues.

User response:

None.

Destination:

Console, job log

Module:

EYU9NXSD, EYU1NXTM

EYUNX0071I
MAS successfully terminated from terminal termid
Explanation:

The MAS agent code has been successfully stopped by an operator running transaction COSH at terminal termid.

System action:

The MAS agent code is stopped. CICS continues to run.

User response:

None.

Destination:

Console, job log, terminal user

Module:

EYU9NXTM

EYUNX0072E
addspace termination from terminal termid failed
Explanation:

An error has occured during MAS termination invoked using transaction COSH, where:

addspace
Start of changeIdentifies the MAS as a local (LMAS).End of change
termid
Identifies the terminal from which the MAS was terminated.

Previous messages indicate the cause of the failure.

System action:

None.

User response:

See previous error messages written to the console and job log.

Destination:

Console, job log, terminal user

Module:

EYU9NXTM

[[ Contents Previous Page | Next Page Index ]]