EYUXEnnnn messages

EYUXE0001I
CPSM subsystem (EYUX) initialization complete
Explanation:

The CICSPlex® SM address space (CMAS) startup program, EYU9XECS, has completed initialization of the CICSPlex SM MVS™ subsystem entry, which is called EYUX. The CICSPlex SM subsystem entry is only created the first time a CMAS is started after an IPL. Subsequent CMAS startups verify the existence of the subsystem entry for the required release of CICSPlex SM.

System action:

CMAS initialization continues.

User response:

None.

Destination:

Console, job log

Module:

EYU9XECS

EYUXE0002I
CICSPlex SM Service Address Space active
Explanation:

This message confirms the existence of the Environment Services System Services (ESSS) address space. The first CICSPlex SM address space (CMAS) to start after an IPL creates the ESSS address space. All subsequent CMAS startups verify that the address space is active. If the address space exists but is not active, the CMAS currently being started must restart it.

System action:

CMAS initialization continues.

User response:

None

Destination:

Console, job log

Module:

EYU9XECS

EYUXE0003I
End of Task entered for CICSPlex SM relnum
Explanation:

The CICSPlex SM subsystem end of task routine, EYU9XEET, was entered due to the abnormal termination of a CICSPlex SM address space, where:

relnum
Identifies the release of CICSPlex SM that was affected.
System action:

CICSPlex SM releases all its environment dependencies in the Environment Services System Services (ESSS) address space.

User response:

Examine the exception trace records, and any messages issued before this one, to determine the cause of the abnormal termination.

Destination:

Console, job log

Module:

EYU9XEET

EYUXE0004E
CPSM subsystem (EYUX) not found
Explanation:

The Environment Services System Services (ESSS) utility program, EYU9XEUT, was invoked, but no CICSPlex SM MVS subsystem could be found. EYUX is the name of the subsystem that EYU9XEUT expected to find. At least one CICSPlex SM address space (CMAS) must be running for the CICSPlex SM subsystem to exist.

System action:

The ESSS utility program terminates.

User response:

Make sure there is a CMAS running and then restart the ESSS utility program.

Destination:

Console, job log

Module:

EYU9XEUT

EYUXE0005E
Invalid ESSS function request
Explanation:

An invalid Environment Services System Services (ESSS) utility function was requested. The valid functions are:

System action:

The ESSS utility program terminates.

User response:

Check the SYSIN statement on the utility program JCL and specify a valid function.

Destination:

Console, job log

Module:

EYU9XEUT

EYUXE0006E
Invalid CICSPlex SM version request
Explanation:

An Environment Services System Services (ESSS) utility function was requested for an invalid version of CICSPlex SM.

System action:

The ESSS utility program terminates.

User response:

Check the version specified on the ESSS utility request and make sure it is a valid version of CICSPlex SM running at your site.

Destination:

Console, job log

Module:

EYU9XEUT

EYUXE0007E
Module is not requested version
Explanation:

An Environment Services System Services (ESSS) RELOAD utility function was requested, but the new program in the UTILLIB data set is not of the requested version.

System action:

The ESSS utility program terminates.

User response:

Update either the UTILLIB data set or the utility request to specify the correct version.

Destination:

Console, job log

Module:

EYU9XEUT

EYUXE0008E
Invalid ESSS function request options
Explanation:

An Environment Services System Services (ESSS) utility request contained invalid options.

System action:

The ESSS utility program terminates.

User response:

Refer to the CICSPlex System Manager Problem Determination manual for a list of valid ESSS utility request options.

Destination:

Console, job log

Module:

EYU9XEUT

EYUXE0009E
Invalid ESSS request syntax
Explanation:

The syntax of an Environment Services System Services (ESSS) utility request was invalid.

System action:

The ESSS utility program terminates.

User response:

Refer to the CICSPlex System Manager Problem Determination manual for the correct syntax of ESSS utility requests.

Destination:

Console, job log

Module:

EYU9XEUT

EYUXE0010E
CICSPlex SM version required
Explanation:

