EYUMMnnnn messages

The following variables are used in EYUMMnnnn messages:

restype
Identifies the type of resource involved as one of the following:
  • All
  • CICS®
  • Connection
  • Data Base
  • File
  • Global
  • Journal
  • Program
  • Terminal
  • Transaction
  • Transient Data Queue
  • Unknown
context
Identifies the CICSplex to which the message applies.
scope
Identifies the CICS systems to which the message applies.
EYUMM0001I
Monitor Initialization Complete
Explanation:

The CMAS Monitor Services component has been successfully initialized. Monitoring is now enabled.

System action:

CMAS initialization continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0MMIN

EYUMM0002E
Monitor Initialization Failed
Explanation:

The CMAS Monitor Services component could not be initialized.

System action:

CMAS initialization continues, but Monitor Services is not available.

User response:

Refer to the messages issued before this one, to determine the cause of the problem.

Destination:

Console, job log, EYULOG

Module:

EYU0MMIN

EYUMM0071E
Monitor MOEB Initialization Failed
Explanation:

The CMAS Monitor Services component was not able to acquire enough storage for its major object environment block (MOEB).

System action:

CMAS initialization continues, but Monitor Services is not available.

User response:

Make more storage available to the CMAS by doing one of the following:

Destination:

Console, job log, EYULOG

Module:

EYU0MMIN

EYUMM0072E
Monitor Data Cache Create Failed
Explanation:

The CMAS Monitor Services component was not able to allocate the required data cache.

System action:

CMAS initialization continues, but Monitor Services is not available. A user trace record is written to the CICS trace data set.

User response:

Examine the exception trace records and any related messages from the Data Cache component (EYUXCnnnn) to determine the cause of the problem.

Destination:

Console, job log, EYULOG

Module:

EYU0MMIN

EYUMM0073E
Monitor List Header Initialization Failed
Explanation:

The CMAS Monitor Services component was not able to create a required internal work list.

System action:

CMAS initialization continues, but Monitor Services is not available. A user trace record is written to the CICS trace data set.

User response:

Examine the exception trace records to determine the cause of the problem.

Destination:

Console, job log, EYULOG

Module:

EYU0MMIN

EYUMM0074E
Monitor Cache Attribute Table Initialization Failed
Explanation:

The CMAS Monitor Services component was not able to load the Resource Descriptor Table, EYUTMMDT.

System action:

CMAS initialization continues, but Monitor Services is not available.

User response:

Make sure the CICSPlex® SM load library contains all distributed modules.

Destination:

Console, job log, EYULOG

Module:

EYU0MMIN

EYUMM0075E
Monitor Administration Service Task Start Failure
Explanation:

The CMAS Monitor Services component was not able to start its service task, EYU0MMST.

System action:

CMAS initialization continues, but Monitor Services is not available. A user trace record is written to the CICS trace data set.

User response:

Examine the exception trace records to determine the cause of the problem.

Destination:

Console, job log, EYULOG

Module:

EYU0MMIN

EYUMM0076E
Monitor has encountered an unknown event notification (nn) event ignored
Explanation:

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.

System action:

Monitor Services ignores the event record and continues processing. The invalid event record is written to the CICS trace data set.

User response:

Collect the trace records and any related messages and contact your IBM® Support Center.

Destination:

Console, job log, EYULOG

Module:

EYU0MMST

EYUMM0077E
Monitor Administration Service Task has had a failure - Task will be Terminated.
Explanation:

The CMAS Monitor Services task has failed.

System action:

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.

User response:

Restart the affected CMAS. Examine the exception trace records to determine the cause of the problem.

Destination:

Console, job log, EYULOG

Module:

EYU0MMST

EYUMM0079E
Monitor was unable to start a restype data collector task
Explanation:

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.

System action:

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.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0MCCM

EYUMM0080E
Monitor data collector task has failed for restype resources
Explanation:

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.

System action:

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.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0MCCM

EYUMM0081E
Monitor data collector task has terminated due to excessive failures for restype resources
Explanation:

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.

