EYUNLnnnn messages

The following variables are used in EYUNLnnnn messages:

eibrcode
The EIBRCODE= value as returned by CICS®.
respcode
The RESP= value as returned by CICS.
resp2code
The RESP2= value as returned by CICS.

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.

EYUNL0001E
MOEB registration failed
Explanation:

The MAS subcomponent was not able to register its major object environment block (MOEB) control block with the Kernel Linkage component.

System action:

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.

User response:

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

Destination:

Console, job log, EYULOG

Module:

EYU0NLRT, EYU1NLRT

EYUNL0002E
Termination ECB registration failed
Explanation:

The MAS subcomponent was not able to register its termination ECB with the Kernel Linkage component.

System action:

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.

User response:

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

Destination:

Console, job log, EYULOG

Module:

EYU0NLRT

EYUNL0003E
GETMAIN for MOEB storage failed
Explanation:

The MAS subcomponent was not able to acquire the necessary storage for its major object environment block (MOEB) control block.

System action:

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.

User response:

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

Destination:

Console, job log, EYULOG

Module:

EYU1NLRT

EYUNL0007E
Communications Receiver Block not available
Explanation:

The address of the Communications Receiver Block required for MAS-to-CMAS communications is zero. MAS-to-CMAS communications is not available.

System action:

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.

User response:

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

Destination:

Console, job log, EYULOG

Module:

EYU0NLRT, EYU1NLRT

EYUNL0010E
Parameter Services query failed
Explanation:

A request was issued to CICSPlex SM Parameter Services and it returned an abnormal response.

System action:

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.

User response:

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

Destination:

Console, job log, EYULOG

Module:

EYU0NLRT, EYU1NLRT

Start of change
EYUNL0087E
EXEC CICS SET TRANSACTION request for CONA failed
Explanation:

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.

System action:

MAS agent initialization continues after the message is issued.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0NLRT

End of change
Start of change
EYUNL0088I
(a ) alternate LRTs were requested and (b ) were started
Explanation:

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:

a
Is the number of CONA tasks that were attempted to be started (the value of the MASALTLRTCNT parm).
b
Is the actual number of tasks that EYU0NLRT successfully started.
System action:

MAS agent initialization continues after the message is issued.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0NLRT

End of change
Start of change
EYUNL0089I
Alternate LRT is performing message processing
Explanation:

This message is issued when the first alternate long running task in a MAS processes a request.

System action:

MAS processing continues after the message is issued.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0NLRA

End of change
EYUNL0090W
addspace is shutting down because it failed to become available to process requests
Explanation:

After initialization completed, the managed application system (MAS) determined that the heartbeat task was not active and initiated a normal shutdown, where:

addspace
Start of changeIdentifies the MAS as a local (LMAS).End of change
System action:

The CICS system continues to run normally, but it is not known to CICSPlex SM.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0NLRT

Start of change
EYUNL0096E
Alternate LRT (n ) is terminating abnormally
Explanation:

This message is issued when the alternate long running task terminates with an error, where:

n
Is the number of the CONA task that is terminating.
System action:

MAS processing continues after the message is issued.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0NLRA

End of change
EYUNL0098E
addspace LRT initialization failed
Explanation:

The long running task (LRT) for a MAS could not be initialized, where:

addspace
Start of changeIdentifies the MAS as a local (LMAS).End of change
System action:

MAS initialization terminates. The CICS system continues to run normally, but it is not known to CICSPlex SM.

User response:

Refer to the messages preceding this one for details on the cause of the problem.

Destination:

Start of changeConsole, job log, EYULOG,End of change

Module:

EYU0NLRT, EYU1NLRT

EYUNL0099I
addspace LRT initialization complete
Explanation:

The long running task (LRT) for a MAS has been successfully initialized, where:

addspace
Start of changeIdentifies the MAS as a local (LMAS).End of change
System action:

The MAS is ready for work. CICSPlex SM processing continues.

User response:

None

Destination:

Start of changeConsole, job log, EYULOGEnd of change

Module:

EYU0NLRT, EYU1NLRT

EYUNL0101W
Method not supported: Format ID=id
Explanation:

Another component of CICSPlex SM made a request that is not supported by the MAS subcomponent, where:

id
Is the request identifier.
System action:

The request is ignored. MAS processing continues.

User response:

None.

Destination:

Console, job log, EYULOG

Module:

EYU0NLRT

EYUNL0103E
WAIT EXTERNAL failed, RESP=respcode RESP2=resp2code
Explanation:

