Reason:
An internal error has occurred in the CMS interface to the central version during an attempt to use the Virtual Machine Communication Facility (VMCF). Retry the application. If the problem occurs repeatedly, contact Technical Support. You can also refer to the VMCF subfunctional numbers and return code, described in IBM documentation, for help in determining the cause of the error.
Module:
IDMSVMCF
Severity:
0
Reason:
The named task is waiting on the named resource and is involved in a deadlock. The <cond> parameter specifies whether the control is returned to the waiting task (C:DEAD), or whether the task is aborted (C:NONE). The <resource-id> is the resource for which the task was waiting when the deadlock was detected. Resources include:
Most resource IDs are self-explanatory, however, the resource ID specified for the LTXNLOCK, GTXNLOCK, and PAGELOCK resource types are encoded as follows:
<wwwwxxyy zzzzzzzz>
where:
<wwww> = page group
<xx> = code identifying the value in <zzzzzzzz>
<yy> = db-key radix
One DC001000 message is issued for each task involved in a deadlock; followed by a DC001002 message for each task that is selected as a deadlock victim in order to resolve the deadlock.
Module:
RHDCDEAD
Severity:
3
Reason:
This is an optional display that is a result of coding the DEADLOCK_DETAILS=ON SYSIDMS parameter in the CV startup JCL. It displays additional debugging information to help identify the participants in a DEADLOCK condition. The message occurs following each DC001000 message identifying a participant in the DEADLOCK. There will be at least 2 DC001001 messages. The first is a "header" line followed by one or more detail lines depending upon the number of rununits the task is associated with.
The fields in the DC001001 message are as follows:
Module:
RHDCDEAD
Severity:
0
Reason:
This message is issued in conjunction with message DC001000 to identify the task which has been selected as the deadlock victim. The run unit associated with this task is rolled out and control is returned to the waiting task if C:DEAD; otherwise, the task is aborted.
Module:
RHDCDEAD
Severity:
3
Reason:
The task has exceeded the inactive interval time, the internal wait time, or the external wait time. These time limits are specified in the SYSGEN by the INACTIVE INTERVAL, INTERNAL WAIT, and EXTERNAL WAIT parameters of the SYSTEM statement. The inactive interval for an individual task can also be specified in the SYSGEN by the INACTIVE INTERVAL parameter of the TASK statement. If this condition occurs repeatedly, increase the appropriate time limit. For more information on these parameters, see the CA IDMS System Generation Guide.
Module:
RHDCWAIT
Severity:
5
Reason:
The named task is waiting on the named resource and is involved in a deadlock. The <cond> parameter specifies whether the control is returned to the waiting task (C:DEAD), or whether the task is aborted (C:NONE). The <task-id> identifies a task running on another CV in a SYSPLEX data sharing environment. The <system-id> is the name of the remote CV who will be sent a SYSPLEX message (DC001005) if this task is chosen as a deadlock victim. The <resource-id> is the resource for which the task was waiting when the deadlock was detected. Resources include:
Most resource IDs are self-explanatory; however, the resource ID specified for the LTXNLOCK, GTXNLOCK, and PAGELOCK resource types are encoded as follows:
<wwwwxxyy zzzzzzzz>
where:
<wwww> = page group
<xx> = code identifying the value in <zzzzzzzz>
<yy> = db-key radix
One DC001004 message is issued for each remote CV task involved in a deadlock; followed by either a DC001002 message (if a local CV task) or a DC001005 message (if a remote CV task) for each task that is selected as a deadlock victim in order to resolve the deadlock.
Module:
RHDCDEAD
Severity:
3
Reason:
This message is issued in conjunction with message DC001004 to identify the remote CV task which has been selected as the deadlock victim in a SYSPLEX data sharing environment. The <task-id> identifies a task running on another CV in a SYSPLEX data sharing environment. The <system-id> is the name of the remote CV who will be sent this SYSPLEX message when this task is chosen as a deadlock victim. The remote CV run unit associated with this task is rolled out and the remote CV task is aborted.
Module:
RHDCDEAD
Severity:
3
Reason:
This message is issued when a local CV task has been selected as a deadlock victim in a SYSPLEX data sharing environment. The <system-id> is the name of the remote CV who sent this message when this task was chosen as a deadlock victim. The run unit associated with this task is rolled out and the task is aborted.
Module:
RHDCDEAD
Severity:
3
Reason:
This message is issued in conjunction with message DC001008 and identifies a task that has stalled and the program name and resource that the task is waiting on at the time that the stall occurred. A DC001003 message will be issued indicating that the task has stalled and will be abended with abend code D002.
Module:
IDMSXTRA
Severity:
3
Reason:
This message is issued in conjunction with message DC001007 and identifies a task that has stalled and the transaction number, program name, subschema name, module line number, and db-key mode that the task is waiting on at the time that the stall occurred. A DC001003 message will be issued indicating that the task has stalled and will be abended with abend code D002.
Module:
IDMSXTRA
Severity:
3
Reason:
This message is issued in conjunction with message DC001010 and identifies a task that holds a db-key that a stalled task is waiting on. It identifies the task number, task name, program name, and db-key that the task is holding. A DC001003 message will be issued indicating that the waiting task has stalled and will be abended with abend code D002.
Module:
IDMSXTRA
Severity:
3
Reason:
This message is issued in conjunction with message DC001009 and identifies a task that holds a db-key that a stalled task is waiting on. It identifies the transaction number, program name, subschema name, and db-key mode that the task is holding. A DC001003 message will be issued indicating that the waiting task has stalled and will be abended with abend code D002.
Module:
IDMSXTRA
Severity:
3
Reason:
This information message indicates that RHDCDEAD is now active and ready for any needed task deadlock resolution.
Module:
RHDCDEAD
Severity:
0
Reason:
The CICS coordinator issued a commit request but the target transaction branch has been heuristically backed out. This message indicates that a DCMT VARY DISTRIBUTED TRANSACTION ... BACKOUT command was incorrectly used to force the changes made by the transaction identified in the following DC001109 message to be backed out.
This may have resulted in a mixed transaction outcome in which some changes were backed out while others were committed. Examine the coordinator's log to determine the final outcome.
Module:
IDMSTRUE
Severity:
0
Reason:
The CICS coordinator issued a backout request but the target transaction branch has been heuristically committed. This message indicates that a DCMT VARY DISTRIBUTED TRANSACTION ... COMMIT command was incorrectly used to force the changes made by the transaction identified in the following DC001109 message to be committed.
This may have resulted in a mixed transaction outcome in which some changes were backed out while others were committed. Examine the coordinator's log to determine the final outcome.
Module:
IDMSTRUE
Severity:
0
Reason:
This message indicates that the CA IDMS resource manager returned a Heuristic Mixed outcome from the commit phase of a 2-phase commit operation. This indicates that some updates may have been committed while others were backed out.
The accompanying DC001009 message identifies the transaction branch for which this condition is being reported.
This situation may have been caused by incorrect manual recovery procedures. You should examine the system log files and journal archive files to determine the reason for this condition and what (if any) corrective action should be taken.
Module:
IDMSTRUE
Severity:
0
Reason:
This message indicates that the CA IDMS resource manager returned a Heuristic Mixed outcome from the backout phase of a 2-phase commit operation. This indicates that some updates may have been committed while others were backed out.
The accompanying DC001009 message identifies the transaction branch for which this condition is being reported.
This situation may have been caused by incorrect manual recovery procedures. You should examine the system log files and journal archive files to determine the reason for this condition and what (if any) corrective action should be taken.
Module:
IDMSTRUE
Severity:
0
Reason:
This message identifies a distributed transaction branch. <dtrid> is the distributed transaction identifier (of which the last 16 characters is the CICS UOW) and <branchid> is the reporting node's branch identifier.
This message is preceded by another message indicating the reason why the identified transaction branch is being reported.
Module:
IDMSTRUE
Severity:
0
Reason:
A CICS task was executed to do a manual two-phase commit resynchronization, but the backend central version was not specified.
Module:
IDMSCSYN
Severity:
0
Reason:
A CICS two-phase commit resynchronization was executed but either the IDMSINTC interface is not started, or the CWADISP of the resynchronization program does not match the CWADISP for the IDMSINTC interface.
Module:
IDMSCSYN
Severity:
0
Reason:
A CICS GETMAIN error was encountered.
Module:
IDMSCSYN
Severity:
0
Reason:
A CICS task was executed to do a manual two-phase commit resynchronization, but the backend central version that was specified was not available through the IDMSINTC interface accessed by the resynchronization program.
The resynchronization program is created by linking module IDMSCSYN with an IDMSCINT module whose CWADISP identifies the IDMSINTC interface to be accessed. That IDMSINTC interface must be connected to the requested CV or it must contain an OPTIXIT which allows it to access the requested CV.
Module:
IDMSCSYN
Severity:
0
Reason:
Error doing a CV query. This is an internal error.
Module:
IDMSCSYN
Severity:
0
Reason:
Error doing a CV query. This is an internal error.
Module:
IDMSCSYN
Severity:
0
Reason:
A CICS RESYNC error was encountered. This is an internal error.
Module:
IDMSCSYN
Severity:
0
Reason:
A CICS two-phase commit resynchronization was executed but an error occurred in attempting to connect to the backend. Likely causes are:
Module:
IDMSCSYN
Severity:
0
Reason:
A CICS FREEMAIN error was encountered.
Module:
IDMSCSYN
Severity:
0
Reason:
A CICS task was executed to do a manual two-phase commit resynchronization, but the backend central version has transactions in progress that prevent the resynchronization.
Module:
IDMSCSYN
Severity:
0
Reason:
A CICS ASSIGN error was encountered. This is an internal error.
Module:
IDMSCSYN
Severity:
0
Reason:
A CICS ENQ error was encountered. This is an internal error.
Module:
IDMSCSYN
Severity:
0
Reason:
The task has exceeded the runaway interval time. This condition occurred within the DC system. Either a system internal error has occurred, or the value specified for the runaway interval time is too low. If this condition occurs repeatedly, increase the time specified in the RUNAWAY INTERVAL parameter of the SYSTEM statement of the SYSGEN.
Module:
RHDCWAIT
Severity:
3
Reason:
DC did not load the nucleus module necessary to process the requested function at startup because the corresponding component was not specified in the SYSGEN.
Module:
RHDCWAIT
Severity:
3
Reason:
The named task requested an RLE, causing the number of RLEs in use to exceed the RLE threshold. The task will be abended and snapped. Possible causes for this message are as follows:
Module:
RHDCWAIT
Severity:
3
Reason:
The named task requested an RCE, causing the number of RCEs in use to exceed the RCE threshold. The task will be abended and snapped. Possible causes for this message are as follows:
Module:
RHDCWAIT
Severity:
3
Reason:
The named task requested a DPE, causing the number of DPEs in use to exceed the DPE threshold. The task will be abended and snapped. Possible causes for this message are as follows:
Module:
RHDCWAIT
Severity:
3
Reason:
The High Performance Storage Protect Option (HPSPO) has been disabled due to an improper definition of the storage pools. The system continues to execute.
At least one storage pool contains both system and user storage. Redefine the storage pools to ensure that all forms of user oriented storage:
user, user-kept, shared, and shared-kept
are isolated into their own storage pools instead of mixing them with system oriented storage types:
terminal, database
Do not use the SYSGEN storage pool sub-clause:
contains types (ALL)
Module:
RHDCWAIT
Severity:
0
Reason:
A system internal error has occurred, possibly caused by storage having been overwritten.
Module:
RHDCWAIT
Severity:
8
Reason:
A task has requested that a system snap be taken using the operating system SVC dump service. This dump will be written to the system dump datasets and not to a dataset allocated to the job executing the CA IDMS central version.
Module:
RHDCSNAP
Severity:
0
Reason:
An SVCDUMP has been produced; appears after DC009001.
Module:
RHDCSNAP
Severity:
0
Reason:
An SVCDUMP request has failed, where <nn> is the return code.
Module:
RHDCSNAP
Severity:
0
Reason:
A system snap has occurred on a DC/UCF system with multitasking enabled. The snap is written to the SYSOUT log file.
This message is provided so that a user can trap the message number in user exit 7. Upon receiving this message, user exit 7 can submit a JCL stream that copies the SYSOUT log file to another file. This method is similar to that used in the WTOEXIT for submitting the ARCHIVE JOURNAL.
Module:
RHDCSNMT
Severity:
0
Reason:
An invalid RLE or RCE pointer has been passed as an RHDCRMGR parameter. This is a system internal error, possibly caused by storage having been overwritten.
Module:
RHDCRMGR
Severity:
4
Reason:
An invalid request type code has been passed to RHDCRMGR. This is a system internal error, possibly caused by storage having been overwritten.
Module:
RHDCRMGR
Severity:
4
Reason:
The specified RCE is not in the specified chain. This is a system internal error, possibly caused by storage having been overwritten.
Module:
RHDCRMGR
Severity:
4
Reason:
A logic error has occurred in RHDCRMGR; an RLE is not in the expected chain. This is a system internal error, possibly caused by storage having been overwritten.
Module:
RHDCRMGR
Severity:
4
Reason:
A shortage condition on a resource (RLE, RCE, or DPE) has occurred. The corresponding resource pool has been dynamically extended, up to the number specified in the message. The DBA should use this message to update the corresponding SYSGEN definition to avoid the overhead of using this facility.
Module:
RHDCRMGR
Severity:
0
|
Copyright © 2014 CA.
All rights reserved.
|
|