System action:

The data collector task is terminated and monitoring of that resource type is no longer available. Monitoring of other resource types continues.

User response:

Collect the trace records and the job log and contact your IBM Support Center.

Destination:

Console, job log, EYULOG

Module:

EYU0MCCM

EYUMM0082W
Monitor has reported an error processing event name
Explanation:

The Monitor Services long running task experienced an internal error while attempting to process the specified event, where:

name
Identifies the event as one of the following:
  • CsysChg
  • EndOfPer
  • ENetDisc
  • MasJoin
  • MasStart
  • MasStop
  • MonSick
  • PlexChg
  • TimeChg
System action:

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.

User response:

Make a note of the event name, then collect the trace records and the job log and contact your IBM Support Center.

Destination:

Console, job log, EYULOG

Module:

EYU0MMST

EYUMM0300I
Monitor resource removal pending for restype for Context(context) Scope(scope)
Explanation:

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.

System action:

Processing continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0MMIS

EYUMM0301I
Monitor resource removal complete for restype for Context(context) Scope(scope)
Explanation:

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.

System action:

Processing continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0MMKL

EYUMM0302E
Monitor resource removal was unsuccessful for restype Context(context) Scope(scope)
Explanation:

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.

System action:

Monitor Services continues its resource cleanup procedures. A user trace record is written to the CICS trace data set.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0MMKL

EYUMM0303I
Monitor resource removal being forced for Context(context) Scope(scope)
Explanation:

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.

System action:

Processing continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0MPUD

EYUMM0304W
Monitoring has been stopped for restype resources for Context(context) Scope(scope)
Explanation:

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.

System action:

Monitor Services begins its resource removal processing for the specified resource type, as indicated by message EYUMM0300I. Monitoring of other resource types continues.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0MAUD

EYUMM0400I
Monitor resource reset in progress for Context(context) Scope(scope)
Explanation:

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.

System action:

Reset processing continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0MMEI

EYUMM0401I
Monitor resource reset complete for Context(context) Scope(scope)
Explanation:

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.

System action:

Processing continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0MMEI

EYUMM0402E
Monitor resource reset failed for Context(context) Scope(scope)
Explanation:

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.

System action:

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.

User response:

Collect the exception trace records and any related messages and contact your IBM Support Center.

Destination:

Console, job log, EYULOG

Module:

EYU0MMEI

EYUMM0600I
Monitoring type (name) has been successfully installed for Context(context) Scope(scope)
Explanation:

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:

type
Identifies the type of monitoring criteria that was installed as one of the following:
  • Definition
  • Group
  • Specification
  • Time Definition
name
Is the user-defined name for that criteria.
System action:

Processing continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0MMIC

EYUMM0601E
Monitoring type (name) failed to install for Context(context) Scope(scope) Reason: code -- text
Explanation:

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:

type
Identifies the type of monitoring criteria that could not be installed as one of the following:
  • Definition
  • Group
  • Specification
  • Time Definition
name
Is the user-defined name for that criteria.
code
Supplies the reason code.
text
Supplies the diagnostic text.
System action:

Processing continues. A user trace record is written to the CICS trace data set.

User response:

Collect the trace records, the reason code and the reason text and contact your IBM Support Center.

Destination:

Console, job log, EYULOG

Module:

EYU0MMIC

EYUMM0602E
Monitoring definition (defname) of Group (grpname) could not be located, request ignored
Explanation:

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.

System action:

Processing continues.

User response:

Make sure the definition name was correctly specified in the request. If necessary, add the definition to the data repository.

Destination:

Console, job log, EYULOG

Module:

EYU0MMIR

EYUMM0603E
Unsuccessful start for restype monitoring for Context(context) Scope(scope)
Explanation:

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.

System action:

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.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0MMCL

EYUMM0604E
Start failed for Monitor End of Transaction data collector
Explanation:

While attempting to install transaction monitoring definitions, Monitor Services tried to start an end of transaction data collector, but was unsuccessful.