An EXEC CICS WAIT EXTERNAL command returned an abnormal response. The respcode and resp2code values are as returned by CICS.

System action:

The MAS attempts a normal shutdown. A user trace record is written to the CICS trace data set.

User response:

Follow the instructions associated with the respcode and resp2code values for the EXEC CICS WAIT EXTERNAL command.

Destination:

Console, job log, EYULOG

Module:

Start of changeEYU0NLRT, EYU0NLRAEnd of change

EYUNL0105E
Lock Services failed. Message processing is inoperative.
Explanation:

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.

System action:

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.

User response:

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

Destination:

Console, job log, EYULOG

Module:

Start of changeEYU0NLRT, EYU0NLRAEnd of change

EYUNL0120W
ENABLE PROGRAM prgmid failed, RESP=respcode EIBRCODE=eibrcode
Explanation:

A program required by the MAS subcomponent could not be enabled, where:

prgmid
Identifies the program that could not be enabled as one of the following:
  • EYU9NLDC
  • EYU9NLDO
  • EYU9NLDR
  • EYU9NLID (CICS/ESA 4.1 or later)
  • EYU9NLME
  • EYU9NMST
  • EYU9NMTE
  • EYU9NMT2 (CICS/MVS™ 2.1.2 only)
  • EYU9XLAP
respcode
Value is as returned by CICS.
eibrcode
Value is as returned by CICS.
System action:

The impact on system processing depends on which program could not be enabled:

EYU9NLDC
The XDUREQC Dump Domain exit is not available. MAS processing continues. Transaction dump completion will be detected by the XDUOUT exit. System dump completion will be detected by the heartbeat task.
EYU9NLDO
The XDUOUT Dump Domain exit is not available. MAS processing continues, but transaction dump (well health) notifications are not issued.
EYU9NLDR
The XDUREQ Dump Domain exit is not available. MAS processing continues, but transaction dump and system dump (sick health) notifications are not issued.
EYU9NLID
The XRSINDI exit is not available. MAS processing continues, but topology changes are not communicated to the CMAS.
EYU9NLME
The XMEOUT Message Domain exit is not available. MAS processing continues, but topology changes are not communicated to the CMAS.
EYU9NMST
The XMNOUT Monitoring Domain exit is not available. MAS processing continues, but end-of-task monitoring data are not collected.
EYU9NMTE
The XSTOUT Statistics Domain exit is not available. MAS processing continues, but monitoring statistics data are lost.
EYU9NMT2
For CICS/MVS 2.1.2 systems, the monitoring exit is not available. MAS processing continues, but end-of-task monitoring data are not collected.
EYU9XLAP
The CICSPlex SM API is not available. MAS processing continues, but the MAS cannot be accessed by API programs.

In all cases, a user trace record is written to the CICS trace data set.

User response:

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:

EYU9NLDO, EYU9NLDR, EYU9NLID, EYU9NLME, EYU9NMST, or EYU9XLAP
Start of changeStop the MAS by issuing the STO action command from the MAS view. Then 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.End of change
EYU9NMTE or EYU9NMT2
Stop and restart CICSPlex SM transaction monitoring by using the the CICSSYS view to update the CICS system definition. Specify a sample rate of zero to stop transaction monitoring; change the sample rate back to a nonzero value to restart transaction monitoring.
Destination:

Console, job log, EYULOG

Module:

Start of changeEYU0NLGT, EYU0NLHD, EYU0NLRA, EYU0NLRT, EYU0NMMCEnd of change

EYUNL0123W
DISABLE PROGRAM prgmid failed, RESP=respcode EIBRCODE=eibrcode
Explanation:

A program used by the MAS subcomponent could not be disabled, where:

prgmid
Identifies the program that could not be disabled as one of the following:
  • EYU9NLDO
  • EYU9NLDR
  • EYU9NLID (CICS/ESA 4.1 or later)
  • EYU9NLME
  • EYU9NMST
  • EYU9NMTE
  • EYU9NMT2 (CICS/MVS 2.1.2 only)
  • EYU9XLAP
respcode
Value is as returned by CICS.
eibrcode
Value is as returned by CICS.
System action:

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

User response:

Follow the instructions associated with the respcode and eibrcode values for the EXEC CICS DISABLE command.

Destination:

Console, job log, EYULOG

Module:

Start of changeEYU0NLHD, EYU0NLRA, EYU0NLRT, EYU0NMMCEnd of change

