The following variables are used in EYUMMnnnn messages:
The CMAS Monitor Services component has been successfully initialized. Monitoring is now enabled.
CMAS initialization continues.
None.
EYULOG
EYU0MMIN
The CMAS Monitor Services component could not be initialized.
CMAS initialization continues, but Monitor Services is not available.
Refer to the messages issued before this one, to determine the cause of the problem.
Console, job log, EYULOG
EYU0MMIN
The CMAS Monitor Services component was not able to acquire enough storage for its major object environment block (MOEB).
CMAS initialization continues, but Monitor Services is not available.
Make more storage available to the CMAS by doing one of the following:
Console, job log, EYULOG
EYU0MMIN
The CMAS Monitor Services component was not able to allocate the required data cache.
CMAS initialization continues, but Monitor Services is not available. A user trace record is written to the CICS trace data set.
Examine the exception trace records and any related messages from the Data Cache component (EYUXCnnnn) to determine the cause of the problem.
Console, job log, EYULOG
EYU0MMIN
The CMAS Monitor Services component was not able to create a required internal work list.
CMAS initialization continues, but Monitor Services is not available. 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
EYU0MMIN
The CMAS Monitor Services component was not able to load the Resource Descriptor Table, EYUTMMDT.
CMAS initialization continues, but Monitor Services is not available.
Make sure the CICSPlex® SM load library contains all distributed modules.
Console, job log, EYULOG
EYU0MMIN
The CMAS Monitor Services component was not able to start its service task, EYU0MMST.
CMAS initialization continues, but Monitor Services is not available. 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
EYU0MMIN
The CMAS Monitor Services component received an unsolicited event record, where nn is the event notification ID that was not recognized by Monitor Services. Given the event notification ID, it is possible to determine which CICSPlex SM method created the event.
Monitor Services ignores the event record and continues processing. The invalid event record is written to the CICS trace data set.
Collect the trace records and any related messages and contact your IBM® Support Center.
Console, job log, EYULOG
EYU0MMST
The CMAS Monitor Services task has failed.
Monitor Services is not able to acknowledge MAS termination. A user trace record is written to the CICS trace data set. Monitoring continues for those MASs currently being monitored. If a MAS that is being monitored terminates, some Monitor Services resources, such as data cache, may remain allocated.
Restart the affected CMAS. Examine the exception trace records to determine the cause of the problem.
Console, job log, EYULOG
EYU0MMST
During CMAS initialization, Monitor Services was not able to start the data collector task for the specified resource type where restype is as described in the introduction to the EYUMMnnnn messages.
Monitoring of the specified resource type is not available for any MAS associated with the CMAS that was initializing. A user trace record is written to the CICS trace data set. CMAS initialization continues.
Examine the exception trace records to determine the cause of the problem. Then, if you want to monitor the specified resource type, stop and restart the CMAS.
Console, job log, EYULOG
EYU0MCCM
The data collector task for the specified resource type experienced a problem that caused it to terminate where restype is as described in the introduction to the EYUMMnnnn messages.
Monitor Services attempts to recover from the failure and restart the data collector task. Monitoring of that resource type is not available, however monitoring of other resource types continues.
Examine the exception trace records to determine the cause of the problem. If the problem persists, collect the trace records and the job log and contact your IBM Support Center.
Console, job log, EYULOG
EYU0MCCM
In attempting to recover the data collector task for the specified resource type, Monitor Services determined that the task had exceeded the maximum allowable number of failures where restype is as described in the introduction to the EYUMMnnnn messages.
The data collector task is terminated and monitoring of that resource type is no longer available. Monitoring of other resource types continues.
Collect the trace records and the job log and contact your IBM Support Center.
Console, job log, EYULOG
EYU0MCCM
The Monitor Services long running task experienced an internal error while attempting to process the specified event, where:
Monitor event processing continues. However, due to the event failure, some data or internal structures may be invalid or incomplete. A user trace record is written to the CICS trace data set.
Make a note of the event name, then collect the trace records and the job log and contact your IBM Support Center.
Console, job log, EYULOG
EYU0MMST
Monitoring has been stopped for the specified resource type in the specified context and scope where restype is as described in the introduction to the EYUMMnnnn messages. Monitor Services waits for the defined retention period before continuing with its resource cleanup procedure. The retention period for monitor data is defined as part of either a CICSSYS or MONSPEC definition; for more information, see CICSPlex System Manager Administration.
Processing continues.
None.
EYULOG
EYU0MMIS
The retention period for the specified resource type in the specified context and scope has expired where restype, context, and scope are as described in the introduction to the EYUMMnnnn messages. Monitor Services has successfully released all outstanding resources.
Processing continues.
None.
EYULOG
EYU0MMKL
The retention period for the specified resource type in the specified context and scope has expired where restype, context, and scope are as described in the introduction to the EYUMMnnnn messages. Monitor Services was not able to release one or more outstanding resources of the specified type.
Monitor Services continues its resource cleanup procedures. A user trace record is written to the CICS trace data set.
Examine the exception trace records to determine the cause of the problem. If the problem persists, collect the trace records and the job log and contact your IBM Support Center.
Console, job log, EYULOG
EYU0MMKL
A request has been issued to either remove a CICSplex or to remove a CICS system from a CICS system group where context and scope are as described in the introduction to the EYUMMnnnn messages. All monitor resources whose removal was pending in this context and scope (as indicated by message EYUMM0300I) are forcibly removed so that the CICSplex or CICS system can be removed successfully.
Processing continues.
None.
EYULOG
EYU0MPUD
As the result of a previous error condition, Monitor Services has stopped monitoring the specified resource type in the specified context and scope where restype, context, and scope are as described in the introduction to the EYUMMnnnn messages.
Monitor Services begins its resource removal processing for the specified resource type, as indicated by message EYUMM0300I. Monitoring of other resource types continues.
Check the job log for EYUMMnnnn messages issued previously that relate to the specified resource type. Because this message is not issued until the end of the monitoring interval, it may be separated from the related error message by as much as the length of an interval. If you cannot determine the cause of the problem, collect the job log and contact your IBM Support Center.
Console, job log, EYULOG
EYU0MAUD
Monitor Services has begun to reset the cache data fields for the specified context and scope to their predetermined values where context and scope are as described in the introduction to the EYUMMnnnn messages. The reset process, which occurs at the end of each monitoring performance interval, is done for all resources types currently being monitored.
Reset processing continues.
None.
EYULOG
EYU0MMEI
Monitor Services has successfully reset the cache data fields for the specified context and scope where context and scope are as described in the introduction to the EYUMMnnnn messages.
Processing continues.
None.
EYULOG
EYU0MMEI
A problem occurred while Monitor Services was attempting to reset the cache data fields for the specified context and scope where context and scope are as described in the introduction to the EYUMMnnnn messages.
Processing continues with the next managed application system (MAS) in the context for which monitoring is active. A user trace record is written to the CICS trace data set. Partial or incomplete monitoring data may be reported.
Collect the exception trace records and any related messages and contact your IBM Support Center.
Console, job log, EYULOG
EYU0MMEI
A request to install the specified monitoring criteria for the specified context and scope was successful where context and scope are as described in the introduction to the EYUMMnnnn messages, where:
Processing continues.
None.
EYULOG
EYU0MMIC
A request to install the specified monitoring criteria for the specified context and scope was not successful where context and scope are as described in the introduction to the EYUMMnnnn messages, where:
Processing continues. A user trace record is written to the CICS trace data set.
Collect the trace records, the reason code and the reason text and contact your IBM Support Center.
Console, job log, EYULOG
EYU0MMIC
A request was made against the specified monitor definition in the specified monitor group, but the definition could not be found in the data repository.
Processing continues.
Make sure the definition name was correctly specified in the request. If necessary, add the definition to the data repository.
Console, job log, EYULOG
EYU0MMIR
An attempt by Monitor Services to start a monitoring agent in the specified context and scope was unsuccessful where restype, context, and scope are as described in the introduction to the EYUMMnnnn messages.
Processing continues, however monitoring is not active for the specified resource type in the specified context and scope. A user trace record is written to the CICS trace data set.
Examine the exception trace records to determine the cause of the problem. If the problem persists, collect the trace records and the job log and contact your IBM Support Center.
Console, job log, EYULOG
EYU0MMCL
While attempting to install transaction monitoring definitions, Monitor Services tried to start an end of transaction data collector, but was unsuccessful.
The installation of the monitor definitions fails. A user trace record is written to the CICS trace data set.
Collect the exception trace records and any related messages and contact your IBM Support Center.
Console, job log, EYULOG
EYU0MMCL
During installation of a monitor specification, group, or definition, tt install requests were made in the specified context and scope, but nn requests failed where context and scope are as described in the introduction to the EYUMMnnnn messages.
Prior to this message, an EYUMM0601E message is issued for each install request that failed.
The monitor definition install process 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. If the problem persists, collect the trace records and the job log and contact your IBM Support Center.
Console, job log, EYULOG
EYU0MMID
During installation of a monitor specification, group, or definition, a certain number of definitions could not be installed in the specified CICS system, where restype, context, and scope are as described in the introduction to the EYUMMnnnn messages, and where:
The monitor definition install process continues. Monitoring of the specified resource type is not available on the specified CICS system.
Depending on the reason value, do one of the following:
Console, job log, EYULOG
EYU0MMIB
During installation of a monitor specification, group, or definition, Monitor Services attempted to register interest in the specified time period, but the period definition does not exist where context and scope are as described in the introduction to the EYUMMnnnn messages. The specified number of definitions, which reference the time period, could not be installed, where:
The monitor definition install process continues. Any monitor definitions that reference the specified time period are not installed.
Make sure the time period name was specified correctly on the MONINGRP view. You can use the PERIODEF view to display a list of existing time period definitions and, if necessary, create a new one. Then, reinstall the monitor definitions using the correct time period name.
Console, job log, EYULOG
EYU0MMIC
The CMAS Monitor Services component was not able to purge its data cache during termination processing.
Monitor Services termination continues.
Examine the exception trace records and any related messages from the Data Cache component (EYUXCnnnn) to determine the cause of the problem.
Console, job log, EYULOG
EYU0MMTM
The CMAS Monitor Services component was not able to release its major object environment block (MOEB) during termination processing.
Monitor Services termination continues.
Examine the exception trace records to determine the cause of the problem.
Console, job log, EYULOG
EYU0MMTM
One or more errors occurred while attempting to terminate the CMAS Monitor Services component.
CMAS termination continues. A user trace record is written to the CICS trace data set.
Collect the exception trace records and any related messages and contact your IBM Support Center.
Console, job log, EYULOG
EYU0MMTM
An attempt by the CMAS Monitor Services component to unregister interest in CICSPlex SM events was unsuccessful.
Monitor Services termination continues.
Examine the exception trace records to determine the cause of the problem.
Console, job log, EYULOG
EYU0MMTM
The CMAS Monitor Services component has been terminated. Resource monitoring is no longer available.
CMAS termination continues.
None.
EYULOG
EYU0MMTM