EYUXLnnnn messages

EYUXL0001I
addspace PLTPI program starting
Explanation:

The startup program for a CICSPlex® SM address space (CMAS) or managed application system (MAS) is being initialized.

System action:

Initialization continues.

User response:

None

Destination:

Console, job log

Module:

EYU9XLCS

EYUXL0002I
CICS TRACE active
Explanation:

The CICSPlex SM address space (CMAS) PLTPI program has determined that CICS internal tracing is active and that user trace entries can be created.

System action:

CMAS initialization continues.

User response:

None.

Destination:

Console, job log

Module:

EYU9XLCS

EYUXL0003I
jobname CPSM Version nnnn comptype startup in progress
Explanation:

A CICSPlex SM component is beginning its initialization process, where:

jobname
Is the job name of the initializing component
nnnn
Is the version of CICSPlex SM under which the component is being initialized (for example, 0130 for Release 3)
comptype
Identifies the component as one of the following:
CMAS
CICSPlex SM address space
LMAS
Local managed application system
System action:

Initialization continues.

User response:

None

Destination:

Start of changeConsole, job log,End of change

Module:

EYU1XLEV, EYU9XLEV

EYUXL0004I
ESSS connection complete
Explanation:

A connection between the Kernel Linkage (KNL) component and the Environment Services System Services (ESSS) has been successfully established.

System action:

CICSPlex SM initialization continues.

User response:

None

Destination:

Console, job log, EYULOG

Module:

EYU9XLEV

EYUXL0005I
Major Object created for component
Explanation:

The specified component has had its load module loaded and its public and private directories created. All basic control blocks for a component have been acquired and formatted, where:

component
Identifies the component as one of the following:
  • Kernel Linkage
  • Trace Services
  • Message Services
  • External Services
  • Common Services
  • Cache Manager
  • Data Repository
  • Queue Manager
  • Communications
  • Topology
  • Monitor Services
  • real-time analysis
  • Workload Manager
  • MAS (Managed Application System)
System action:

Initialization continues.

User response:

None.

Destination:

Console, job log

Module:

EYU1XLBE, EYU9XLBE

EYUXL0006I
component initialization has started
Explanation:

The Kernel Linkage component has requested initialization of the specified component. CICSPlex SM components are initialized in the following order:

System action:

Initialization of the named component begins. Additional messages are issued to record the progress of the component initialization.

User response:

None.

Destination:

EYULOG

Module:

EYU0XLBI, EYU3XLBI, EYU3XLBV, EYU9XLEV

EYUXL0007I
comptype Phase nn initialization complete
Explanation:

A CICSPlex SM component of the specified type has completed one of its initialization phases, where:

Start of changecomptypeEnd of change
Start of changeIdentifies the component that is initializing as one of the following:
CMAS
CICSPlex SM address space
LMAS
Local managed application system
End of change
nn
Indicates which initialization phase has been successfully completed. Depending on the type of address space, anywhere from one to four initialization phases must be completed. This message appears after completion of the following phases:
Phase
Description
II
Initializes all Kernel Linkage subcomponents and establishes a connection to the Environment Services System Services (ESSS).
III
Initializes all CICSPlex SM Base Service components.
IV
Registers all supported CICSplexes with the ESSS address space, attaches an OS task to manage connections to the CAS, and initializes the ISPF EUI selector interface (CMAS only).
System action:

CICSPlex SM initialization continues.

User response:

None.

Destination:

Start of changeConsole, job log, EYULOG.End of change

Module:

EYU1XLEV, EYU9XLEV.

EYUXL0008I
CICSplex registration complete
Explanation:

All CICSplexes managed by the CMAS that is initializing have been registered with Environment Services System Services (ESSS). This message is issued only when a CMAS is being initialized.

System action:

CMAS initialization continues.

User response:

None.

Destination:

Console, job log, EYULOG

Module:

EYU9XLEV

EYUXL0009I
CAS connection established
Explanation:

A connection between a CICSPlex SM address space (CMAS) and a coordinating address space (CAS) has been successfully created.

System action:

All service points to the CAS are attached. The ISPF end-user interface, which is provided by the CAS, is now available.

User response:

None

Destination:

Console, job log

Module:

EYU9XLEC

EYUXL0010I
CMAS initialization complete
Explanation:

A CICSPlex SM address space (CMAS) has been successfully initialized.

System action:

CICSPlex SM initialization continues.

User response:

None.

Destination:

Console, job log, EYULOG

Module:

EYU1XLEV, EYU9XLEV

EYUXL0011I
comptype shutdown in progress
Explanation:

A CICSPlex SM component of the specified type is being shutdown, where comptype identifies the component as one of the following:

Start of changeCMASEnd of change
Start of changeCICSPlex SM address spaceEnd of change
LMAS
Local managed application system
System action:

Shutdown of the specified CICSPlex SM component continues.

User response:

None

Destination:

Console, job log, EYULOG

Module:

EYU1XLEV, EYU9XLEV

EYUXL0012I
ESSS disconnect complete
Explanation:

The connection to the Environment Services System Services (ESSS) address space that was established during CICSPlex SM initialization has been terminated. Disconnection from the ESSS occurs during the normal shutdown of a CICSPlex SM address space (CMAS) or local managed application system (MAS).

System action:

CICSPlex SM shutdown continues. The ESSS address space is no longer available.

User response:

None.

Destination:

Console, job log

Module:

EYU9XLEV

EYUXL0013I
CICSplex registration terminated
Explanation:

All CICSplexes previously registered with this CICSPlex SM address space (CMAS) in the Environment Services System Services (ESSS) are unregistered. No other address space can connect to this CMAS.

System action:

The CMAS continues to executes without any connections to other CICSPlex SM address spaces.

User response:

None.

Destination:

EYULOG

Module:

EYU0XLES

Start of changeEYUXL0014IEnd of change
CAS connection terminated
Explanation:

A connection between a CICSPlex SM address space (CMAS) and a coordinating address space (CAS) has been terminated.

System action:

The ISPF end-user interface, which is provided by the CAS, is no longer available. The CMAS continues to execute.

User response:

If this message occurs before the termination of the CMAS, then this indicates that the CAS address space has terminated. If the ISPF end-user interface is required, the CAS address space should be restarted.

Destination:

Console, job log, EYULOG

Module:

EYU0XLES, EYU9XLEV

EYUXL0015I
component termination requested
Explanation:

The Kernel Linkage component has requested termination of the specified component as part of CICSPlex SM shutdown. CICSPlex SM components are terminated in the following order:

System action:

Termination of the named component begins.

User response:

None.

Destination:

EYULOG

Module:

EYU0XLES, EYU3XLES

EYUXL0016I
addspace shutdown complete
Explanation:

A CICSPlex SM component of the specified type has been successfully shutdown, where:

Start of changeaddspaceEnd of change
Start of changeIdentifies the type of address space as one of the following:
CMAS
CICSPlex SM address space
LMAS
Local managed application system
End of change
System action:

Start of changeThe specified address space no longer exists. If it was a CMASor local MAS, control is returned to CICS.End of change

User response:

None

Destination:

Console, job log

Start of changeConsole, job logEnd of change

Module:

EYU1XLEV, EYU9XLEV

EYUXL0017I
addspace PLTPI program terminating.
Explanation:

The startup program for a CICSPlex SM address space (CMAS) is complete.

System action:

CMAS initialization continues.

User response:

None

Destination:

Console, job log

Module:

EYU9XLCS

EYUXL0018I
comptype restart in progress
Explanation:

A CICSPlex SM component of the specified type is attempting to restart itself after a CICSPlex SM address space (CMAS) shutdown or abend. All CICSPlex SM components have been shutdown and control has been returned to the startup processes of those components, where:

comptype
Start of changeIdentifies the component that is restarting as a local MAS (LMAS).End of change
System action:

The MAS attempts to restart itself and wait for the terminated CMAS to initialize and establish a connection to Environment Services System Services (ESSS).

User response:

None.

Destination:

Start of changeConsole, job logEnd of change

Module:

EYU1XLEV, EYU9XLEV

EYUXL0019I
comptype restart complete
Explanation:

A CICSPlex SM component of the specified type has been successfully restarted and has reestablished its connection to the CICSPlex SM address space (CMAS), where:

comptype
Identifies the component that was restarted as a local MAS (LMAS).
System action:

MAS initialization continues.

User response:

None.

Destination:

EYULOG

Module:

EYU9XLEV

EYUXL0020I
ESSS connection in progress target
Explanation:

As part of initialization, the Kernel Linkage (KNL) subcomponent is attempting to establish a connection between Environment Services System Services (ESSS) and a CMAS or MAS. This connection provides CICSPlex SM with access to certain required MVS™ program call routines, where target identifies the target of the connection. For a CMAS, there is no target information; the CMAS being connected to can be identified by the APPLID in the message prefix. For a MAS, target is one of the following:

to CICSplex(plexname)
The CICSplex specified in the MAS startup parameters, when no CMAS was specified.
to CICSplex(plexname) for SYSID(cmasname)
The CICSplex and CMAS specified in the MAS startup parameters.
System action:

The attempt to establish a connection to ESSS continues. This message is followed by one of two messages indicating the success or failure of the connection attempt: EYUXL0004I indicates the connection was successful, while EYUXL0105E indicates it was not.

Note:
If a connection is being attempted to a CMAS that is not active, no further processing is done until that CMAS becomes available.
User response:

None.

Destination:

Console, job log, EYULOG

Module:

EYU9XLEV

EYUXL0021I
component initialization has started
Explanation:

Initialization of the specified component has begun, where:

component
Identifies the component as one of the following:
  • Trace Services
  • Message Services
System action:

This message is issued by the External Message processor because the Message Services component is not yet active. Initialization continues.

User response:

None.

Destination:

Console, job log

Module:

EYU3XLBV, EYU9XLEV

EYUXL0022I
addspace Phase I initialization complete
Explanation:

An address space of the specified type has completed the first of its initialization phases, which verifies CICSPlex SM requirements and sets up the Major Object Base environment, where:

Start of changeaddspaceEnd of change
Start of changeIdentifies the type of address space that is initializing as one of the following:
CMAS
CICSPlex SM address space
LMAS
Local managed application system
End of change
System action:

CICSPlex SM initialization continues.

User response:

None.

Destination:

Console, job log

Module:

EYU9XLEV

EYUXL0023I
Trace Services termination requested
Explanation:

The Kernel Linkage component has requested termination of Trace Services as part of CICSPlex SM shutdown.

System action:

This message is issued by the external message processor because the Message Services component is no longer active. Trace Services termination begins.

User response:

None.

Destination:

Console, job log

Module:

EYU0XLES, EYU3XLES

EYUXL0024I
Waiting for CICSPlex SM subsystem activation
Explanation:

Initialization of a local MAS was suspended because the Environmental Services System Services (ESSS) subsystem is not yet active. ESSS is initialized by the first CMAS to start up in the MVS image. Message EYUXL0103E is issued before this one.

System action:

Initialization is suspended. The CICS® system remains active but is not known to CICSPlex SM. As long as the CICS system is active, the MAS checks at regular intervals to determine if the ESSS subsystem is active. Once the ESSS subsystem is available, MAS initialization completes.

User response:

Start the CMAS.

Destination:

Console, job log

Module:

EYU9XLBE

EYUXL0025I
Waiting for ESSS for CICSPlex SM release
Explanation:

Initialization of a local MAS was suspended because the release descriptor block (RDB) is not yet available from the CICSPlex SM subsystem (CPSM). The RDB identifies the CICSPlex SM release that is running; it is built during initialization of the first CMAS. Message EYUXL0104E is issued before this one.

System action:

The CICS system continues to run normally, but it is not known to CICSPlex SM. As long as the CICS system is active, the MAS tries at regular intervals to find the RDB. Once the RDB is available, MAS initialization completes.

User response:

None.

Destination:

Console, job log

Module:

EYU9XLBE

EYUXL0026I
Waiting for ESSS to become active for CICSPlex SM release
Explanation:

Initialization of a local MAS was suspended because no Environment Services System Services (ESSS) address space was found to be active for the release of CICSPlex SM identified by the release descriptor block (RDB).

System action:

MAS initialization is suspended until an ESSS address space becomes active.

User response:

Restart the ESSS address space by starting a CMAS.

Destination:

Console, job log

Module:

EYU9XLBE

EYUXL0027I
Automatic Restart request from compid for sysname in plexname issued.
Explanation:

A request was issued to cancel and restart the specified CICS system using the MVS automatic restart manager (ARM), where:

compid
Identifies the component that issued the request as one of the following:
API
Application programming interface.
EUI
ISPF end-user interface, which means the ARMRESTART action was issued from a CICSRGN view.
RTA
real-time analysis, which means the ACTNDEF for a notification condition specified the restart.
sysname
Identifies the CICS system that will be cancelled and restarted.
plexname
Identifies the CICSplex of which the CICS system is a member.
System action:

The automatic restart request is passed to ARM. If the request is accepted and completes successfully, the CICS system is immediately cancelled and automatically restarted.

If the request can not be processed, MVS writes messages to the console and CICSPlex SM writes a user trace record to the CICS trace data set.

User response:

Check the MVS console log to determine if the restart request was successful.

Destination:

Console, job log, EYULOG

Module:

EYU0XLTA

Start of change
EYUXL0029I
ESDUMP value set to value through process.
Explanation:

During CMAS or MAS execution, the value for the ESDUMP EYUPARM has been updated, where:

value
Identifies the value the ESDUMP was set to:
YES
No SVC dumps are suppressed.
NO
Duplicate SVC dumps taken by EYU9XLRV and EYU0XZPT may be suppressed, depending upon the value of the ESDUMPLIMIT EYUPARM.
process
Identifies how the ESDUMP value was updated:
COD0
The update was performed through the COD0 transaction SET command.
CMAS resource table
The update was performed by changing the CMAS resource table through the EUI, API, or WUI.
System action:

Processing continues.

User response:

None

Destination:

EYULOG

Module:

EYU9DBG1, EYU0XLAU

End of change
EYUXL0075W
CMAS/EUI recovery entered.
Explanation:

A failure occurred during processing of an ISPF end-user interface request. The MVS recovery routine was entered.

System action:

Any resources allocated to the end-user interface request are released. MVS diagnostic messages are written to the CMAS job log.

CMAS and end-user interface processing continue, but the ISPF end user may receive unexpected results because of the failure.

User response:

Review the job log for MVS or CMAS-related messages issued before this one. Collect any related messages and a dump of the CMAS address space, and contact your IBM® Support Center.

Destination:

Console, job log

Module:

EYU9XLCI

EYUXL0076W
CMAS STCB corruption detected - STCB will be orphaned
Explanation:

During processing of an ISPF end-user interface request, the CMAS attempted to locate an available server task control block (STCB). The CMAS found an STCB, but it could not be validated; it may have been overwritten.

System action:

The CMAS unchains the STCB at the point of the validation failure. If another STCB cannot be located and validated, a new one is allocated to satisfy the end-user interface request.

User response:

If this problem persists, obtain a dump of the CMAS address space and contact your IBM Support Center.

Destination:

Console, job log

Module:

EYU9XLCI

Start of change
EYUXL0077W
No SVC dumps will be taken because ESDUMP has been set to NEVER through process.
Explanation:

During CMAS or MAS execution, the value for the ESDUMP EYUPARM has been set to NEVER, where:

process
Identifies how the ESDUMP value was updated:
EYUPARM
The update was performed through the ESDUMP EYUPARM.
COD0
The update was performed through the COD0 transaction SET command.
CMAS resource table
The update was performed by changing the CMAS resource table through the EUI, API, or WUI.
System action:

Processing continues. All SVC dumps that would normally be issued by CICSPlex SM in the system will be suppressed.

User response:

Suppression of SVC dumps may affect the ability to debug problems. If a problem occurs with SVC dump suppression active, users may be required to reproduce the problem without SVC dump suppression active before debugging can be performed for the problem. It is strongly recommended by CICSPlex SM service that ESDUMP is not set to NEVER.

Destination:

Console, job log, EYULOG

Module:

EYU0XLBV, EYU9DBG1, EYU0XLAU

End of change
Start of change
EYUXL0090W
PLT Processing continuing while MAS Agent waits to connect to ESSS Subsystem
Explanation:

Processing of the CICS initialization PLT continues but the MAS agent will continue to wait for the CICSplex to be registered with the ESSS subsystem by a starting CMAS.

System action:

The CICS system continues to run normally, but it is not known to CICSPlex SM. When a CMAS registers the CICSplex with the ESSS subsystem, MAS agent initialization will continue.

User response:

Ensure that the CMAS to which the MAS will connect is started. If the functioning of the region depends upon CICSPlex SM facilities (for example, BAS resource installation or WLM routing) it may be desirable to shut down the CICS region until a CMAS can be started.

Destination:

Console, job log

Module:

EYU0XLBV

End of change
EYUXL0100E
No CICS CWA available
Explanation:

The CICS common work area (CWA) is not large enough to contain the CICSPlex SM Kernel Linkage work area, EYURXLWA, which is required for CMAS initialization.

System action:

CMAS initialization terminates.

User response:

The default CWA size is 512 bytes, which is not large enough for EYURXLWA. Make sure WRKAREA=2048 is included as one of the initialization parameters for the CMAS.

Destination:

Console, job log

Module:

EYU9XLCS

EYUXL0101E
Not authorized for TRACE inquires
Explanation:

The CICSPlex SM address space (CMAS) PLTPI program does not have the authorization to issue a required EXEC CICS INQUIRE TRACEDEST or TRACEFLAG command.

System action:

The PLTPI program ends with an error condition, which forces the CMAS to terminate.

User response:

Acquire the necessary authorization and then restart the CMAS initialization job.

Destination:

Console, job log, EYULOG

Module:

EYU9XLCS

EYUXL0102E
Unable to set type option
Explanation:

The CICSPlex SM address space (CMAS) PLTPI program issued an EXEC CICS SET command for the specified trace option, but it received an error code, where:

type
Identifies the option as either TRACEDEST or TRACEFLAG.
System action:

The PLTPI program ends with an error condition, which forces the CMAS to terminate.

User response:

Examine the CICS trace records to determine what caused the EXEC CICS error. Then, restart the CMAS initialization job.

Destination:

Console, job log

Module:

EYU9XLCS

EYUXL0103E
CICSPlex SM subsystem (EYUX) not active
Explanation:

The CICSPlex SM MVS/ESA subsystem entry is not active.

System action:

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

CMAS
CMAS initialization terminates.
Local MAS
The MAS issues message EYUXL0024I and then waits for a CMAS to initialize and restart the ESSS address space.
User response:

The appropriate response depends on what type of address space was being initialized:

CMAS
Make sure the startup JCL is executing program EYU9XECS.
Local MAS
None. MAS initialization continues once the ESSS address space is available.
Destination:

Console, job log

Module:

EYU9XLEV

EYUXL0104E
No ESSS for current CICSPlex SM release
Explanation:

The ESSS address space does not contain an entry for the release of CICSPlex SM that is attempting to initialize.

System action:

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

CMAS
CMAS initialization terminates. CICSPlex SM takes an SVC dump with a dump code of EYUXL001.
Local MAS
The MAS issues message EYUXL0025I and then waits for a CMAS of the required version to initialize and restart the ESSS address space.
User response:

The appropriate response depends on what type of address space was being initialized:

CMAS
Make sure the startup JCL is executing program EYU9XECS.
Local MAS
None. MAS initialization continues once the ESSS address space is available.
Destination:

Console, job log

Module:

EYU9XLEV

EYUXL0105E
ESSS connection failed
Explanation:

An attempt to establish a connection between the Kernel Linkage component and the Environment Services System Services (ESSS) has failed during initialization of an address space in the CICSPlex SM environment.

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:

The trace record indicates the reason for the ESSS connection failure. Depending upon what type of address space was initializing when the failure occurred, take one of the following actions:

CMAS
Make sure the JCL specifies the proper PLTPI program to identify the CMAS to the ESSS.
MAS
If the JCL specifies both a CICSplex and a CMAS, make sure the named CMAS is active.

If the JCL specifies only a CICSplex, make sure the CICSplex exists in at least one CMAS attached to the ESSS.

Destination:

Console, job log, EYULOG

Module:

EYU9XLEV

EYUXL0106E
Unable to acquire CICS storage
Explanation:

An attempt to acquire main storage from the specified storage area has failed, where:

storage
Identifies the storage area as one of the following:
DSA
Dynamic storage area (below the 16MB line)
EDSA
Extended dynamic storage area (above the 16MB line)
System action:

The startup program for the address space that was being initialized ends.

User response:

Determine the cause of the GETMAIN failure by examining the CICS trace records.

Destination:

Console, job log

Module:

EYU1ISTI, EYU1XLBE, EYU1XLEV, EYU1XLOP, EYU9XLBE, EYU9XLEV

EYUXL0107W
Major Object create failed for compid
Explanation:

An attempt to create the specified component has failed, where:

compid
Identifies the component as one of the following:
KNL
Kernel Linkage
TRC
Trace Services
MSG
Message Services
SRV
Common Services
CHE
Data Cache Manager
DAT
Data Repository
QUE
Queue Manager
COM
Communications
TOP
Topology Services
MON
Monitor Services
RTA
real-time analysis
WLM
Workload Manager
MAS
Managed Application System
System action:

CICSPlex SM initialization continues.

User response:

If the component that could not be created is required by the initializing address space, make sure the load module for that component (EYU9xx0x) is in the proper load library.

If the module is in the correct load library and the component still cannot be created, collect the exception trace records and any messages issued before this one and contact your IBM Support Center.

Destination:

Console, job log

Module:

EYU1XLBE, EYU9XLBE

Start of changeEYUXL0108EEnd of change
CICSPlex registration failed
Explanation:

An attempt to register CICSplexes with Environment Services System Services (ESSS) has failed during initialization of a CMAS.

System action:

CMAS initialization continues. CICSPlex SM writes exception trace records to the CICS trace data set and requests an SVC dump. The title of the dump will be similar to the following example:

EYU0XZPT Dump,cmasjobn, cmasname, lpar,CMAS,XLEV,
         tasknum,TRAC,EYU0XLCE,date,time
User response:

Make sure the ESSS and CAS address spaces are active. If both are active and the problem persists, collect the complete job output and auxtrace datasets for the CMAS, along with the dump, and contact your local IBM Support Center.

Destination:

Console, job log, EYULOG

Module:

EYU0XLES, EYU9XLEV

EYUXL0109E
CAS connection failed
Explanation:

An attempt to establish a connection between a CICSPlex SM address space (CMAS) and a coordinating address space (CAS) has failed.

System action:

The EYU9XLEC subtask attached to handle CAS interfacing is ended. Because no communication exists between the CMAS and the CAS, the ISPF end-user interface, which is provided by the CAS, is not available. The CMAS continues to execute.

User response:

Examine the user trace records, and any messages issued prior to this one, to determine the cause of the problem. If the cause cannot be determined, contact your IBM Support Center.

Destination:

Console, job log

Module:

EYU9XLEC

EYUXL0110E
Load failed for module modname
Explanation:

An attempt to load the specified module has failed.

System action:

Processing continues, if possible.

User response:

Examine the user trace records to determine the reason for the load failure.

Destination:

Console, job log

Start of changeConsole, job logEnd of change

Module:

EYU1ISTI, EYU1XLBE, EYU9XLEV

Start of change
EYUXL0111E
ESSS disconnect failed, RESP=response
Explanation:

During orderly shutdown of a CICSPlex SM component, an attempt to disconnect from the Environment Services System Services (ESSS) address space failed.response is the ESSS response code from the disconnect routine.

System action:

CICSPlex SM shutdown continues.

User response:

Examine the user trace records to determine the cause of the disconnection failure. You may need further assistance from IBM to solve this problem. If so, you will need to report the value of response from the message.

Destination:

Console, job log

Module:

EYU9XLEV

End of change
EYUXL0112E
addspace initialization failed
Explanation:

An address space of the specified type could not be initialized, where:

Start of changeaddspaceEnd of change
Start of changeIdentifies the type of address space as one of the following:
CMAS
CICSPlex SM address space
LMAS
Local managed application system
End of change
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 user trace records, and any messages issued before this one, to determine the cause of the problem.

Destination:

Start of changeConsole, job logEnd of change

Module:

EYU1XLEV, EYU9XLEV

EYUXL0113E
Termination of CICSPlex registration failed
Explanation:

An attempt to unregister CICSplexes previously registered with Environment Services System Services (ESSS) has failed during CMAS shutdown.

System action:

CMAS shutdown continues. A user trace record is written to the CICS trace data set.

User response:

Examine the exception trace records to determine the cause of the problem.

Destination:

Console, job log, EYULOG

Module:

EYU0XLES

EYUXL0114E
CAS termination failed
Explanation:

An attempt to terminate the connection between a CMAS and a CAS has failed during CMAS shutdown. The termination may have failed for one of two reasons:

  1. The CAS abended or terminated prematurely
  2. ECBs provided by the CAS during connection are not valid
System action:

CMAS shutdown continues. A user trace record is written to the CICS trace data set. Once CMAS shutdown is complete, all connections to the CAS are broken.

User response:

If this error persists, examine the exception trace records and any related messages to determine the cause of the problem.

Destination:

Console, job log, EYULOG

Module:

EYU0XLES

EYUXL0115E
CMAS initialization transaction not found
Explanation:

An EXEC CICS START TRANID command was issued for the transaction XLEV, by the CMAS PLTPI program EYU9XLCS, but the transaction XLEV could not be found.

System action:

The PLTPI program ends with an error condition, which forces the CMAS to terminate.

User response:

Make sure transaction XLEV is defined in the CSD and that the CMAS PLTPI program EYU9XLCS is being run during PLTPI stage 2 processing (that is EYU9XLCS should appear after the DFHDELIM statement in the CMAS PLTPI).

Destination:

Start of changeConsole, job logEnd of change

Module:

EYU9XLCS

EYUXL0116E
addspace PLTPI program abended
Explanation:

The startup program for a CICSPlex SM address space (CMAS) terminated abnormally.

System action:

Initialization terminates. CICSPlex SM takes a CICS system dump.

User response:

Collect the dump, and any messages issued before this one and contact your IBM Support Center.

Destination:

Console, job log

Module:

EYU9XLCS

Start of change
EYUXL0117E
addspace PLTPI program - reasontext
Explanation:

The startup program for a CICSPlex SM address space (CMAS) terminated.

reasontext identifies the reason for the premature termination as follows:

CICS error
Initialization terminated because of a CICS error
Already started
Both CPSMCONN=CMAS and PLTPI=CM were encountered in the system initialization parameters in effect.
System action:

The currently executing initialization program terminates.

User response:

This depends on the reason for the termination:

CICS error
Examine the messages issued before this one to determine the cause of the CICS error. Correct the problem and restart the job.
Already started
The CMAS was started by another instance of the program EYU9XLCS. Ensure that only one of CPSMCONN or PLTPI is coded in the system initialization parameters.
Destination:

Console, job log

Module:

EYU9XLCS

End of change
EYUXL0118E
PERFORM SHUTDOWN failed: RESP=respcode RESP2=resp2code
Explanation:

A PERFORM SHUTDOWN command was issued during CMAS shutdown, and it returned an abnormal response, where:

respcode
Is the value returned by CICS.
resp2code
Is the value 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 CEMT PERFORM SHUTDOWN (CICS/MVS 2.1.2) or EXEC CICS PERFORM SHUTDOWN (CICS/ESA 3.3 or later). For descriptions of the respcode and resp2code values associated with these commands, refer to the CICS/ESA System Programming Reference.

Destination:

Console, job log

Module:

EYU9XLEV

EYUXL0122E
No XLWA found
Explanation:

The parameters passed to the Kernel Linkage startup program by the PLTPI program did not contain the EYURXLWA control block.

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. CICSPlex SM takes a transaction dump with a dump code of EYUI.
User response:

Make sure the startup JCL is invoking the proper PLTPI program.

Destination:

Console, job log

Module:

EYU1XLEV, EYU9XLEV

EYUXL0123E
name is not a supported CICSPlex SM environment
Explanation:

The parameters passed to the Kernel Linkage startup program by the PLTPI program contained an invalid four-character address space name.

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.

CICSPlex SM initialization is halted with a user ABEND 1000.

User response:

Make sure the startup JCL is invoking the proper PLTPI program.

Destination:

Console, job log

Module:

EYU9XLEV

EYUXL0124E
Parameter block not passed from PLTPI program
Explanation:

The Kernel Linkage startup program could not obtain the parameter block passed by the PLTPI program.

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:

Make sure the startup JCL is invoking the proper PLTPI program.

Destination:

Console, job log

Module:

EYU1XLEV, EYU9XLEV

EYUXL0125E
Not authorized to INQUIRE SYSTEM
Explanation:

The Kernel Linkage startup program is not authorized to issued the EXEC CICS INQUIRE SYSTEM command.

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:

Obtain the required authority and restart the job.

Destination:

Console, job log

Module:

EYU9XLEV

EYUXL0126E
An status CMAS has the same name as this CMAS.
Explanation:

During Environment Services System Services (ESSS) connect processing, the ESSS address space determined that a CMAS with the same name or SYSID as the connecting CMAS was either active or, if inactive, had API applications or local MAS systems connected to it and is therefore encumbered, where:

status
Is either active or encumbered
name
Is either the CMAS name or SYSID

This message follows EYUXL0020I (ESSS connection in progress) and precedes message EYUXL0105E (ESSS connection failed).

System action:

CMAS initialization fails

User response:

Make sure that no two CMASs have the same name and/or SYSID if run on the same MVS image for the same release of CICSPlex SM.

Destination:

Console, Job Log, EYULOG

Module:

EYU0XLBV

EYUXL0127E
addspace restart attempt failed
Explanation:

An attempt to restart a CICSPlex SM component after a CMAS shutdown or abend was not successful, where addspace identifies the type of address space that was attempting to restart as a local MAS (LMAS). A MAS connection to the CMAS cannot be established if, after the CMAS becomes active, it no longer manages the CICSplex to which the MAS needs to connect.