EYUNL0125W
LOAD PROGRAM EYU9NLM2 failed, RESP=respcode EIBRCODE=eibrcode
Explanation:

Under CICS/MVS 2.1.2, a program required by the MAS subcomponent could not be loaded, where:

respcode
Value is as returned by CICS.
eibrcode
Value is as returned by CICS.
System action:

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.

User response:

Start of changeFollow 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.End of change

Destination:

Console, job log, EYULOG

Module:

EYU0NLGT

EYUNL0130W
addspace heartbeat terminated. Retry limit reached.
Explanation:

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:

addspace
Start of changeIdentifies the MAS as a local (LMAS).End of change
System action:

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.

User response:

Collect the trace records and the transaction dump, if available, and contact your IBM Support Center.

Destination:

Console, job log, EYULOG

Module:

EYU0NLRT, EYU1NLRT

EYUNL0131W
addspace heartbeat terminated. Being restarted.
Explanation:

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:

addspace
Start of changeIdentifies the MAS as a local (LMAS).End of change
System action:

The heartbeat task for the specified MAS is automatically restarted.

User response:

None.

Destination:

Console, job log, EYULOG

Module:

EYU0NLRT, EYU1NLRT

EYUNL0140W
restype monitoring terminated. Retry limit reached.
Explanation:

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:

restype
Identifies the type of resource for which monitoring terminated as one of the following:
Start of changeHTASKEnd of change
Start of changeCompleted taskEnd of change
MCICS
CICS systems
MCONN
Connections and modenames
MDBX
DB2® and DBCTL resources
MFILE
Files
MGLBL
Global resources
MJRNL
Journals
MPROG
Programs
MTDQS
Transient data queues
MTERM
Terminals
MTRAN
Transactions
System action:

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.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0NLRT, EYU1NLRT

EYUNL0141W
restype monitoring terminated. Being restarted.
Explanation:

Monitoring of the specified resource terminated abnormally and is being restarted, where:

restype
Identifies the type of resource for which monitoring terminated as one of the following:
Start of changeHTASKEnd of change
Start of changeCompleted taskEnd of change
MCICS
CICS systems
MCONN
Connections and modenames
MDBX
DB2 and DBCTL resources
MFILE
Files
MGLBL
Global resources
MJRNL
Journals
MPROG
Programs
MTDQS
Transient data queues
MTERM
Terminals
MTRAN
Transactions
System action:

The monitoring task for the specified resource is automatically restarted.

User response:

None.

Destination:

Console, job log, EYULOG

Module:

EYU0NLRT, EYU1NLRT

EYUNL0142W
MDBX monitoring terminated. DB2 release level not supported.
Explanation:

Monitoring of DB2 resources was requested, but is not available for the specified release of DB2.

System action:

The monitoring task for DB2 (MDBX) is terminated. MAS processing, including the monitoring of other resources, continues.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0NM2T

Start of change
EYUNL0143W
MTRAN monitoring data incomplete - CICS Monitor data reason
Explanation:

Some or all MTRAN monitoring data is unavailable because CICSPlex SM was not able to process CICS monitor data at exit point XMNOUT, where:

reason
Identifies the reason why CICS monitor data could not be processed:
missing
The work area for dictionary data was too small. All performance data will be discarded.
truncated
The buffers used to pass performance data to the CICSPlex SM monitor component were too small. Performance records will be truncated.
System action:

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.

User response:

Collect AUXTRACE records and MAS and CMAS job logs and contact your IBM Support Center.

Destination:

Console, job log, CMAS EYULOG

Module:

EYU0NMMC

End of change
EYUNL0148W
Warning - active MAS tasks force purged during addspace termination
Explanation:

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:

addspace
Start of changeIdentifies the MAS as a local (LMAS).End of change
System action:

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.

User response:

If the condition persists, collect the trace records and the job log and contact your IBM Support Center.

Destination:

Console, job log, EYULOG

Module:

EYU0NLRT, EYU1NLRT

EYUNL0149I
Active MAS tasks being terminated by LRT for addspace termination
Explanation:

All active MAS tasks are being terminated as a result of a MAS termination, where:

addspace
Start of changeIdentifies the MAS as a local (LMAS).End of change
System action:

Termination ECB are posted for all active MAS tasks. The MAS waits one minute for the tasks to terminate, then continues its termination process.

User response:

None.

Destination:

Console, job log, EYULOG

Module:

EYU0NLRT, EYU1NLRT