System action:

The installation of the monitor definitions fails. A user trace record is written to the CICS trace data set.

User response:

Collect the exception trace records and any related messages and contact your IBM Support Center.

Destination:

Console, job log, EYULOG

Module:

EYU0MMCL

EYUMM0605E
Monitor had nn out of tt type install failures for Context(context) Scope(scope)
Explanation:

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.

type
Identifies the type of monitoring criteria that was being installed as one of the following:
  • Definition
  • Group
  • Specification
  • Time Definition

Prior to this message, an EYUMM0601E message is issued for each install request that failed.

System action:

The monitor definition install process continues. A user trace record is written to the CICS trace data set.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0MMID

EYUMM0606W
Monitor could not install nn restype resource definition(s) for Context(context) Scope(scope) - reason.
Explanation:

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:

nn
Identifies how many definitions could not be installed.
reason
Indicates the definitions could not be installed for one of the following reasons:
A zero sample interval
The sample interval for the specified resource type was zero, which means no monitor sampling will occur.
Resource not supported
The specified CICS system does not support the specified resource. For example, a definition to monitor DB2® resources cannot be installed in a CICS/VSE system because CICS/VSE does not support DB2.
System action:

The monitor definition install process continues. Monitoring of the specified resource type is not available on the specified CICS system.

User response:

Depending on the reason value, do one of the following:

A zero sample interval
Use the MAS view to set the monitoring sample interval for the specified resource type to a nonzero value. Then, reinstall the monitor definitions for that resource type.
Resource not supported
To prevent this message from appearing the next time monitor definitions are installed, limit the scope associated with the specified resource definitions to CICS systems that support the resource. To determine if a particular resource is supported by a particular platform or release of CICS, refer to the CICSPlex System Manager Resource Tables Reference book.
Destination:

Console, job log, EYULOG

Module:

EYU0MMIB

EYUMM0607W
Monitor could not install nn definition(s) for Context(context) Scope(scope) due to Time Period(defname) not being defined.
Explanation:

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:

nn
Identifies how many definitions could not be installed.
defname
Is the name of the time period definition that could not be found.
System action:

The monitor definition install process continues. Any monitor definitions that reference the specified time period are not installed.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0MMIC

EYUMM0903E
Monitor Data Cache Delete Failed
Explanation:

The CMAS Monitor Services component was not able to purge its data cache during termination processing.

System action:

Monitor Services termination continues.

User response:

Examine the exception trace records and any related messages from the Data Cache component (EYUXCnnnn) to determine the cause of the problem.

Destination:

Console, job log, EYULOG

Module:

EYU0MMTM

EYUMM0904E
Monitor MOEB Delete Failed
Explanation:

The CMAS Monitor Services component was not able to release its major object environment block (MOEB) during termination processing.

System action:

Monitor Services termination continues.

User response:

Examine the exception trace records to determine the cause of the problem.

Destination:

Console, job log, EYULOG

Module:

EYU0MMTM

EYUMM0905E
Monitor Termination Failed
Explanation:

One or more errors occurred while attempting to terminate the CMAS Monitor Services component.

System action:

CMAS termination continues. A user trace record is written to the CICS trace data set.

User response:

Collect the exception trace records and any related messages and contact your IBM Support Center.

Destination:

Console, job log, EYULOG

Module:

EYU0MMTM

EYUMM0906E
Monitor event notification unregistration Failed
Explanation:

An attempt by the CMAS Monitor Services component to unregister interest in CICSPlex SM events was unsuccessful.

System action:

Monitor Services termination continues.

User response:

Examine the exception trace records to determine the cause of the problem.

Destination:

Console, job log, EYULOG

Module:

EYU0MMTM

EYUMM0999I
Monitor Termination Complete
Explanation:

The CMAS Monitor Services component has been terminated. Resource monitoring is no longer available.

System action:

CMAS termination continues.

User response:

None.

Destination:

EYULOG

Module:

EYU0MMTM

[[ Contents Previous Page | Next Page Index ]]