System action:

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

User response:

Make sure the MAS JCL specifies the correct CICSplex and, if appropriate, CMAS.

Destination:

Console, job log, EYULOG

Module:

EYU9XLEV

EYUXL0132I
Notification Services Long Running Task has started.
Explanation:

The Notification Services subcomponent of Kernel Linkage was either initialized as part of CICSPlex SM initialization or was restarted after an abnormal termination.

System action:

Processing continues.

User response:

None.

Destination:

Console, job log, EYULOG

Module:

EYU0XLNX

EYUXL0133I
Notification Services Long Running Task terminated type.
Explanation:

The Notification Services subcomponent of Kernel Linkage has been terminated, where type indicates the type of termination that occurred:

Normally
Notification Services was terminated as part of CICSPlex SM termination.
Abnormally
Notification Services terminated abnormally and will be restarted.
System action:

If Notification Services terminated normally, CICSPlex SM termination continues. If Notification Services terminated abnormally, a user trace record is written to the CICS trace data set and it restarts itself. Message EYUXL0132I is issued when Notification Services has been restarted.

User response:

If Notification Services terminated normally, no action is required. If it terminated abnormally, examine the trace records to determine the cause of the problem.

If Notification Services terminates abnormally and restarts itself repeatedly (as indicated by this message and message EYUXL0132I being issued recursively), then shut down the CMAS. If Notification Services terminates abnormally and restarts itself ten times, the CMAS shuts down automatically. Collect the trace records and the job log and contact your IBM Support Center.

Destination:

Console, job log, EYULOG

Module:

EYU0XLNX

EYUXL0134E
ESSS for current CICSPlex SM release is not active
Explanation:

During CMAS or local MAS initialization, no Environment Services System Services (ESSS) address space was found to be active for the release of CICSPlex SM identified by the release descriptor block (RDB). The CICSPlex SM subsystem (CPSM) and the RDB were found, but the ESSS address space itself had been terminated.

System action:

In the case of a CMAS, initialization terminates.

In the case of a local MAS, initialization is suspended and message EYUXL0026I is issued.

User response:

Restart the ESSS address space by starting a CMAS.

Destination:

Console, job log

Module:

EYU9XLBE

EYUXL0135A
CPSM subsystem (EYUX) or version ESSS still not available. Reply 'C' to terminate wait processing.
Explanation:

During local MAS initialization, module EYU9XLBE has determined that either the CPSM subsystem EYUX or the ESSS address space is not available, where version identifies the ESSS CPSM release.

System action:

The message remains on the console until a reply is received or the EYUX subsystem and/or ESSS become available.

If the proper reply is made, local MAS initialization is terminated with message EYUXL0136E, and CICS initialization continues without the CPSM MAS agent present.

User response:

Start a CMAS of the appropriate release to create the EYUX subsystem and ESSS. When EYU9XLBE detects that the proper environment has been reached, it cancels the message from the console.

If the appropriate CMAS cannot be started, reply 'C' to terminate local MAS initialization and continue with CICS initialization in the region. If a CMAS is started at a later time, the COLM transaction can be used to initialize the CPSM MAS agent in the region.

Destination:

Console, job log

Module:

EYU9XLBE

EYUXL0136E
LMAS initialization is terminating due to operator reply to EYUXL0135A
Explanation:

The operator has replied 'C' to message EYUXL0135A.

System action:

Local MAS initialization is terminated, and CICS initialization continues without the CPSM MAS agent present.

User response:

After a CMAS has been started that the MAS can connect to, issue the COLM transaction to initialize the CPSM MAS agent in the region.

Destination:

Console, job log

Module:

EYU9XLBE

EYUXL0137E
LMAS initialization is terminating due to failure attempting to issue EYUXL0135A
Explanation:

An error has occured attempting to issue message EYUXL0135A.

System action:

Local MAS initialization is terminated, and CICS initialization continues without the CPSM MAS agent present.

User response:

After a CMAS has been started that the MAS can connect to, issue the COLM transaction to initialize the CPSM MAS agent in the region.

Destination:

Console, job log

Module:

EYU9XLBE

EYUXL0138I
EYU9XLOP waiting for workload
Explanation:

This message occurs in a region that has specified EYU9XLOP as the distributed or dynamic routing exit, when that region is not connected to a workload.

System action:

If EYU9XLOP was specified, and there is no workload associated with the region, then any request to CICS that drives the appropriate routing exit causes CICS to invoke EYU9XLOP, which then goes into a wait state. Requests that may drive one of the routing exits include, for example, dynamic and undefined transactions, EXEC CICS START commands, CICS BTS activities, and dynamic program link requests.

User response:

You should ensure that you only specify EYU9XLOP when you have a workload associated with the region. Either:

  1. change the specified routing module, or
  2. associate the region with a workload, then activate WLM in the region by either:
    1. recycling the region, or
    2. stopping and restarting the MAS agent code in the region by issuing a STOp command from the MAS EUI view, then issuing the COLM transaction in the region.
Destination:

Console, job log

Module:

EYU9XLOP

EYUXL0140E
Automatic Restart request not issued for CMAS jobname (cmas), reason: reason. CMAS terminating without restart.
Explanation:

An attempt to perform an automatic restart of the named CMAS failed for the reason given, where:

cmas
is the job name of the failing CMAS.
reason
is the reason why an ARM Restart of the CMAS could not be attempted.
System action:

The CMAS is terminated.

User response:

Perform the recommended actions for any messages which preceded this message and restart the CMAS.

Destination:

Console, job log, EYULOG

Module:

EYU0XLES