EYUNL0150W
Get Topology for resource restype failed, COMMAND=cmdname RESP=respcode RESP2=resp2code
Explanation:

Topology data collection for the specified resource failed during the execution of an EXEC CICS command, where:

restype
Identifies the type of resource for which data collection failed as one of the following:
  • AUTINSTMODEL
  • CFDT POOL
  • CONNECTION
  • DATA SET NAMES
  • DB2 CONNECTION
  • DB2 ENTRY
  • DB2 TRANSACTION
  • ENQUEUE MODEL
  • FEPI CONNECTIONS
  • FEPI NODE
  • FEPI POOL
  • FEPI TARGET
  • FILE
  • GLOBAL EXITS
  • JOURNAL
  • JOURNALNAMES
  • MODENAME
  • PARTNER
  • PROCESS TYPE
  • PROFILE
  • PROGRAM
  • REQUEST MODEL
  • SYSTEM DUMP CODES
  • TASK EXITS
  • TCP/IP SERVICE
  • TDQUEUE
  • TEMP STORAGE MODEL
  • TERMINAL
  • TRANCLASS
  • TRANSACTION DUMP CODES
  • TRANSACTION
cmdname
Identifies the EXEC CICS command that was being issued as either START or NEXT.
respcode
Value is as returned by CICS.
resp2code
Value is as returned by CICS.
System action:

Topology data collection continues with the next resource.

User response:

Start of changeFollow 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.End of change

Destination:

Console, job log, EYULOG

Module:

EYU0NLGT, EYU1NLGT

EYUNL0151I
Get Topology for resource restype has zero data records
Explanation:

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:

restype
Identifies the type of resource for which no data was returned as one of the following:
  • AUTINSTMODEL
  • CFDT POOL
  • CONNECTION
  • DATA SET NAMES
  • DB2 CONNECTION
  • DB2 ENTRY
  • DB2 TRANSACTION
  • ENQUEUE MODEL
  • FEPI CONNECTIONS
  • FEPI NODE
  • FEPI POOL
  • FEPI TARGET
  • FILE
  • GLOBAL EXITS
  • JOURNAL
  • JOURNALNAMES
  • MODENAME
  • PARTNER
  • PROCESS TYPE
  • PROFILE
  • PROGRAM
  • REQUEST MODEL
  • SYSTEM DUMP CODES
  • TASK EXITS
  • TCP/IP SERVICE
  • TDQUEUE
  • TEMP STORAGE MODEL
  • TERMINAL
  • TRANCLASS
  • TRANSACTION DUMP CODES
  • TRANSACTION
System action:

Topology data collection continues with the next resource.

User response:

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.

Destination:

EYULOG

Module:

EYU0NLGT, EYU1NLGT

EYUNL0153W
Get Topology for resource restype is incomplete
Explanation:

Topology data collection for the specified resource failed before it could be completed, where:

restype
Identifies the type of resource for which data collection was incomplete as one of the following:
  • AUTINSTMODEL
  • CFDT POOL
  • CONNECTION
  • DATA SET NAMES
  • DB2 CONNECTION
  • DB2 ENTRY
  • DB2 TRANSACTION
  • ENQUEUE MODEL
  • FEPI CONNECTIONS
  • FEPI NODE
  • FEPI POOL
  • FEPI TARGET
  • FILE
  • GLOBAL EXITS
  • JOURNAL
  • JOURNALNAMES
  • MODENAME
  • PARTNER
  • PROCESS TYPE
  • PROFILE
  • PROGRAM
  • REQUEST MODEL
  • SYSTEM DUMP CODES
  • TASK EXITS
  • TCP/IP SERVICE
  • TDQUEUE
  • TEMP STORAGE MODEL
  • TERMINAL
  • TRANCLASS
  • TRANSACTION DUMP CODES
  • TRANSACTION
System action:

Topology data collection continues with the next resource. A user trace record is written to the CICS trace data set.

User response:

Check for one of two messages that may have preceded this one:

EYUNL0150W
A problem occurred with an EXEC CICS command.
EYUTS0021E
The request for MAS topology timed out.

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.

Destination:

Console, job log, EYULOG

Module:

EYU0NLGT, EYU1NLGT

EYUNL0159I
Resource topology data retrieval complete
Explanation:

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.

System action:

MAS topology processing is complete and the MAS is ready for work.

User response:

None.

Destination:

EYULOG

Start of changeEYULOG,End of change

Module:

EYU0NLGT, EYU1NLGT

EYUNL0160I
Workload registration complete
Explanation:

The region has been joined to the workload.

System action:

None.

User response:

None.

Destination:

EYULOG

Module:

EYU0NLSP

Start of change
EYUNL0161E
Resource topology data retrieval failed
Explanation:

During Topology Connect, an error has occurred during resource topology data retrieval in the MAS.

System action:

Topology Connect fails and the MAS Agent is terminated.

User response:

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.

Destination:

Console, job log, EYULOG

Module:

EYU0NLGT

End of change
Start of change
EYUNL0170I
Task History Recorder has been activated
Explanation:

The history recorder long running task has been successfully initialized.

System action:

CICSPlex SM processing continues. The task history recorder task is ready to accept details of completed CICS transactions.

User response:

None.

Destination:

Console, job log

Module:

EYU0NHCT

End of change
Start of change
EYUNL0171I
Task History Recorder has been terminated
Explanation:

The history recorder long running task has been terminated.

System action:

CICSPlex SM processing continues. No further task history recording will take place.

User response:

If termination of history recording is not expected examine earlier messages to determine why the history recorder terminated.

Destination:

Console, job log

Module:

EYU0NHCT

End of change
Start of change
EYUNL0172E
An abend has occurred within Task History Recorder
Explanation:

The history recorder long running task has detected an abend.

System action:

The history recorder task will terminate and then attempt to restart. CICSPlex SM processing continues.

User response:

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.

Destination:

Console, job log

Module:

EYU0NHCT

End of change
Start of change
EYUNL0173I
Task History Recorder has switched datasets from x to y
Explanation:

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.

System action:

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.

User response:

None.

Destination:

Console, job log

Module:

EYU0NHCT

End of change
Start of change
EYUNL0174E
Error Returned from XXXXXX command to dataset EYUHISTx,RESP=nnnnnnnn RESP2=nnnnnnnn
Explanation:

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.

System action:

History recording terminates.

User response:

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.

Destination:

Console, job log

Module:

EYU0NHCT

End of change
Start of change
EYUNL0175W
Concurrent iteration of Task History Recorder
Explanation:

During initialization, the long running task history recorder task has detected that there was already an instance of the history recorder task active.

System action:

This instance of the history recorder task is terminated.

User response:

None.

Destination:

Console, job log

Module:

EYU0NHCT

End of change
Start of change
EYUNL0176W
No History Datasets available
Explanation:

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.

System action:

The history recorder task is not started.

User response:

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.

Destination:

Console, job log

Module:

EYU0NHCT

End of change
Start of change
EYUNL0177W
HISTDBUFFS EYUPARM is too small, and has been increased to nnnnn
Explanation:

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.

System action:

CICS file creation for the history data sets continues using the value shown.

User response:

Re-adjust the HISTDBUFFS EYUPARM to an acceptable numeric value that is at least 1 greater than the HISTIBUFFS specification.

Destination:

Console, job log

Module:

EYU0NHFM

End of change
Start of change
EYUNL0178E
Task History Recorder unable to initialize EYUHISTx
Explanation:

The MAS history file manager detected problems meaning that it was unable to initialize the named history data set with its control information.

System action:

The named history data set is marked unuseable. The history recorder task is terminated.

User response:

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.

Destination:

Console, job log

Module:

EYU0NHFM

End of change
Start of change
EYUNL0179I
Task History Recorder dataset EYUHISTx has accrued nnnn records
Explanation:

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.

System action:

Task history recording continues.

User response:

None.

Destination:

Console, job log

Module:

EYU0NHCT

End of change
Start of change
EYUNL0181E
Invalid number of History data sets
Explanation:

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.

System action:

History recording is not activated.

User response:

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.

Destination:

Console, job log

Module:

EYU0NHFM

End of change
Start of change
EYUNL0182W
No History buckets available, nnn records dropped
Explanation:

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.

System action:

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.

User response:

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.

Destination:

Console, job log

Module:

EYU0NHCT

End of change
Start of change
EYUNL0183W
No History Exit Workarea available, nnn records dropped
Explanation:

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.

System action:

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.

User response:

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.

Destination:

Console, job log

Module:

EYU0NHCT

End of change
Start of change
EYUNL0184E
Invalid Attribute for History File EYUHISTx:
Explanation:

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.

System action:

The history recorder long running task is terminated.

User response:

Use the following EYUNL0185 message to determine which file attribute is invalid.

