If you need to contact your IBM® Support Center in response to any of these codes, gather as much of the following diagnostic information as possible::
A non-recoverable error occurred during MAS initialization.
MAS initialization terminates. The CICS system continues to run normally, but it is not known to CICSPlex SM.
Examine the MAS job log for any messages that might indicate a problem. If such messages exist, follow the instructions associated with those messages and then restart the MAS. If no messages exist, or if no appropriate action is indicated, gather the specified diagnostic information and contact your IBM Support Center.
EYU9XLEV
Either a non-recoverable abend occurred during MAS initialization or a proper environment did not exist when attempting to recover from an abend.
MAS initialization terminates. The CICS system continues to run normally, but it is not known to CICSPlex SM.
If this abend occurred during initialization, MAS initialization terminates. The CICS system continues to run normally, but it is not known to CICSPlex SM.
If this abend occurred at any time other than MAS initialization, the failing task terminates. The CICS system continues to run normally, but it may not be known to CICSPlex SM.
Examine the MAS job log for any messages that might indicate a problem. If such messages exist, follow the instructions associated with those messages and then restart the MAS, if necessary. If no messages exist, or if no appropriate action is indicated, gather the specified diagnostic information and contact your IBM Support Center.
EYU9XLRV
The environment create routine in a CMAS or MAS was called invalidly. The calling process was not a CICSPlex SM service.
CICS system processing continues.
Make sure that:
If neither of these conditions exists, gather the specified diagnostic information and contact your IBM Support Center.
EYU9XLOP
An error occurred while attempting to recover from an abend.
The failing task terminates. The CICS system continues to run normally, but it may not be known to CICSPlex SM.
Examine the MAS job log for any messages that might indicate a problem. If such messages exist, follow the instructions associated with those messages and then restart the MAS, if necessary. If no messages exist, or if no appropriate action is indicated, gather the specified diagnostic information and contact your IBM Support Center.
EYU9XLRV
The Web User Interface environment create routine in a CMAS or MAS was called invalidly. The calling process was not a CICSPlex SM service.
The failing task terminates. A transaction dump is taken. CICS system processing continues.
Make sure that:
If neither of these conditions exists, contact your IBM Support Center.
EYU0VGIN
An exception condition was detected in a remote MAS but a full CICSPlex SM exception trace could not be written at that time. This condition is not necessarily a failure in the application, but the reporting of an exception condition, which is usually the result of communications problems. Communications exceptions cannot be sent to the connected CMAS.
A transaction dump is taken to document the exception. Task execution continues, taking the appropriate action for the exception condition.
Examine the MAS and CMAS job logs for any messages that might indicate a problem, especially for those related to the communications network. If such messages exist, follow the instructions associated with those messages. If no messages exist, or if no appropriate action is indicated, gather the specified diagnostic information and contact your IBM Support Center.
EYU9XLEV, EYU9XLOP
A CMAS-to-CMAS connection has terminated abnormally. The receive task component of the connection has tried to terminate as cleanly as possible, but it has detected that it is still in a network receive state. This makes it impossible for it to terminate, without CICS generating an additional transaction abend describing this apparent transmission state discrepancy. However, this network state cannot be reset because of the reported connection failure. This abend is issued to preempt the normal CICS abend code related to these network state errors.
The CPI-C or MRO receive task should now end completely with this abend. When all task components for the connection have terminated, the first speaker CMAS of the connection pair should attempt to reestablish the connection.
Check the CMAS job log, EYULOG and CICS message log for previous failures or error conditions and follow the User Response for these messages.
EYU0CLCT, EYU0CLCU, EYU0CLMT, EYU0CLMU