The Environment Services System Services (ESSS) utility request that was made requires a specific version of CICSPlex SM.

System action:

The ESSS utility program terminates.

User response:

Check the ESSS utility program JCL and add the VERSION keyword to the appropriate utility request. Refer to the CICSPlex System Manager Problem Determination manual for the correct syntax of ESSS utility requests.

Destination:

Console, job log

Module:

EYU9XEUT

EYUXE0011E
Program name is not APF authorized.
Explanation:

The specified program should be in an APF-authorized library, but is not, where:

name
Identifies the program as one of the following:
EYU9XECS
The CICSPlex SM address space (CMAS) startup program
EYU9XEUT
The Environment Services System Services (ESSS) utility program
Be aware that the specified program may be in an APF-authorized library, but if that library is in a STEPLIB concatenation with other libraries that are not APF-authorized, it becomes unauthorized.
System action:

Depending on which program was not authorized, either CMAS initialization or the ESSS utility terminates.

User response:

Make sure the specified program, and all other libraries in the STEPLIB concatenation, are APF-authorized. Then, restart the job.

Destination:

Console, job log

Module:

EYU9XECS, EYU9XEUT

EYUXE0012E
dsname dataset not opened
Explanation:

One of the following data sets could not be opened by the Environment Services System Services (ESSS) utility program:

System action:

The ESSS utility program terminates.

User response:

Determine the cause of the OPEN error and then restart the utility program.

Destination:

Console, job log

Module:

EYU9XEUT

EYUXE0013E
BLDL error has occurred
Explanation:

An error occurred while attempting to issue a BLDL for a module in the UTILLIB data set, while executing the EYU9XEUT utility or during CMAS initialization.

System action:

The ESSS utility program or CMAS initialization terminates, depending on which environment produced the error.

User response:

Determine the cause of the BLDL error and then restart the utility program or the CMAS, depending on which environment produced the error.

Destination:

Console, job log

Module:

EYU9XEUT, EYU9XECS

EYUXE0014E
modname module not found
Explanation:

The specified module could not be located in the UTILLIB data set if executing utility program EYU9XEUT, or the specified module could not be located in the MVS linklist or LPALIB if this message was issued during CMAS initialization.

System action:

The ESSS utility program or CMAS initialization terminates, depending on which environment produced the error.

User response:

Place the module in the UTILLIB data set and then restart the utility program if running EYU9XEUT, or ensure that the module is in the MVS linklist or LPALIB if the message was issued during CMAS initialization.

Destination:

Console, job log

Module:

EYU9XEUT, EYU9XECS

EYUXE0015E
modname module not executable
Explanation:

The specified module is in a nonexecutable format.

System action:

The ESSS utility program or CMAS initialization terminates, depending on which environment produced the error.

User response:

Determine the reason for the module being nonexecutable and then restart the utility program, or restart the CMAS, depending on which environment produced the error message.

Destination:

Console, job log

Module:

EYU9XEUT, EYU9XECS

EYUXE0016E
type GETMAIN failure
Explanation:

A GETMAIN for the specified type of storage has failed, where:

type
Identifies the type of storage that could not be obtained as CSA, DSA, or ECSA.
System action:

The ESSS utility program or CMAS initialization terminates, depending on which environment produced the error.

User response:

Increase the appropriate region size and then restart the utility program, or restart the CMAS, depending on which environment produced the error.

Destination:

Console, job log

Module:

EYU9XEUT, EYU9XECS

EYUXE0017E
Module modname cannot be loaded
Explanation:

An attempt to load the specified module has failed.

System action:

The ESSS utility program or CMAS initialization terminates, depending on which environment produced the error.

User response:

Determine the reason for the LOAD failure and then restart the utility program, or restart the CMAS, depending on which environment produced the error.

Destination:

Console, job log

Module:

EYU9XEUT, EYU9XECS

EYUXE0019E
ESSS PC REPLACE request failed
Explanation:

An attempt to update the CICSPlex SM program call routines in the ESSS service address space has failed.

System action:

System continues to run using existing PC routines.

User response:

Attempt to rerun the EYU9XEUT utility, if the problem persists contact IBM® service.

Destination:

Console, job log

Module:

EYU9XEUT

EYUXE0020E
ESSS IDENTIFY Failed Return code = X'code'
Explanation:

The CICSPlex SM address space (CMAS) startup program, EYU9XECS, received a nonzero return code while attempting to identify itself to the Environment Services System Services (ESSS) address space, where:

code
Is the hexadecimal return code.
System action:

CMAS initialization terminates.

User response:

Use the DUMP option of the ESSS utility program, EYU9XEUT, to obtain a report on the data structures in the ESSS address space. Then, contact your IBM Support Center.

Destination:

Console, job log

Module:

EYU9XECS

EYUXE0021E
No EYURXESS available
Explanation:

The CICSPlex SM ESSS service address space could not be found.

System action:

EYU9XEUT utility terminates.

User response:

Ensure that the VERSION keyword matches a running CICSPlex SM service address space.

Destination:

Console, job log

Module:

EYU9XEUT

EYUXE0022E
ESSS not active
Explanation:

The Environment Services System Services (ESSS) utility JCL included a request for a release of CICSPlex SM that is not currently active.

System action:

The ESSS utility program terminates.

User response:

Check the ESSS utility program JCL and specify a valid VERSION keyword. Then, restart the utility program.

Destination:

Console, job log

Module:

EYU9XEUT

Start of changeEYUXE0023EEnd of change
ESSS address space not created -- reason
Explanation:

The Environment Services System Services (ESSS) address space could not be created, where:

reason
indicates one of the following errors:
  • Invalid return code from EYU9X310
  • EYUTXEPC cannot be loaded
  • Getmain for region storage failed
  • Getmain for common storage failed
  • ESSS control block build failed
  • EYUX310 address space abended
System action:

A dump is taken of the ESSS address space. For the EYUX310 address space abended error, the title of the dump is EYU9X310.SYSTEM.FAILURE. For all other errors the dump title is EYU9X310.CREATE.FAIL.DUMP. The creating CMAS issues this message and then terminates.

User response:

Make sure the ESSS initialization routine, EYU9X310, resides in one of the following places:

Then, restart the CMAS startup program.

Determine the cause of the error from the message insert. Depending upon the message, you may be able to correct the error:

EYUTXEPC cannot be loaded
Ensure that EYUTXEPC is in a data set allocated to the SEYUAUTH file in the CMAS, then restart the CMAS.
Getmain for region storage failed
ensure that any IEFUSI exit in place allows the EYUX310 address space to allocate at least 32 MB of storage above the 16 MB line, then restart the CMAS.
Getmain for common storage failed
Ensure that at least 8 KB of contiguous ECSA storage (SP241 above the 16 MB line) is available, then restart the CMAS.

If the error cannot be rectified as specified above, and for all other messages, collect the dump, the CMAS job output, and the system log from the time of the error, and contact your IBM support center.

Destination:

Console, job log

Module:

EYU9XECS

EYUXE0024E
ESSS release limit exceeded
Explanation:

The maximum number of different CICSPlex SM releases allowed in a system at one time has been reached.

System action:

The CICSPlex SM address space (CMAS) startup program, EYU9XECS is terminated.

User response:

Remove at least one previous release of CICSPlex SM from your system. Then, restart the CMAS startup program.

Destination:

Console, job log

Module:

EYU9XECS

EYUXE0025E
ESSS and PC Routines Mismatch Encountered.
Explanation:

During CMAS initialization, the Environment Services System Services (ESSS) IDENTIFY function determined that the generation dates of the ESSS address space code and the program call (PC) routines it uses were not the same.

Start of change
System action:

A dump is taken of the ESSS address space. The title of the dump is EYU9X310.CREATE.FAIL.DUMP. The creating CMAS issues this message and then terminates.

End of change
User response:

Verify the following:

Issue the MVS command F LLA,REFRESH to refresh the LNKLST LOOKASIDE address space (LLA). Then try to restart a CMAS. If this problem reoccurs, you must reIPL the system.

Destination:

Console, job log

Module:

EYU9XECS

EYUXE0026I
EYU9XECS Recovery Routine Entered
Explanation:

The CICSPlex SM address space (CMAS) startup recovery routine has been entered due to an abnormal termination of the startup program, EYU9XECS.

System action:

CICSPlex SM attempts to recover from the abend and obtain an SVC dump.

User response:

Examine the SVC dump, if available, and any messages issued prior to this one, to determine the cause of the abnormal termination.

Destination:

Console, job log

Module:

EYU9XECS

EYUXE0027W
Lock recovery failed - reason
Explanation:

CICSPlex SM uses its own logical lock scheme to serialize access to its shared resources. During CICSPlex SM address space (CMAS) or managed application system (MAS) termination, the MVS end-of-task routine provided by CICSPlex SM invokes a lock recovery PC routine to:

This lock recovery routine has failed for one of the following reasons:

  1. Insufficient storage for work area
    There was insufficient storage for a local work area required by the PC routine.
  2. Parameter list not addressable
    The parameter list passed as input to the PC routine was in storage that could not be addressed.
  3. Invalid parameter(s)
    One or more invalid parameters were found in the parameter list passed as input to the PC routine.
  4. Abnormal termination
    An abnormal termination was intercepted by the PC routine.
System action:

The impact on system processing depends on the reason for the failure:

  1. The PC routine is unable to fulfill any of its responsibilities. This may result in errors in associated address spaces (that is, MASs associated with a CMAS or the CMAS associated with a MAS). It may also make it impossible to restart the terminating address space without first terminating all associated address spaces.
  2. Same as 1.
  3. Same as 1.
  4. The PC routine may have managed to partially fulfill its responsibilities before encountering the abnormal termination. Therefore, the result of the error cannot be predicted. Before returning control to the end-of-task exit, an attempt is made to obtain an SVC dump and a software error recording request is made to the MVS LOGREC facility.
User response:

The appropriate response depends on the reason for the failure:

  1. Terminate all address spaces associated with the terminating address space. Then, restart all the address spaces. If the problem persists, contact your IBM Support Center.
  2. Same as 1.
  3. Same as 1.
  4. Collect the following information and contact your IBM Support Center:
    • The SVC dump, if one was obtained
    • The job log, and
    • The record written to the SYS1.LOGREC data set
Destination:

Console, job log

Module:

EYU9XEET

EYUXE0028I
End of Memory entered for CICSPlex SM relnum, JOB jobname Return code = X'code'
Explanation:

The CICSPlex SM subsystem end of memory routine, EYU9XEEM, was entered due to an abnormal termination of a CICSPlex SM address space, where:

relnum
Identifies the release of CICSPlex SM that was affected.
jobname
Is the name of the address space that terminated.
code
Is the hexadecimal return code.
System action:

CICSPlex SM releases all its environment dependencies in the Environment Services System Services (ESSS) address space.

User response:

Examine the exception trace records, and any messages issued before this one, to determine the cause of the abnormal termination.

Destination:

Console, job log

Module:

EYU9XEEM

EYUXE0029E
ESSS connection termination failed: Return Code = X'code'
Explanation:

The CICSPlex SM subsystem end of task routine, EYU9XEET, could not terminate the connection between a CMAS or MAS and the Environment Services System Services (ESSS) address space, where:

code
Is the hexadecimal return code.
System action:

End of task processing continues. However, some dependencies still exist between the CMAS or MAS and the ESSS address space.

User response:

Use the DUMP option of the ESSS utility program, EYU9XEUT, to dump the data structures in the ESSS address space. Collect the dump output and contact your IBM Support Center.

Destination:

Console, job log

Module:

EYU9XEET

EYUXE0030E
Insufficient storage for Subsystem function routing
Explanation:

The CICSPlex SM subsystem preprocessor routine (EYU9XEER) attempted to create a work area for end of task or end of memory processing, but there was not enough storage available. The routine requires approximately 100 bytes above the 16Mb line.

System action:

The subsystem preprocessor routine terminates. No CICSPlex SM-related end of task or end of memory processing occurs.