Start of change
EYUXL0141E
(tranname transaction definition missing or incorrect
Explanation:

During CMAS or MAS initialization the CICS transaction definition for tranname is not found or does not specify the correct program name.

System action:

Initialization continues, but unpredictable results may occur due to the missing or incorrect transaction definition.

User response:

Ensure that the CSD used by the CMAS or MAS is correct and the appropriate CICSPlex SM definitions have been installed.

Destination:

Console, job log

Module:

EYU9XLBE

End of change
Start of change
EYUXL0142E
CICS Transaction Server CMAS release cmasrelease is different from CICS release cicsrelease. CMAS initialization is terminated.
Explanation:

CMAS initialization has failed because the CMAS and CICS release levels do not match. A CMAS can run only with a CICS Transaction Server at the same release level.

System action:

Initialization terminates.

User response:

Ensure that the CICS Transaction Server CMAS release cmasrelease matches the CICS release cicsrelease.

Destination:

Console, job log

Module:

EYU9XLCS

End of change
EYUXL0143A
MAS agent termination is delayed because the MAS is a ROUTER. Reply 'C' to continue termination.
Explanation:

A request to terminate the MAS agent in the MAS is being delayed because it has been determined that the MAS is functioning as a CPSM WLM routing region (ROUTER). The delay allows the region to continue functioning as a routing region. Once the MAS agent is terminated, the region will no longer function as a routing region until it reconnects to a CMAS.

System action:

MAS agent termination is delayed until a correct response is received for the prompt, the COSH transaction is issued, or the region is terminated.

User response:

When it is safe to terminate the MAS agent in the region, either reply 'C' to the prompt, issue the COSH transaction, or terminate the region. To determine why the MAS agent termination request was made, check for previous error messages in the job log and follow the instructions for those messages.

Destination:

Console, job log

Module:

EYU9XLEV

EYUXL0144I
MAS agent is terminating due to operator reply to EYUXL0143A
Explanation:

The operator has replied correctly to the prompt for message EYUXL0143A.

System action:

MAS agent termination continues.

User response:

None.

Destination:

Console, job log

Module:

EYU9XLEV

EYUXL0145E
MAS agent is terminating due to failure attempting to issue EYUXL0143A
Explanation:

A failure occurred when attempting to issue message EYUXL0143A to delay MAS agent termination.

System action:

After issuing transaction dump code EYUI, MAS agent termination continues.

User response:

Collect from the MAS the complete job output, the dump, the auxtrace data set (if active), and the documentation required by any previous message (for example, EYUNL0905E), then contact your IBM Support Center.

Destination:

Console, job log

Module:

EYU9XLEV

EYUXL0146E
Invalid reply to EYUXL0143A - 'r'
Explanation:

The operator replied incorrectly to the prompt for message EYUXL0143A, where r is the reply entered.

System action:

After issuing this message, message EYUXL0143A is reissued.

User response:

Refer to the instructions for message EYUXL0143A.

Destination:

Console, job log

Module:

EYU9XLEV

EYUXL0147I
MAS agent is terminating due to termination request
Explanation:

While the prompt for message EYUXL0143A was active, the COSH transaction was issued or a request to terminate the region was received.

System action:

The prompt for message EYUXL0143A is cancelled and MAS agent termination continues.

User response:

None.

Destination:

Console, job log

Module:

EYU9XLEV

Start of change
EYUXL0148E
ENABLE PROGRAM cccccccc failed, EIBRCODE=xxxxxxxxxxxx
Explanation:

An error occurred during CMAS initialization while attempting to enable a CICSPlex SM related CICS exit (EXEC CICS ENABLE PROGRAM), where:

cccccccc
Is the name of the exit
xxxxxxxxxxxx
Is the CICS hexadecimal EIBRCODE
System action:

An EYUS transaction dump will be taken and the CMAS initialization will fail.

User response:

Verify that the exit program is defined and installed in the CMAS, that it resides in a DFHRPL library being used by the CMAS, and then restart the CMAS. 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

Module:

EYU9XLCS

End of change
Start of change
EYUXL0149E
EXTRACT EXIT cccccccc failed, EIBRCODE=xxxxxxxxxxxx
Explanation:

An error occurred during CMAS initialization while attempting to extract the global area address for a CICSPlex SM related CICS exit (EXEC CICS EXTRACT EXIT), where:

cccccccc
Is the name of the exit
xxxxxxxxxxxx
Is the CICS hexadecimal EIBRCODE
System action:

An EYUS transaction dump will be taken and the CMAS initialization will fail.

User response:

Verify that the exit program is defined and installed in the CMAS, that it resides in a DFHRPL library being used by the CMAS, and then restart the CMAS. 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

Module:

EYU9XLCS

End of change
Start of change
EYUXL0150E
START EXIT cccccccc failed, EIBRCODE=xxxxxxxxxxxx
Explanation:

An error occurred during CMAS initialization while attempting to start processing for a CICSPlex SM related CICS exit (EXEC CICS ENABLE PROGRAM START), where:

cccccccc
Is the name of the exit
xxxxxxxxxxxx
Is the CICS hexadecimal EIBRCODE
System action:

An EYUS transaction dump will be taken and the CMAS initialization will fail.

User response:

Verify that the exit program is defined and installed in the CMAS, that it resides in a DFHRPL library being used by the CMAS, and then restart the CMAS. 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

Module:

EYU9XLCS

End of change
Start of change
EYUXL0151E
INQUIRE PROGRAM cccccccc failed, EIBRCODE=xxxxxxxxxxxx
Explanation:

An error occurred during CMAS initialization while attempting to inquire on the entry point address for a CICSPlex SM related CICS exit (EXEC CICS INQUIRE PROGRAM), where:

cccccccc
Is the name of the exit
xxxxxxxxxxxx
Is the CICS hexadecimal EIBRCODE
System action:

An EYUS transaction dump will be taken and the CMAS initialization will fail.

User response:

Verify that the exit program is defined and installed in the CMAS, that it resides in a DFHRPL library being used by the CMAS, and then restart the CMAS. 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

Module:

EYU9XLCS

End of change
Start of change
EYUXL0152I
CMAS not avaiable
Explanation:

A CICSPlex SM network task has started but the CMAS is not in a suitable state to complete the initialization of the network task.

This message is normally reported in message EYUCS0009I.

System action:

If possible, the CICSPlex SM network task will be retried after a short delay.

User response:

Check that the CMAS is properly initialized.

Destination:

EYULOG

Module:

EYU9XLOP

End of change
Start of change
EYUXL0153W
EYU9XLOP link task (tran) terminated. Reason (reason).
Explanation:

A CICSPlex SM network task has started but the CMAS is not in a suitable state to complete the initialization of the network task. EYU9XLOP has attempted to properly complete the conversation, but failed to do so.

tran
Identifies the network tasks transaction name
reason
identifies the reason that EYU9XLOP failed to complete the request. It may be one of the following:
  • 1 - Receive failed.
  • 3 - Unexpected data received.
  • 4 - Unexpected data length.
  • 5 - Ring token not found.
  • 6 - Send failed.
  • 7 - Unexpected state.
System action:

System Action: EYU9XLOP terminates. Depending on the error CICS may not free the connection.

User response:

Check that the CMAS is properly initialized.

Destination:

Console, job log

Module:

EYU9XLOP

End of change
EYUXL0200S
Invalid Parameter Table initialization failed
Explanation:

During CMAS or MAS initialization, the internal parameter table could not be initialized.

System action:

Parameter initialization for the CMAS or MAS 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:

EYU0XLPI

EYUXL0201E
EYUPARM Data Set Cannot Be Accessed
Explanation:

During CMAS or MAS initialization, the EYUPARM data set could not be accessed for one of the following reasons:

System action:

Parameter initialization for the CMAS or MAS terminates.

User response:

Make sure the DD statement for EYUPARM is properly specified in the CMAS or MAS startup JCL. Review the DCT requirements in the CICS Transaction Server for z/OS® Installation Guide manual and make any necessary corrections.

Destination:

Console, job log, EYULOG

Module:

EYU0XLPI, EYU1XLPI

EYUXL0202E
EYUPARM Data Set Invalid LRECL
Explanation:

During CMAS or MAS initialization, the logical record length of the EYUPARM data set was found to be invalid. The data set must have a record length of 80.

System action:

Parameter initialization for the CMAS or MAS terminates.

User response:

Make sure the EYUPARM data set and its DD statement specify a logical record length of 80.

Destination:

Console, job log, EYULOG

Module:

EYU0XLPI

EYUXL0203E
EYUPARM Data Set Invalid RECFORM
Explanation:

During CMAS or MAS initialization, the record format of the EYUPARM data set was found to be invalid. The data set must have a record format of fixed (F) or fixed block (FB).

System action:

Parameter initialization for the CMAS or MAS terminates.

User response:

Make sure the EYUPARM data set and its DD statement specify a record format of F or FB.

Destination:

Console, job log, EYULOG

Module:

EYU0XLPI

EYUXL0204E
EYUPARM Data Set Invalid I/O Type
Explanation:

During CMAS or MAS initialization, the disposition of the EYUPARM data set was found to be invalid. EYUPARM must be an input data set.

System action:

Parameter initialization for the CMAS or MAS terminates.

User response:

Make sure the DD statement for EYUPARM is properly specified in the CMAS or MAS startup JCL. Review the DCT requirements in the CICS Transaction Server for z/OS Installation Guide manual and make any necessary corrections.

Destination:

Console, job log, EYULOG

Module:

EYU0XLPI

EYUXL0205D
Parameter Errors have Occurred. Reply 'GO' or 'CANCEL'.
Explanation:

Noncritical errors occurred during CMAS or MAS parameter initialization.

System action:

Parameter initialization pauses and waits for a reply.

User response:

Review the messages issued before this one to determine what types of parameter errors occurred. Then decide if parameter initialization should continue with those errors or be canceled. If you reply ‘GO’, parameter initialization continues. If you reply ‘CANCEL’, parameter initialization is terminated; correct the errors identified in the related messages and rerun the CMAS or MAS startup job.

Destination:

Console, job log, EYULOG

Module:

EYU0XLPI

EYUXL0206E
Invalid parameter name - parmname - parameter bypassed
Explanation:

An invalid parameter name was found during CMAS or MAS parameter initialization, where:

parmname
Identifies the invalid parameter name.
System action:

The invalid parameter name is ignored. This is a noncritical error; parameter initialization for the CMAS or MAS continues. This message is followed by message EYUXL0205D.

User response:

Reply to message EYUXL0205D when it is issued.

Destination:

Console, job log, EYULOG

Module:

EYU0XLPI, EYU1XLPI

EYUXL0207E
Invalid parameter value - value - parameter bypassed
Explanation:

An invalid parameter value was found during CMAS or MAS parameter initialization, where value identifies the invalid parameter value.

System action:

The invalid parameter value is ignored. This is a noncritical error; parameter initialization for the CMAS or MAS continues. This message is followed by message EYUXL0205D.

User response:

Reply to message EYUXL0205D when it is issued.

Destination:

Console, job log, EYULOG

Module:

EYU0XLPI, EYU1XLPI

EYUXL0208E
Invalid parameter statement - parameter
Explanation:

An invalid parameter statement was found during CMAS or MAS parameter initialization. The parameter statement was either too long or not properly delimited, where value identifies the invalid parameter statement.

System action:

The invalid parameter statement is ignored. This is a noncritical error; parameter initialization for the CMAS or MAS continues. This message is followed by message EYUXL0205D.

User response:

Reply to message EYUXL0205D when it is issued.

Destination:

Console, job log, EYULOG

Module:

EYU0XLPI, EYU1XLPI

EYUXL0209I
type Parameters For compid
Explanation:

This is the message header for a parameter list request, where type identifies the type of parameters being listed as SYSTEM, major object descriptor block (MODB), or major object execution parameters (MOEP). For MODB parameters, compid identifies which CICSPlex SM component the parameters are associated with.

System action:

None.

User response:

None.

Destination:

EYULOG

Module:

EYU0XLPR

EYUXL0210I
parameter = value
Explanation:

This message lists a parameter and the value that is currently in effect.

System action:

None.

User response:

None.

Destination:

EYULOG

Module:

EYU0XLPR

EYUXL0211I
CPSM Start Up Parameters
Explanation:

This is the message header for an EYUPARM list and any associated errors.

System action:

None.

User response:

None.

Destination:

Console, job log, EYULOG

Module:

EYU0XLPI, EYU1XLPI

EYUXL0212I
parameter
Explanation:

This message lists a parameter statement as it was found in the EYUPARM input data set during CMAS or MAS parameter initialization.

System action:

If any part of the parameter statement is invalid, this message is followed by the appropriate error message.

User response:

None.

Destination:

Console, job log, EYULOG

Module:

EYU0XLPI, EYU1XLPI

EYUXL0213E
Required Parameter "parameter" not supplied
Explanation:

A required parameter was not found during CMAS or MAS parameter initialization.

System action:

Parameter initialization for the CMAS or MAS terminates.

User response:

Review the parameter requirements in the CICS Transaction Server for z/OS Installation Guide and add the missing parameters to the EYUPARM data set.

Destination:

Console, job log, EYULOG

Module:

EYU0XLPI, EYU1XLPI

EYUXL0214I
Parameter Services initialization complete
Explanation:

The Parameter Services subcomponent has been successfully initialized.

System action:

CICSPlex SM initialization continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0XLPI, EYU1XLPI

EYUXL0215E
Parameter Services initialization failed
Explanation:

The Parameter 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:

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:

EYU0XLPI, EYU1XLPI

Start of change
EYUXL0216I
EYUPARM SET issued by user userid from termid termid : eyuparm = value
Explanation:

A CICSPlex SM EYUPARM has been updated via the COD0 transactions SET request, where:

userid
Is the user ID associated with the terminal running the COD0 transaction.
termid
Is the CICS terminal identifier associated with the COD0 transaction.
eyuparm
Is the CICSPlex SM system parameter (EYUPARM) being updated.
value
Is the name value the EYUPARM is being set to.

If one or both userid and terminal inserts are not available N/A will be displayed for these inserts.

System action:

The specified EYUPARM is updated.

User response:

None. This message is to log a change in the CICSPlex SM system parameter.

Destination:

Console, job log

Module:

EYU9DBG1

End of change
EYUXL0900I
Starting Environment Recovery
Explanation:

The CICSPlex SM recovery routine has been entered as a result of an abend in a CMAS or a MAS.

System action:

The recovery routine attempts to capture and format any relevant diagnostic information. All available information is presented in EYUXL09nn messages that follow this one.

A transaction dump is taken. If a CMAS or local MAS abended and the method that abended was found to be in access register (AR) mode improperly, an SVC dump may also be taken.

User response:

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

Destination:

Console, Job log

Module:

EYU9XLRV

EYUXL0902I
ABEND Outputting Storage Areas
Explanation:

While attempting to capture and format diagnostic information, the CICSPlex SM recovery routine encountered addresses that could not be accessed.

System action:

The recovery routine terminates and no further diagnostic information is presented.

User response:

Follow the instructions in message EYUXL0900I.

Destination:

Console, Job log

Module:

EYU9XLRV

EYUXL0903I
Branch to location ZERO, Using R14 for Offset
Explanation:

A calling program attempted to branch to an invalid address. The CICSPlex SM recovery routine uses the address in register 14 in an attempt to format any relevant diagnostic information.

System action:

The recovery routine begins formatting diagnostic information.

User response:

Follow the instructions in message EYUXL0900I.

Destination:

Console, Job log

Module:

EYU9XLRV

EYUXL0904I
method call-type in AR MODE, Displaying from call
Explanation:

A program was found to be in access register (AR) mode when it should not be, where:

call-type
Indicates whether the problem was found by a calling program (CALL) or a returning program (EXIT).
method
Is displayed only for a call-type of EXIT, and identifies the CICSPlex SM method that detected the problem.
System action:

The recovery routine identifies the problem program and displays its name in message EYUXL0905E.

User response:

Follow the instructions in message EYUXL0900I.

Destination:

Console, Job log

Module:

EYU9XLRV

EYUXL0905E
applid abcode IN method OFFSET nnnnnnnn PSW psw1 psw2 INTC=intcode ILC=len TXCP=addr SCODE=syscode TRAN=tranid TASK=tasknum METHODS=methnames
Explanation:

This message describes the location and conditions of an abend that occurred in CICSPlex SM, where:

applid
VTAM® application ID of the CICS system that abended.
abcode
Four-digit CICS user abend code.
method
CICSPlex SM method that abended.
nnnnnnnn
Offset within the method where the abend occurred.
psw1/psw2
Contents of the PSW at the time of the abend.
intcode
Interrupt code.
len
Length of the instruction.
addr
Address of the last translation exception.
syscode
Three-digit system abend equivalent of the CICS user abend code.
tranid
CICS transaction id.
tasknum
CICS task number.
methnames
names of all CICSPlex SM methods active in the failing task.
System action:

The recovery routine continues to format diagnostic information.

User response:

Follow the instructions in message EYUXL0900I.

Destination:

Console, Job log

Module:

EYU9XLRV

EYUXL0906I
Registers at ABEND
Explanation:

The register contents at the location of the abend have been formatted; this message serves as a header for the content records that follow.

System action:

The recovery routine continues to format diagnostic information. The register contents are displayed in EYUXL0907I messages immediately following this header.

User response:

Follow the instructions in message EYUXL0900I.

Destination:

Console, Job log

Module:

EYU9XLRV

EYUXL0907I
register contents
Explanation:

The name of each register that was formatted is displayed along with its content.

System action:

The recovery routine continues to format diagnostic information.

User response:

Follow the instructions in message EYUXL0900I.

Destination:

Console, Job log

Module:

EYU9XLRV

EYUXL0908I
Storage At ABEND
Explanation:

The contents of storage at the location of the abend have been formatted; this message serves as a header for the content records that follow.

System action:

The recovery routine continues to format diagnostic information. The contents of storage are displayed in EYUXL0909I messages immediately following this header.

User response:

Follow the instructions in message EYUXL0900I.

Destination:

Console, Job log

Module:

EYU9XLRV

EYUXL0909I
+/-nn storage contents
Explanation:

The contents of storage at each of the following locations is displayed:

-20
32 bytes before the PSW
-10
16 bytes before the PSW
+00
Start of the PSW
+10
16 bytes after the PSW
System action:

The formatting of diagnostic information is complete. The recovery routine terminates.

The impact on system processing depends on when the abend occurred:

During CMAS initialization
The CMAS terminates.
During MAS initialization
All MAS agent code is removed from the CICS system. The CICS system continues to initialize, but it is not known to CICSPlex SM.
After CMAS or MAS initialization
CICSPlex SM attempts to return control to the last point of processing before the abend.
User response:

Follow the instructions in message EYUXL0900I.

Destination:

Console, Job log

Module:

EYU9XLRV

EYUXL0910I
dump_title
Explanation:

This message indicates that an SDUMP has been requested by CPSM recovery, where:

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

An SDUMP has been requested, containing the current region, the ESSS Address Space, and cache data spaces for components accessed in the abending task.

User response:

Follow the instructions in message EYUXL0900I.

Destination:

Console, job log

Module:

EYU9XLRV

Start of change
EYUXL0911W
EYU9XLRV dump suppressed because ESDUMP is set to NEVER
Explanation:

A SVC dump that would have been issued by abend recovery module EYU9XLRV has been suppressed because the value of the ESDUMP EYUPARM is NEVER.

System action:

Processing continues.

User response:

Suppression of SVC dumps may affect the ability to debug problems. If a problem occurs with SVC dump suppression active, users may be required to reproduce the problem without SVC dump suppression active before debugging can be performed for the problem. It is strongly recommended by CICSPlex SM service that ESDUMP is not set to NEVER.

Destination:

Console, job log

Module:

EYU9XLRV

End of change
Start of change
EYUXL0912W
EYU9XLRV dump suppressed because ESDUMPLIMIT has been reached
Explanation:

An SVC dump has been requested but the dump has been suppressed because the CICSPlex SM system parameter ESDUMP is set to NO and the number of dumps requested with this program name, abend code, offset and region type (CMAS or MAS) combination exceeds the value specified on the CICSPlex SM system parameter ESDUMPLIMIT.

System action:

Processing continues.

User response:

This is normal and can be ignored unless a new dump is needed. If a new dump is needed, set the ESDUMP parm to YES, reproduce the problem, and then reset ESDUMP back to NO. Refer to the ESDUMP and ESDUMPLIMIT documentation in CICS Transaction Server for z/OS CICSPlex SM Problem Determination Guide Version 3 Release 1

Destination:

Console, job log

Module:

EYU9XLRV

End of change
EYUXL0951E
Exception occurred on mm/dd/yy at hh:mm:ss
Explanation:

This message indicates the date and time at which the abend described in message EYUXL0950E occurred, where:

mm/dd/yy
Is the date when the abend occurred.
hh:mm:ss
Is the time when the abend occurred.
System action:

The recovery routine continues to format diagnostic information.

User response:

Follow the instructions in message EYUXL0900I.

Destination:

Console, Job log, EYULOG

Module:

EYU1XLRV

EYUXL0952E
CPSM DLL module path at offset address
Explanation:

This message identifies the CICSPlex SM dynamic link library (DLL) where the abend occurred, where:

path
Is the full path and file name of the DLL.
address
Is the offset within the DLL where the abend occurred.
System action:

The recovery routine continues to format diagnostic information.

User response:

Follow the instructions in message EYUXL0900I.

Destination:

Console, Job log, EYULOG

Module:

EYU1XLRV

EYUXL0953E
CPSM method name at offset offset
Explanation:

This message identifies the CICSPlex SM method where the abend occurred, where:

name
Is the name of the method.
offset
Is the offset within the method where the abend occurred.
System action:

The recovery routine continues to format diagnostic information.

User response:

Follow the instructions in message EYUXL0900I.

Destination:

Console, Job log, EYULOG

Module:

EYU1XLRV

EYUXL0955I
Registers at ABEND:
Explanation:

The register contents at the location of the abend have been formatted; this message serves as a header for the content records that follow.

System action:

The recovery routine continues to format diagnostic information. The register contents are displayed in EYUXL0956I messages immediately following this header.

User response:

Follow the instructions in message EYUXL0900I.

Destination:

Console, Job log, EYULOG

Module:

EYU1XLRV

EYUXL0956I
CS=cs DS=ds ES=es FS=fs GS=gs SS=ss EIP=eip EAX=eax EBX=ebx ECX=ecx EDX=edx EBP=ebp EDI=edi ESI=esi ESP=esp FLAGS=flags PID=pid TID=tid
Explanation:

The name of each register that was formatted is displayed along with its content. The registers are displayed in logical groups. The first group includes the machine registers, where:

cs
Code segment
ds
Data segment
es
Extra segment
fs
Far segment
gs
General segment
ss
Stack segment

The next group includes the extended (32-bit) registers, where:

eip
Instruction pointer
eax
Extended ax
ebx
Extended bx
ecx
Extended cx
edx
Extended dx
ebp
Base pointer
edi
Destination index
esi
Source index
esp
Stack pointer

The last group includes hardware and operating system registers, where:

flags
Hardware status flags
pid
Operating system process ID
tid
Operating system thread ID
System action:

The recovery routine continues to format diagnostic information.

User response:

Follow the instructions in message EYUXL0900I.

Destination:

Console, Job log, EYULOG

Module:

EYU1XLRV

EYUXL0957I
Stack Len: length Extra Info: data
Explanation:

This message provides additional information about the abend, where:

length
Is the length of the remaining stack.
data
Is additional data that is supplied for some abend codes.
System action:

The recovery routine continues to format diagnostic information.

User response:

Follow the instructions in message EYUXL0900I.

Destination:

Console, Job log, EYULOG

Module:

EYU1XLRV

EYUXL0958I
Exception handled
Explanation:

The CICSPlex SM recovery routine was able to recover from the abend.

System action:

The formatting of diagnostic information is complete. The recovery routine terminates.

User response:

Follow the instructions in message EYUXL0900I.

Destination:

Console, Job log, EYULOG

Module:

EYU1XLRV

EYUXL0999I
XLRV Exiting Successfully
Explanation:

The CICSPlex SM recovery routine (XLRV) has successfully completed processing the abend reported in the previous EYUXL09xx messages.

System action:

None.

User response:

Follow the instructions in message EYUXL0900I.

Destination:

Console, Job log

Module:

EYU9XLRV

[[ Contents Previous Page | Next Page Index ]]