The following variables are used in EYUNLnnnn messages:
Each message that uses these variables identifies the CICS command that returned them. For descriptions of the values for a particular CICS command, refer to the CICS/ESA System Programming Reference.
The MAS subcomponent was not able to register its major object environment block (MOEB) control block with the Kernel Linkage component.
MAS initialization terminates. A user trace record is written to the CICS trace data set. The CICS system continues to run normally, but it is not known to CICSPlex® SM.
Collect the trace records and the job log and contact your IBM® Support Center.
Console, job log, EYULOG
EYU0NLRT, EYU1NLRT
The MAS subcomponent was not able to register its termination ECB with the Kernel Linkage component.
MAS initialization terminates. A user trace record is written to the CICS trace data set. The CICS system continues to run normally, but it is not known to CICSPlex SM.
Collect the trace records and the job log and contact your IBM Support Center.
Console, job log, EYULOG
EYU0NLRT
The MAS subcomponent was not able to acquire the necessary storage for its major object environment block (MOEB) control block.
MAS initialization terminates. A user trace record is written to the CICS trace data set. The CICS system continues to run normally, but it is not known to CICSPlex SM.
Collect the trace records and the job log and contact your IBM Support Center.
Console, job log, EYULOG
EYU1NLRT
The address of the Communications Receiver Block required for MAS-to-CMAS communications is zero. MAS-to-CMAS communications is not available.
MAS processing terminates. A user trace record is written to the CICS trace data set. The CICS system continues to run normally, but it is not known to CICSPlex SM.
Collect the trace records and the job log and contact your IBM Support Center.
Console, job log, EYULOG
EYU0NLRT, EYU1NLRT
A request was issued to CICSPlex SM Parameter Services and it returned an abnormal response.
MAS initialization terminates. A user trace record is written to the CICS trace data set. The CICS system continues to run normally, but it is not known to CICSPlex SM.
Collect the trace records and the job log and contact your IBM Support Center.
Console, job log, EYULOG
EYU0NLRT, EYU1NLRT
Upon discovering a non-zero value for the MASALTLRTCNT EYUPARM during MAS agent initialization, EYU0NLRT attempted to set the priority of the CONA transaction to the value specified in the MASALTLRTPRI EYUPARM, but a non-OK response was received.
MAS agent initialization continues after the message is issued.
Ensure that the CONA transaction is installed in the MAS. If not, upgrade the CSD if necessary, install the transaction, and restart the MAS agent. If the CONA transaction is installed, collect the auxtrace data sets and the complete job output from the MAS and the CMAS it connects to and contact your IBM Support Center.
Console, job log, EYULOG
EYU0NLRT
During MAS agent initialization, EYU0NLRT running under the CONL task will issue this message after starting CONA tasks if the MASALTLRTCNT EYUPARM is non-zero, where:
MAS agent initialization continues after the message is issued.
If a equals b, no action is required, unless a change is required for the number of tasks started. If a does not equal b, collect the auxtrace data sets and the complete job output from the MAS and the CMAS it connects to and contact your IBM Support Center.
Console, job log, EYULOG
EYU0NLRT
This message is issued when the first alternate long running task in a MAS processes a request.
MAS processing continues after the message is issued.
No action is required unless alternate long running task processing is not desired in the MAS, in which case set EYUPARM MASALTLRTCNT to 0 (zero) and restart the MAS agent.
Normally the absence of this message, when the EYUNL0088I message indicates that at least one alternate LRT was started, indicates that a problem exists. Verify that the CONA transaction is defined to security and that the userid used to start the MAS has authority to start the transaction. If security is not an issue, collect the auxtrace data sets and the complete job output from the MAS and the CMAS it connects to and contact your IBM Support Center.
Console, job log, EYULOG
EYU0NLRA
After initialization completed, the managed application system (MAS) determined that the heartbeat task was not active and initiated a normal shutdown, where:
The CICS system continues to run normally, but it is not known to CICSPlex SM.
Check the CMAS EYULOG for any related messages and follow the instructions provided for those messages. The MAS can be restarted with the COLM or CORM transactions. If the problem persists, collect the trace records and the CMAS EYULOG and contact your IBM Support Center.
Console, job log, EYULOG
EYU0NLRT
This message is issued when the alternate long running task terminates with an error, where:
MAS processing continues after the message is issued.
Check for any previous messages in the log that may indicate why the alternate long running task terminated abnormally, referring to the documentation for those messages. If no other messages exist, collect the auxtrace data sets and the complete job output from the MAS and the CMAS it connects to and contact your IBM Support Center.
Console, job log, EYULOG
EYU0NLRA
The long running task (LRT) for a MAS could not be initialized, where:
MAS initialization terminates. The CICS system continues to run normally, but it is not known to CICSPlex SM.
Refer to the messages preceding this one for details on the cause of the problem.
Console, job log, EYULOG,
EYU0NLRT, EYU1NLRT
The long running task (LRT) for a MAS has been successfully initialized, where:
The MAS is ready for work. CICSPlex SM processing continues.
None
Console, job log, EYULOG
EYU0NLRT, EYU1NLRT
Another component of CICSPlex SM made a request that is not supported by the MAS subcomponent, where:
The request is ignored. MAS processing continues.
None.
Console, job log, EYULOG
EYU0NLRT
An EXEC CICS WAIT EXTERNAL command returned an abnormal response. The respcode and resp2code values are as returned by CICS.
The MAS attempts a normal shutdown. A user trace record is written to the CICS trace data set.
Follow the instructions associated with the respcode and resp2code values for the EXEC CICS WAIT EXTERNAL command.
Console, job log, EYULOG
EYU0NLRT, EYU0NLRA
An error occurred in the Lock Services subcomponent while retrieving a message to be processed by the MAS. The MAS can no longer process CICSPlex SM requests.
MAS processing terminates. A user trace record is written to the CICS trace data set. The CICS system continues to run normally, but it is not known to CICSPlex SM.
Collect the trace records and the job log and contact your IBM Support Center.
Console, job log, EYULOG
EYU0NLRT, EYU0NLRA
A program required by the MAS subcomponent could not be enabled, where:
The impact on system processing depends on which program could not be enabled:
In all cases, a user trace record is written to the CICS trace data set.
Follow the instructions associated with the respcode and eibrcode values for the EXEC CICS ENABLE command. Then, depending on which program could not be enabled, do one of the following:
Console, job log, EYULOG
EYU0NLGT, EYU0NLHD, EYU0NLRA, EYU0NLRT, EYU0NMMC
A program used by the MAS subcomponent could not be disabled, where:
MAS processing continues. A user trace record is written to the CICS trace data set.
Follow the instructions associated with the respcode and eibrcode values for the EXEC CICS DISABLE command.
Console, job log, EYULOG
EYU0NLHD, EYU0NLRA, EYU0NLRT, EYU0NMMC
Under CICS/MVS 2.1.2, a program required by the MAS subcomponent could not be loaded, where:
The MAS interface to CICS catalog control is not available. MAS processing continues, but topology changes are not communicated to the CMAS. A user trace record is written to the CICS trace data set.
Follow the instructions associated with the respcode and eibrcode values
for the EXEC CICS LOAD command. Then stop the MAS by issuing the
STO action command from the MAS view. You can restart the MAS by
issuing the COLM (for a local MAS) transaction from CICS;
these transactions restart the CICSPlex SM MAS agent code in a running CICS system.
Console, job log, EYULOG
EYU0NLGT
The MAS heartbeat task, which issues notification events to the CICSPlex SM address space (CMAS) at regular intervals, terminated abnormally. The heartbeat task can not be restarted because the abnormal condition has occurred the maximum number of times allowed by CICSPlex SM, where:
The heartbeat task for the specified MAS is not restarted. MAS processing continues and the CICS system is unaffected. User trace records are written to the CICS trace data set. If the heartbeat task abended, a transaction dump is written to the CICS dump data set.
Collect the trace records and the transaction dump, if available, and contact your IBM Support Center.
Console, job log, EYULOG
EYU0NLRT, EYU1NLRT
The MAS heartbeat task, which issues notification events to the CICSPlex SM address space (CMAS) at regular intervals, terminated abnormally and is being restarted, where:
The heartbeat task for the specified MAS is automatically restarted.
None.
Console, job log, EYULOG
EYU0NLRT, EYU1NLRT
Monitoring of the specified resource terminated abnormally and can not be restarted because the abnormal condition has occurred the maximum number of times allowed by CICSPlex SM, where:
The monitoring task for the specified resource is not restarted. MAS processing, including other monitoring tasks, continues. User trace records are written to the CICS trace data set. If the monitoring task abended, a transaction dump is written to the CICS dump data set.
Use the MONDEF view to reinstall the monitor definitions for the specified resource. If the condition persists, collect the trace records and the transaction dump, if available, and contact your IBM Support Center.
Console, job log, EYULOG
EYU0NLRT, EYU1NLRT
Monitoring of the specified resource terminated abnormally and is being restarted, where:
The monitoring task for the specified resource is automatically restarted.
None.
Console, job log, EYULOG
EYU0NLRT, EYU1NLRT
Monitoring of DB2 resources was requested, but is not available for the specified release of DB2.
The monitoring task for DB2 (MDBX) is terminated. MAS processing, including the monitoring of other resources, continues.
Review the installation requirements for a list of the DB2 releases supported by CICSPlex SM. If a supported release of DB2 becomes available and you want to monitor its resources, you must restart monitoring for the DB2 resource class.
Console, job log, EYULOG
EYU0NM2T
Some or all MTRAN monitoring data is unavailable because CICSPlex SM was not able to process CICS monitor data at exit point XMNOUT, where:
CICSPlex SM monitoring of MTRAN resources continues but some or all performance data provided by the CICS monitor domain will be missing. Data provided by CICS statistics domain will be collected and reported at monitor sample intervals.
Collect AUXTRACE records and MAS and CMAS job logs and contact your IBM Support Center.
Console, job log, CMAS EYULOG
EYU0NMMC
During termination of a MAS, one or more MAS tasks could not be properly terminated; instead, the tasks were forcibly purged from the CICS system, where:
MAS termination continues. A series of task abend messages (EYUXL09nn) is written to the console for each task that was purged. This message is also accompanied by message EYUNL0149I. After all active tasks are forcibly purged, the MAS waits up to one minute for the tasks to terminate completely. MAS termination then continues and storage areas are freed. The disposition of any task remaining active is unpredictable.
If the condition persists, collect the trace records and the job log and contact your IBM Support Center.
Console, job log, EYULOG
EYU0NLRT, EYU1NLRT
All active MAS tasks are being terminated as a result of a MAS termination, where:
Termination ECB are posted for all active MAS tasks. The MAS waits one minute for the tasks to terminate, then continues its termination process.
None.
Console, job log, EYULOG
EYU0NLRT, EYU1NLRT
Topology data collection for the specified resource failed during the execution of an EXEC CICS command, where:
Topology data collection continues with the next resource.
Follow the instructions associated with the respcode and resp2code values
for the specified EXEC CICS command. To resume topology data collection
for the specified resource, first stop the MAS by issuing the STO
action command from the MAS view. Then restart the MAS by issuing
the COLM (for a local MAS) or CORM transaction from CICS;
these transactions restart the CICSPlex SM MAS agent code in a running CICS system.
Console, job log, EYULOG
EYU0NLGT, EYU1NLGT
Topology data collection for the specified resource returned no data. Either no data was available, or a problem occurred during the data collection process, where:
Topology data collection continues with the next resource.
If no topology data was expected for the specified resource, no action is required.
If topology data was expected, a problem may have occurred during data collection. In that case, this message is preceded by one of two messages, either EYUNL0150W or EYUNL0153W. Refer to the appropriate message for details on the cause of the problem.
EYULOG
EYU0NLGT, EYU1NLGT
Topology data collection for the specified resource failed before it could be completed, where:
Topology data collection continues with the next resource. A user trace record is written to the CICS trace data set.
Check for one of two messages that may have preceded this one:
Refer to the appropriate message for details on the cause of the problem. If the condition persists, collect the trace records and the job log and contact your IBM Support Center.
Console, job log, EYULOG
EYU0NLGT, EYU1NLGT
The collection of resource topology data by the MAS is complete. This message does not necessarily indicate that the data collection process was successful. If any problems occurred during data collection, they would be described in EYUNLnnnn or EYUTSnnnn messages issued before this one.
MAS topology processing is complete and the MAS is ready for work.
None.
EYULOG
EYULOG,
EYU0NLGT, EYU1NLGT
The region has been joined to the workload.
None.
None.
EYULOG
EYU0NLSP
During Topology Connect, an error has occurred during resource topology data retrieval in the MAS.
Topology Connect fails and the MAS Agent is terminated.
Check for any previous messages in the MAS job log that may indicate why the problem occurred. If the problem cannot be determined, collect the complete job output and auxtrace datasets from the MAS and the CMAS to which it was connecting, and any dumps that may have occurred in the MAS or CMAS, and contact your local IBM Support Center.
Console, job log, EYULOG
EYU0NLGT
The history recorder long running task has been successfully initialized.
CICSPlex SM processing continues. The task history recorder task is ready to accept details of completed CICS transactions.
None.
Console, job log
EYU0NHCT
The history recorder long running task has been terminated.
CICSPlex SM processing continues. No further task history recording will take place.
If termination of history recording is not expected examine earlier messages to determine why the history recorder terminated.
Console, job log
EYU0NHCT
The history recorder long running task has detected an abend.
The history recorder task will terminate and then attempt to restart. CICSPlex SM processing continues.
Check for previous messages to identify the cause of the abend or error that caused the history recorder to terminate. If you cannot determine the cause of the problem, collect the complete job log from the MAS, any dumps that may have been captured, the complete CMAS job log or EYULOG, and CMAS auxiliary trace data sets and contact your IBM support center.
Console, job log
EYU0NHCT
The long running task history recorder task in attempting to record a completed task on VSAM data set EYUHISTx found that the data set was full, and so has switched to start using data set EYUHISTy.
Task history recorder continues using data set EYUHISTy. The full data set EYUHISTx remains open and its data is available until such time that the history recorder has filled all data sets and requires use of EYUHISTx again. At this time EYUHISTx will be set closed, emptied and reopened, thereby destroying its previous contents.
None.
Console, job log
EYU0NHCT
The long running task history recorder task issued a CICS file control command or CICS SPI command against the specified history data set and received a bad response.
History recording terminates.
Examine the RESP and RESP2 values returned for the CICS command to identify the problem. If you cannot determine the cause of the problem, collect the complete job log from the MAS, any dumps that may have been captured, the complete CMAS job log or EYULOG and CMAS auxiliary trace data sets and contact your IBM support center.
Console, job log
EYU0NHCT
During initialization, the long running task history recorder task has detected that there was already an instance of the history recorder task active.
This instance of the history recorder task is terminated.
None.
Console, job log
EYU0NHCT
During initialization, the long running task history recorder task detected problems meaning that there no are history data sets available for it to record to.
The history recorder task is not started.
If you are sure that history recording will not be required on the local CICS region, this message is simply a confirmation that the history recorder process will not be startable. If you anticipate that task history recording will be required at some point during the execution of the current CICS region, you must ensure that the history data sets have been allocated to the local MAS region by means of DD cards. If allocated correctly, examine earlier messages to determine the problem. If you cannot determine the cause of the problem, collect the complete job log from the MAS, any dumps that may have been captured, the complete CMAS job log or EYULOG and CMAS auxiliary trace data sets and contact your IBM support center.
Console, job log
EYU0NHCT
The CICS definitions for the history data sets are created automatically during the initialization of the history recorder task. During this process, the program has determined that the default setting for the DATABUFFS parameter of the EXEC CICS CREATE for the dataset in question has been overridden with an invalid value. As such, the DATABUFFS value has been reset to that shown in this message.
CICS file creation for the history data sets continues using the value shown.
Re-adjust the HISTDBUFFS EYUPARM to an acceptable numeric value that is at least 1 greater than the HISTIBUFFS specification.
Console, job log
EYU0NHFM
The MAS history file manager detected problems meaning that it was unable to initialize the named history data set with its control information.
The named history data set is marked unuseable. The history recorder task is terminated.
Examine earlier messages to determine the problem. If you cannot determine the cause of the problem, collect the complete job log from the MAS, any dumps that may have been captured, the complete CMAS job log or EYULOG and CMAS auxiliary trace data sets and contact your IBM support center.
Console, job log
EYU0NHFM
Informational message detailing how many records have been written by the history recorder long running task to the named history data set. The display frequency of this message is controlled by the HISTRECSMSG EYUPARM.
Task history recording continues.
None.
Console, job log
EYU0NHCT
The history file manager detected an invalid number of history data sets (EYUHISTx). At least two history data sets (EYUHISTA and EYUHISTB) must be allocated to the MAS.
History recording is not activated.
Ensure that at least two history data sets have been allocated and that DD statements (EYUHISTA, EYUHISTB and so on in sequence) have been supplied for the datasets in the MAS JCL.
Console, job log
EYU0NHFM
Completed task history data is passed to the history recorder via a service queue that is loaded by the CPSM Monitor Data Global User Exit. This exit program places tasks data in pre-allocated data slots, or "buckets", to transport the completed task detail to the history long running task. When trying to acquire a free bucket to use for the current completed task detail, the GLUE has determined that there are no buckets available for use.
The Glue drops the current completed task datum, and increments a count of dropped records. When the history recorder completes the filing of it's outstanding data queue, it reports this dropped record count, and resets the counter to zero.
It is possible that this message may be issued occasionally during peaks of transaction processing on the local MAS. As such, it will be necessary to retune the settings of the controlling parameters of the history recorder to accommodate these processing peaks. This should be performed only under the advice and guidance of qualified CICS service personnel. Please contact you IBM support center to seek advice.
Console, job log
EYU0NHCT
Completed task history data is passed to the history ecorder via a service queue that is loaded by the CPSM Monitor Data Global User Exit. This exit program places tasks data in pre-allocated data slots, or "buckets", to transport the completed task detail to the history long running task. These buckets reside in a contiguous exit workarea within the MAS dataspace that is allocated by an asynchronous process controlled by the CMAS. When trying to acquire a free bucket (to use for the current completed task detail) the GLUE has determined that the controlling process has not completed the allocation of this exit workarea, and so no buckets are currently available for use.
The Glue drops the current completed task datum, and increments a count of dropped records. When the history recorder completes the filing of it's outstanding data queue, it reports this dropped record count, and resets the counter to zero.
It is possible that on a busy MAS, this condition may be reported because the GLUE will be gathering task data before the history recorder environment has completed initialization. If this condition is reported during regular transaction processing within the MAS, this indicates a more serious problem. Therefore, collect the complete job log from the MAS, any dumps that may have been captured, the complete CMAS job log or EYULOG and CMAS auxiliary trace data sets and contact your IBM support center.
Console, job log
EYU0NHCT
The MAS history file manager detected invalid attributes for the named history file. This message is followed by message EYUNL0185E which gives details of the invalid attribute.
The history recorder long running task is terminated.
Use the following EYUNL0185 message to determine which file attribute is invalid.
Console, job log
EYU0NHFM
This message is output in conjunction with message EYUNL0184E and gives details of an invalid attribute for a history file. The expected value and value detected are returned in the form of CICS CVDA values.
CICSPlex SM processing continues.
Use the information in the message to correct the history file attribute.
Console, job log
EYU0NHFM
The history recorder long running task has started receiving and storing completed task data. Prior to the display of this message, the history recorder was in a waiting state ready to process task data. This message indicates that the first completed task datum has been received and appropriately processed.
CICSPlex SM processing continues. The task history recorder task will continue to accept and process details of completed CICS transactions.
None.
Console, job log
EYU0NHCT
The long running task (LRT) for a MAS is being terminated because the CICS system it is associated with is being terminated, where:
Termination of the MAS continues.
None.
Console, job log, EYULOG
EYU0NLRT, EYU1NLRT
The long running task (LRT) for a MAS is being terminated as a result of a request from the CMAS that controls it, where:
Termination of the MAS continues. The CICS system continues to run normally, but it is no longer known to CICSPlex SM.
None.
Console, job log, EYULOG
EYU0NLRT, EYU1NLRT
The long running task (LRT) for a MAS is being terminated as a result of an error or abend in the LRT, where:
Termination of the MAS is attempted.
Check for previous messages to identify the cause of the abend or error that caused the LRT to terminate. If you cannot determine the cause of the problem, collect the complete joblog from the MAS, any dumps that may have been captured, the complete CMAS Joblog / EYULOG and CMAS auxillary trace data sets and contact your IBM support center.
Console, job log, EYULOG,
EYU0NLRT
An attempt to abnormally terminate the long running task (LRT) for a MAS has failed.
The MAS agent LRT completes but some MAS agent components may remain active. The MAS agent will not be able to be restarted in this CICS execution.
See the User Response for message ***, which should precede this message. You need to restart the CICS region before the MAS agent can reconnect.
Console, job log, EYULOG,
EYU0NLRT
An unrecoverable error has been detected during the execution of the MAS. The MAS agent is terminated.
After requesting an exception trace and a dump, the MAS agent is terminated.
Check if the cause of the error can be determined from previous error messages (for example, CICS SOS). If not, collect from the MAS the complete job output, the dump, and the auxtrace data set (if active) and contact your IBM Support Center
Console, job log, EYULOG
EYU0NLSD
This message is issued when the alternate long running task terminates normally, where:
MAS processing continues after the message is issued.
No action is required.
Console, job log, EYULOG
EYU0NLRA
No explanation available.
None.
None.
Module unknown.
Console and COLG
No explanation available.
None.
None.
Module unknown.
Console and COLG
No explanation available.
None.
None.
Module unknown.
Console and COLG
The long running task (LRT) for a MAS has been terminated, where:
The MAS subcomponent is removed from the CICS system. The CICS system either terminates or continues to run, as indicated by the message that precedes this one (either EYUNL0901I or EYUNL0902I).
None.
Console, job log, EYULOG
EYU0NLRT, EYU1NLRT