Destination:

Console, job log

Module:

EYU0NHFM

End of change
Start of change
EYUNL0185E
Keyword: xxxxxxxxx Expected value:nnn Returned value:nnn
Explanation:

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.

System action:

CICSPlex SM processing continues.

User response:

Use the information in the message to correct the history file attribute.

Destination:

Console, job log

Module:

EYU0NHFM

End of change
Start of change
EYUNL0186I
Task History Recorder has begun data collection
Explanation:

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.

System action:

CICSPlex SM processing continues. The task history recorder task will continue to accept and process details of completed CICS transactions.

User response:

None.

Destination:

Console, job log

Module:

EYU0NHCT

End of change
EYUNL0901I
addspace LRT NORMAL termination initiated
Explanation:

The long running task (LRT) for a MAS is being terminated because the CICS system it is associated with is being terminated, where:

addspace
Start of changeIdentifies the MAS as a local (LMAS).End of change
System action:

Termination of the MAS continues.

User response:

None.

Destination:

Start of changeConsole, job log, EYULOGEnd of change

Module:

EYU0NLRT, EYU1NLRT

EYUNL0902I
addspace LRT CMAS Requested termination initiated
Explanation:

The long running task (LRT) for a MAS is being terminated as a result of a request from the CMAS that controls it, where:

addspace
Start of changeIdentifies the MAS as a local (LMAS).End of change
System action:

Termination of the MAS continues. The CICS system continues to run normally, but it is no longer known to CICSPlex SM.

User response:

None.

Destination:

Start of changeConsole, job log, EYULOGEnd of change

Module:

EYU0NLRT, EYU1NLRT

Start of change
EYUNL0903E
addspace LRT Abnormal termination initiated
Explanation:

The long running task (LRT) for a MAS is being terminated as a result of an error or abend in the LRT, where:

addspace
Start of changeIdentifies the MAS as a local (LMAS).End of change
System action:

Termination of the MAS is attempted.

User response:

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.

Destination:

Console, job log, EYULOG,

Module:

EYU0NLRT

End of change
Start of change
EYUNL0904E
LRT Abnormal termination failed
Explanation:

An attempt to abnormally terminate the long running task (LRT) for a MAS has failed.

System action:

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.

User response:

See the User Response for message ***, which should precede this message. You need to restart the CICS region before the MAS agent can reconnect.

Destination:

Console, job log, EYULOG,

Module:

EYU0NLRT

End of change
Start of change
EYUNL0905E
An unrecoverable error has occurred. The MAS agent is being terminated.
Explanation:

An unrecoverable error has been detected during the execution of the MAS. The MAS agent is terminated.

System action:

After requesting an exception trace and a dump, the MAS agent is terminated.

User response:

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

Destination:

Start of changeConsole, job log, EYULOGEnd of change

Module:

EYU0NLSD

End of change
Start of change
EYUNL0910I
Alternate LRT (n ) is terminating normally
Explanation:

This message is issued when the alternate long running task terminates normally, where:

n
Is the number of the CONA task that is terminating.
System action:

MAS processing continues after the message is issued.

User response:

No action is required.

Destination:

Console, job log, EYULOG

Module:

EYU0NLRA

End of change
Start of change
EYUNL0911I
date time applid Number of active alternate LRTs: n.
Explanation:

No explanation available.

System action:

None.

User response:

None.

Module:

Module unknown.

:
  1. date
  2. time
  3. applid
  4. n
Destination:

Console and COLG

End of change
Start of change
EYUNL0912I
date time applid Number of active alternate LRTs: n.
Explanation:

No explanation available.

System action:

None.

User response:

None.

Module:

Module unknown.

:
  1. date
  2. time
  3. applid
  4. n
Destination:

Console and COLG

End of change
Start of change
EYUNL0913I
date time applid Number of active alternate LRTs:n.
Explanation:

No explanation available.

System action:

None.

User response:

None.

Module:

Module unknown.

:
  1. date
  2. time
  3. applid
  4. n
Destination:

Console and COLG

End of change
EYUNL0999I
addspace LRT termination complete
Explanation:

The long running task (LRT) for a MAS has been terminated, where:

addspace
Start of changeIdentifies the MAS as a local (LMAS).End of change
System action:

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).

User response:

None.

Destination:

Start of changeConsole, job log, EYULOGEnd of change

Module:

EYU0NLRT, EYU1NLRT

[[ Contents Previous Page | Next Page Index ]]