User response:

Increase the appropriate region size.

Destination:

Console, job log

Module:

EYU9XEER

EYUXE0031E
Function (funcname) not performed: MASs are active
Explanation:

The TERMINATE or REPLACE request cannot be processed because of active CICSPlex SM MASs.

System action:

EYU9XEUT utility terminates.

User response:

Ensure that the CICSPlex SM function in MAS regions is shut down before rerunning EYU9XEUT.

Destination:

Console, job log

Module:

EYU9XEUT

EYUXE0032A
CICSPlex SM relnum Service Address Space Dump termination requested. Reply Y when a Dump Dataset is available.
Explanation:

The program call (PC) routines detected possible corruption in the internal data structures of the Environment Services System Services (ESSS) address space, where:

relnum
Identifies the release of CICSPlex SM that was affected.
System action:

This message remains on the console until a reply is received.

Once a reply of Y is received, a system dump is taken and the ESSS address space terminates. Any CMAS or MAS that was connected to the ESSS address space also abends as a result of ESSS not being available. Additional messages related to CMAS or MAS abends may be issued to the console.

User response:

Make sure a system dump data set is available and then issue a reply of Y to this message. Collect the dump output and contact your IBM Support Center.

Messages related to CMAS or MAS abends can be ignored, as they are a result of the ESSS address space termination.

Destination:

Console

Module:

EYU9X310

EYUXE0033E
ESSS Shutdown detected: CMAS startup terminated
Explanation:

During CMAS initialization, CICSPlex SM detected that the ESSS service address space is being shutdown.

System action:

The CMAS startup is terminated and the CICS® job ends.

User response:

Wait until ESSS shutdown completes and restart the CMAS

Destination:

Console, job log

Module:

EYU9XECS

EYUXE0034E
Invalid Version Detected for module, found version, expected version
Explanation:

This message is issued during CMAS startup while loading the specified module in preparation for initializing or restarting the ESSS address space.

The CICSPlex SM version of the module does not match the version of EYU9XECS. The possible values for module are:

EYU9XEEM (End Of Memory Exit)
EYU9XEET (End Of Task Exit)
EYUTXEPC (ESSS PC routines)

System action:

CMAS startup fails, the ESSS address space is not created.

User response:

Ensure that the named module at the proper version is in a load library which is first in the concatenation of the following search order: 1. steplib/joblib 2. link list 3. LPA Restart the CMAS.

Destination:

Console

Module:

EYU9XECS

EYUXE0035W
Site security user exit program, EYU9XESV, not found
Explanation:

The security exit program could not be found.

System action:

The system continues and uses the default security validation processing.

User response:

Ensure EYU9XESV is in a library in the CMAS STEPLIB concatenation if you have written a security validation exit.

Destination:

Console, Joblog

Module:

EYU9XECS

Start of change
EYUXE0036E
Address Space Create program failed - R15=X'xxxxxxxx'
Explanation:

When attempting to create the EYUX310 address space the CMAS's LINK to the sddress space create program ended with the specified non-zero return code in general register 15.

System action:

A dump is taken of the CMAS address space. The title of the dump is EYU9XECS.AS.CREATE.FAIL.DUMP. The CMAS then issues this message and terminates.

User response:

Collect the dump, the CMAS job output, and the system log from the time of the error, and contact your IBM support center.

Destination:

Console, Joblog

Module:

EYU9XECS

End of change
Start of change
EYUXE0037E
Insufficient storage for Subsystem function End Of Task (EOT)
Explanation:

The CICSPlex SM subsystem end of task (EOT) routine (EYU9XEET) attempted to create a work area for end of task processing for a CMAS or MAS, but there was not enough storage available. The routine requires approximately 600 bytes above the 16Mb line.

System action:

The subsystem EOT routine terminates. No CICSPlex SM-related end of task processing occurs for the CMAS or MAS.

User response:

Increase the appropriate region size.

Destination:

Console, Joblog

Module:

EYU9XEET

End of change [[ Contents Previous Page | Next Page Index ]]