The startup program for a CICSPlex® SM address space (CMAS) or managed application system (MAS) is being initialized.
Initialization continues.
None
Console, job log
EYU9XLCS
The CICSPlex SM address space (CMAS) PLTPI program has determined that CICS internal tracing is active and that user trace entries can be created.
CMAS initialization continues.
None.
Console, job log
EYU9XLCS
A CICSPlex SM component is beginning its initialization process, where:
Initialization continues.
None
Console, job log,
EYU1XLEV, EYU9XLEV
A connection between the Kernel Linkage (KNL) component and the Environment Services System Services (ESSS) has been successfully established.
CICSPlex SM initialization continues.
None
Console, job log, EYULOG
EYU9XLEV
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:
Initialization continues.
None.
Console, job log
EYU1XLBE, EYU9XLBE
The Kernel Linkage component has requested initialization of the specified component. CICSPlex SM components are initialized in the following order:
Initialization of the named component begins. Additional messages are issued to record the progress of the component initialization.
None.
EYULOG
EYU0XLBI, EYU3XLBI, EYU3XLBV, EYU9XLEV
A CICSPlex SM component of the specified type has completed one of its initialization phases, where:
CICSPlex SM initialization continues.
None.
Console, job log, EYULOG.
EYU1XLEV, EYU9XLEV.
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.
CMAS initialization continues.
None.
Console, job log, EYULOG
EYU9XLEV
A connection between a CICSPlex SM address space (CMAS) and a coordinating address space (CAS) has been successfully created.
All service points to the CAS are attached. The ISPF end-user interface, which is provided by the CAS, is now available.
None
Console, job log
EYU9XLEC
A CICSPlex SM address space (CMAS) has been successfully initialized.
CICSPlex SM initialization continues.
None.
Console, job log, EYULOG
EYU1XLEV, EYU9XLEV
A CICSPlex SM component of the specified type is being shutdown, where comptype identifies the component as one of the following:
Shutdown of the specified CICSPlex SM component continues.
None
Console, job log, EYULOG
EYU1XLEV, EYU9XLEV
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).
CICSPlex SM shutdown continues. The ESSS address space is no longer available.
None.
Console, job log
EYU9XLEV
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.
The CMAS continues to executes without any connections to other CICSPlex SM address spaces.
None.
EYULOG
EYU0XLES
A connection between a CICSPlex SM address space (CMAS) and a coordinating address space (CAS) has been terminated.
The ISPF end-user interface, which is provided by the CAS, is no longer available. The CMAS continues to execute.
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.
Console, job log, EYULOG
EYU0XLES, EYU9XLEV
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:
Termination of the named component begins.
None.
EYULOG
EYU0XLES, EYU3XLES
A CICSPlex SM component of the specified type has been successfully shutdown, where:
The specified address space no longer exists. If it was a CMASor
local MAS, control is returned to CICS.
None
Console, job log
Console, job log
EYU1XLEV, EYU9XLEV
The startup program for a CICSPlex SM address space (CMAS) is complete.
CMAS initialization continues.
None
Console, job log
EYU9XLCS
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:
The MAS attempts to restart itself and wait for the terminated CMAS to initialize and establish a connection to Environment Services System Services (ESSS).
None.
Console, job log
EYU1XLEV, EYU9XLEV
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:
MAS initialization continues.
None.
EYULOG
EYU9XLEV
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:
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.
None.
Console, job log, EYULOG
EYU9XLEV
Initialization of the specified component has begun, where:
This message is issued by the External Message processor because the Message Services component is not yet active. Initialization continues.
None.
Console, job log
EYU3XLBV, EYU9XLEV
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:
CICSPlex SM initialization continues.
None.
Console, job log
EYU9XLEV
The Kernel Linkage component has requested termination of Trace Services as part of CICSPlex SM shutdown.
This message is issued by the external message processor because the Message Services component is no longer active. Trace Services termination begins.
None.
Console, job log
EYU0XLES, EYU3XLES
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.
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.
Start the CMAS.
Console, job log
EYU9XLBE
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.
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.
None.
Console, job log
EYU9XLBE
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).
MAS initialization is suspended until an ESSS address space becomes active.
Restart the ESSS address space by starting a CMAS.
Console, job log
EYU9XLBE
A request was issued to cancel and restart the specified CICS system using the MVS automatic restart manager (ARM), where:
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.
Check the MVS console log to determine if the restart request was successful.
Console, job log, EYULOG
EYU0XLTA
During CMAS or MAS execution, the value for the ESDUMP EYUPARM has been updated, where:
Processing continues.
None
EYULOG
EYU9DBG1, EYU0XLAU
A failure occurred during processing of an ISPF end-user interface request. The MVS recovery routine was entered.
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.
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.
Console, job log
EYU9XLCI
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.
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.
If this problem persists, obtain a dump of the CMAS address space and contact your IBM Support Center.
Console, job log
EYU9XLCI
During CMAS or MAS execution, the value for the ESDUMP EYUPARM has been set to NEVER, where:
Processing continues. All SVC dumps that would normally be issued by CICSPlex SM in the system will be suppressed.
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.
Console, job log, EYULOG
EYU0XLBV, EYU9DBG1, EYU0XLAU
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.
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.
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.
Console, job log
EYU0XLBV
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.
CMAS initialization terminates.
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.
Console, job log
EYU9XLCS
The CICSPlex SM address space (CMAS) PLTPI program does not have the authorization to issue a required EXEC CICS INQUIRE TRACEDEST or TRACEFLAG command.
The PLTPI program ends with an error condition, which forces the CMAS to terminate.
Acquire the necessary authorization and then restart the CMAS initialization job.
Console, job log, EYULOG
EYU9XLCS
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:
The PLTPI program ends with an error condition, which forces the CMAS to terminate.
Examine the CICS trace records to determine what caused the EXEC CICS error. Then, restart the CMAS initialization job.
Console, job log
EYU9XLCS
The CICSPlex SM MVS/ESA subsystem entry is not active.
The impact on system processing depends on what type of address space was being initialized:
The appropriate response depends on what type of address space was being initialized:
Console, job log
EYU9XLEV
The ESSS address space does not contain an entry for the release of CICSPlex SM that is attempting to initialize.
The impact on system processing depends on what type of address space was being initialized:
The appropriate response depends on what type of address space was being initialized:
Console, job log
EYU9XLEV
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.
The impact on system processing depends on what type of address space was being initialized:
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:
If the JCL specifies only a CICSplex, make sure the CICSplex exists in at least one CMAS attached to the ESSS.
Console, job log, EYULOG
EYU9XLEV
An attempt to acquire main storage from the specified storage area has failed, where:
The startup program for the address space that was being initialized ends.
Determine the cause of the GETMAIN failure by examining the CICS trace records.
Console, job log
EYU1ISTI, EYU1XLBE, EYU1XLEV, EYU1XLOP, EYU9XLBE, EYU9XLEV
An attempt to create the specified component has failed, where:
CICSPlex SM initialization continues.
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.
Console, job log
EYU1XLBE, EYU9XLBE
An attempt to register CICSplexes with Environment Services System Services (ESSS) has failed during initialization of a CMAS.
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
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.
Console, job log, EYULOG
EYU0XLES, EYU9XLEV
An attempt to establish a connection between a CICSPlex SM address space (CMAS) and a coordinating address space (CAS) has failed.
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.
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.
Console, job log
EYU9XLEC
An attempt to load the specified module has failed.
Processing continues, if possible.
Examine the user trace records to determine the reason for the load failure.
Console, job log
Console, job log
EYU1ISTI, EYU1XLBE, EYU9XLEV
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.
CICSPlex SM shutdown continues.
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.
Console, job log
EYU9XLEV
An address space of the specified type could not be initialized, where:
The impact on system processing depends on what type of address space was being initialized:
Examine the user trace records, and any messages issued before this one, to determine the cause of the problem.
Console, job log
EYU1XLEV, EYU9XLEV
An attempt to unregister CICSplexes previously registered with Environment Services System Services (ESSS) has failed during CMAS shutdown.
CMAS shutdown continues. A user trace record is written to the CICS trace data set.
Examine the exception trace records to determine the cause of the problem.
Console, job log, EYULOG
EYU0XLES
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:
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.
If this error persists, examine the exception trace records and any related messages to determine the cause of the problem.
Console, job log, EYULOG
EYU0XLES
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.
The PLTPI program ends with an error condition, which forces the CMAS to terminate.
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).
Console, job log
EYU9XLCS
The startup program for a CICSPlex SM address space (CMAS) terminated abnormally.
Initialization terminates. CICSPlex SM takes a CICS system dump.
Collect the dump, and any messages issued before this one and contact your IBM Support Center.
Console, job log
EYU9XLCS
The startup program for a CICSPlex SM address space (CMAS) terminated.
reasontext identifies the reason for the premature termination as follows:
The currently executing initialization program terminates.
This depends on the reason for the termination:
Console, job log
EYU9XLCS
A PERFORM SHUTDOWN command was issued during CMAS shutdown, and it returned an abnormal response, where:
The shutdown task returns control to CICS. Shutdown of the CICS system is not initiated.
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.
Console, job log
EYU9XLEV
The parameters passed to the Kernel Linkage startup program by the PLTPI program did not contain the EYURXLWA control block.
The impact on system processing depends on what type of address space was being initialized:
Make sure the startup JCL is invoking the proper PLTPI program.
Console, job log
EYU1XLEV, EYU9XLEV
The parameters passed to the Kernel Linkage startup program by the PLTPI program contained an invalid four-character address space name.
The impact on system processing depends on what type of address space was being initialized:
CICSPlex SM initialization is halted with a user ABEND 1000.
Make sure the startup JCL is invoking the proper PLTPI program.
Console, job log
EYU9XLEV
The Kernel Linkage startup program could not obtain the parameter block passed by the PLTPI program.
The impact on system processing depends on what type of address space was being initialized:
Make sure the startup JCL is invoking the proper PLTPI program.
Console, job log
EYU1XLEV, EYU9XLEV
The Kernel Linkage startup program is not authorized to issued the EXEC CICS INQUIRE SYSTEM command.
The impact on system processing depends on what type of address space was being initialized:
Obtain the required authority and restart the job.
Console, job log
EYU9XLEV
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:
This message follows EYUXL0020I (ESSS connection in progress) and precedes message EYUXL0105E (ESSS connection failed).
CMAS initialization fails
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.
Console, Job Log, EYULOG
EYU0XLBV
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.
MAS initialization terminates. The CICS system continues to execute normally, but it is not known to CICSPlex SM.
Make sure the MAS JCL specifies the correct CICSplex and, if appropriate, CMAS.
Console, job log, EYULOG
EYU9XLEV
The Notification Services subcomponent of Kernel Linkage was either initialized as part of CICSPlex SM initialization or was restarted after an abnormal termination.
Processing continues.
None.
Console, job log, EYULOG
EYU0XLNX
The Notification Services subcomponent of Kernel Linkage has been terminated, where type indicates the type of termination that occurred:
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.
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.
Console, job log, EYULOG
EYU0XLNX
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.
In the case of a CMAS, initialization terminates.
In the case of a local MAS, initialization is suspended and message EYUXL0026I is issued.
Restart the ESSS address space by starting a CMAS.
Console, job log
EYU9XLBE
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.
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.
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.
Console, job log
EYU9XLBE
The operator has replied 'C' to message EYUXL0135A.
Local MAS initialization is terminated, and CICS initialization continues without the CPSM MAS agent present.
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.
Console, job log
EYU9XLBE
An error has occured attempting to issue message EYUXL0135A.
Local MAS initialization is terminated, and CICS initialization continues without the CPSM MAS agent present.
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.
Console, job log
EYU9XLBE
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.
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.
You should ensure that you only specify EYU9XLOP when you have a workload associated with the region. Either:
Console, job log
EYU9XLOP
An attempt to perform an automatic restart of the named CMAS failed for the reason given, where:
The CMAS is terminated.
Perform the recommended actions for any messages which preceded this message and restart the CMAS.
Console, job log, EYULOG
EYU0XLES
During CMAS or MAS initialization the CICS transaction definition for tranname is not found or does not specify the correct program name.
Initialization continues, but unpredictable results may occur due to the missing or incorrect transaction definition.
Ensure that the CSD used by the CMAS or MAS is correct and the appropriate CICSPlex SM definitions have been installed.
Console, job log
EYU9XLBE
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.
Initialization terminates.
Ensure that the CICS Transaction Server CMAS release cmasrelease matches the CICS release cicsrelease.
Console, job log
EYU9XLCS
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.
MAS agent termination is delayed until a correct response is received for the prompt, the COSH transaction is issued, or the region is terminated.
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.
Console, job log
EYU9XLEV
The operator has replied correctly to the prompt for message EYUXL0143A.
MAS agent termination continues.
None.
Console, job log
EYU9XLEV
A failure occurred when attempting to issue message EYUXL0143A to delay MAS agent termination.
After issuing transaction dump code EYUI, MAS agent termination continues.
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.
Console, job log
EYU9XLEV
The operator replied incorrectly to the prompt for message EYUXL0143A, where r is the reply entered.
After issuing this message, message EYUXL0143A is reissued.
Refer to the instructions for message EYUXL0143A.
Console, job log
EYU9XLEV
While the prompt for message EYUXL0143A was active, the COSH transaction was issued or a request to terminate the region was received.
The prompt for message EYUXL0143A is cancelled and MAS agent termination continues.
None.
Console, job log
EYU9XLEV
An error occurred during CMAS initialization while attempting to enable a CICSPlex SM related CICS exit (EXEC CICS ENABLE PROGRAM), where:
An EYUS transaction dump will be taken and the CMAS initialization will fail.
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:
Console, job log
EYU9XLCS
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:
An EYUS transaction dump will be taken and the CMAS initialization will fail.
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:
Console, job log
EYU9XLCS
An error occurred during CMAS initialization while attempting to start processing for a CICSPlex SM related CICS exit (EXEC CICS ENABLE PROGRAM START), where:
An EYUS transaction dump will be taken and the CMAS initialization will fail.
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:
Console, job log
EYU9XLCS
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:
An EYUS transaction dump will be taken and the CMAS initialization will fail.
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:
Console, job log
EYU9XLCS
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.
If possible, the CICSPlex SM network task will be retried after a short delay.
Check that the CMAS is properly initialized.
EYULOG
EYU9XLOP
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.
System Action: EYU9XLOP terminates. Depending on the error CICS may not free the connection.
Check that the CMAS is properly initialized.
Console, job log
EYU9XLOP
During CMAS or MAS initialization, the internal parameter table could not be initialized.
Parameter initialization for the CMAS or MAS terminates. A user trace record is written to the CICS trace data set.
Collect the exception trace records and contact your IBM Support Center.
Console, job log, EYULOG
EYU0XLPI
During CMAS or MAS initialization, the EYUPARM data set could not be accessed for one of the following reasons:
Parameter initialization for the CMAS or MAS terminates.
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.
Console, job log, EYULOG
EYU0XLPI, EYU1XLPI
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.
Parameter initialization for the CMAS or MAS terminates.
Make sure the EYUPARM data set and its DD statement specify a logical record length of 80.
Console, job log, EYULOG
EYU0XLPI
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).
Parameter initialization for the CMAS or MAS terminates.
Make sure the EYUPARM data set and its DD statement specify a record format of F or FB.
Console, job log, EYULOG
EYU0XLPI
During CMAS or MAS initialization, the disposition of the EYUPARM data set was found to be invalid. EYUPARM must be an input data set.
Parameter initialization for the CMAS or MAS terminates.
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.
Console, job log, EYULOG
EYU0XLPI
Noncritical errors occurred during CMAS or MAS parameter initialization.
Parameter initialization pauses and waits for a reply.
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.
Console, job log, EYULOG
EYU0XLPI
An invalid parameter name was found during CMAS or MAS parameter initialization, where:
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.
Reply to message EYUXL0205D when it is issued.
Console, job log, EYULOG
EYU0XLPI, EYU1XLPI
An invalid parameter value was found during CMAS or MAS parameter initialization, where value identifies the invalid parameter value.
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.
Reply to message EYUXL0205D when it is issued.
Console, job log, EYULOG
EYU0XLPI, EYU1XLPI
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.
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.
Reply to message EYUXL0205D when it is issued.
Console, job log, EYULOG
EYU0XLPI, EYU1XLPI
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.
None.
None.
EYULOG
EYU0XLPR
This message lists a parameter and the value that is currently in effect.
None.
None.
EYULOG
EYU0XLPR
This is the message header for an EYUPARM list and any associated errors.
None.
None.
Console, job log, EYULOG
EYU0XLPI, EYU1XLPI
This message lists a parameter statement as it was found in the EYUPARM input data set during CMAS or MAS parameter initialization.
If any part of the parameter statement is invalid, this message is followed by the appropriate error message.
None.
Console, job log, EYULOG
EYU0XLPI, EYU1XLPI
A required parameter was not found during CMAS or MAS parameter initialization.
Parameter initialization for the CMAS or MAS terminates.
Review the parameter requirements in the CICS Transaction Server for z/OS Installation Guide and add the missing parameters to the EYUPARM data set.
Console, job log, EYULOG
EYU0XLPI, EYU1XLPI
The Parameter Services subcomponent has been successfully initialized.
CICSPlex SM initialization continues.
None.
EYULOG
EYU0XLPI, EYU1XLPI
The Parameter Services subcomponent could not be initialized.
CICSPlex SM initialization terminates. A user trace record is written to the CICS trace data set.
Examine the exception trace records, and any messages issued before this one, to determine the cause of the problem.
Console, job log, EYULOG
EYU0XLPI, EYU1XLPI
A CICSPlex SM EYUPARM has been updated via the COD0 transactions SET request, where:
If one or both userid and terminal inserts are not available N/A will be displayed for these inserts.
The specified EYUPARM is updated.
None. This message is to log a change in the CICSPlex SM system parameter.
Console, job log
EYU9DBG1
The CICSPlex SM recovery routine has been entered as a result of an abend in a CMAS or a MAS.
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.
Collect as much of the following information as possible, and contact your IBM Support Center:
Console, Job log
EYU9XLRV
While attempting to capture and format diagnostic information, the CICSPlex SM recovery routine encountered addresses that could not be accessed.
The recovery routine terminates and no further diagnostic information is presented.
Follow the instructions in message EYUXL0900I.
Console, Job log
EYU9XLRV
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.
The recovery routine begins formatting diagnostic information.
Follow the instructions in message EYUXL0900I.
Console, Job log
EYU9XLRV
A program was found to be in access register (AR) mode when it should not be, where:
The recovery routine identifies the problem program and displays its name in message EYUXL0905E.
Follow the instructions in message EYUXL0900I.
Console, Job log
EYU9XLRV
This message describes the location and conditions of an abend that occurred in CICSPlex SM, where:
The recovery routine continues to format diagnostic information.
Follow the instructions in message EYUXL0900I.
Console, Job log
EYU9XLRV
The register contents at the location of the abend have been formatted; this message serves as a header for the content records that follow.
The recovery routine continues to format diagnostic information. The register contents are displayed in EYUXL0907I messages immediately following this header.
Follow the instructions in message EYUXL0900I.
Console, Job log
EYU9XLRV
The name of each register that was formatted is displayed along with its content.
The recovery routine continues to format diagnostic information.
Follow the instructions in message EYUXL0900I.
Console, Job log
EYU9XLRV
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.
The recovery routine continues to format diagnostic information. The contents of storage are displayed in EYUXL0909I messages immediately following this header.
Follow the instructions in message EYUXL0900I.
Console, Job log
EYU9XLRV
The contents of storage at each of the following locations is displayed:
The formatting of diagnostic information is complete. The recovery routine terminates.
The impact on system processing depends on when the abend occurred:
Follow the instructions in message EYUXL0900I.
Console, Job log
EYU9XLRV
This message indicates that an SDUMP has been requested by CPSM recovery, where:
An SDUMP has been requested, containing the current region, the ESSS Address Space, and cache data spaces for components accessed in the abending task.
Follow the instructions in message EYUXL0900I.
Console, job log
EYU9XLRV
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.
Processing continues.
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.
Console, job log
EYU9XLRV
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.
Processing continues.
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
Console, job log
EYU9XLRV
This message indicates the date and time at which the abend described in message EYUXL0950E occurred, where:
The recovery routine continues to format diagnostic information.
Follow the instructions in message EYUXL0900I.
Console, Job log, EYULOG
EYU1XLRV
This message identifies the CICSPlex SM dynamic link library (DLL) where the abend occurred, where:
The recovery routine continues to format diagnostic information.
Follow the instructions in message EYUXL0900I.
Console, Job log, EYULOG
EYU1XLRV
This message identifies the CICSPlex SM method where the abend occurred, where:
The recovery routine continues to format diagnostic information.
Follow the instructions in message EYUXL0900I.
Console, Job log, EYULOG
EYU1XLRV
The register contents at the location of the abend have been formatted; this message serves as a header for the content records that follow.
The recovery routine continues to format diagnostic information. The register contents are displayed in EYUXL0956I messages immediately following this header.
Follow the instructions in message EYUXL0900I.
Console, Job log, EYULOG
EYU1XLRV
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:
The next group includes the extended (32-bit) registers, where:
The last group includes hardware and operating system registers, where:
The recovery routine continues to format diagnostic information.
Follow the instructions in message EYUXL0900I.
Console, Job log, EYULOG
EYU1XLRV
This message provides additional information about the abend, where:
The recovery routine continues to format diagnostic information.
Follow the instructions in message EYUXL0900I.
Console, Job log, EYULOG
EYU1XLRV
The CICSPlex SM recovery routine was able to recover from the abend.
The formatting of diagnostic information is complete. The recovery routine terminates.
Follow the instructions in message EYUXL0900I.
Console, Job log, EYULOG
EYU1XLRV
The CICSPlex SM recovery routine (XLRV) has successfully completed processing the abend reported in the previous EYUXL09xx messages.
None.
Follow the instructions in message EYUXL0900I.
Console, Job log
EYU9XLRV