Reason:
This message is displayed periodically as the log fills. Generally, when the reported percent exceeds 70 percent, the PRINT LOG utility statement should be run.
Module:
RHDCMISC
Severity:
0
Reason:
A system internal error has occurred, possibly caused by storage having been overwritten.
Module:
RHDCMISC
Severity:
0
Reason:
A system internal error has occurred, possibly caused by storage having been overwritten.
Module:
RHDCMISC
Severity:
0
Reason:
Run the PRINT LOG utility statement to archive the DDLDCLOG area. System activity is suspended until the PRINT LOG utility statement terminates.
Module:
RHDCMISC
Severity:
0
Reason:
Probable causes of this error are as follows:
Module:
RHDCMISC
Severity:
0
Reason:
A system internal error has occurred, possibly caused by storage having been overwritten.
Module:
RHDCMISC
Severity:
0
Reason:
A system internal error has occurred during an attempt to release a buffer for the system log. The error is possibly caused by storage having been overwritten or by a bad I/O status from DBIO.
Module:
RHDCMISC
Severity:
0
Reason:
The named system-requested single-threaded resource type is currently unavailable. Waiting for the resource would have caused a deadlock. Wait a few minutes; then reinvoke the task.
Module:
RHDCMISC
Severity:
3
Reason:
A system internal error has occurred, possibly caused by storage having been overwritten.
Module:
RHDCMISC
Severity:
3
Reason:
The segment containing the DCLOG physical file has been defined with more than 255 records per page. Redefine the segment specifying MAXIMUM RECORDS PER PAGE 255.
Module:
RHDCMISC
Severity:
0
Reason:
The system requested the release of the named single-threaded resource type, but the resource type is not owned by the requesting task. This is a system internal error, possibly caused by storage having been overwritten.
Module:
RHDCMISC
Severity:
4
Reason:
A system internal error has occurred, possibly caused by storage having been overwritten.
Module:
RHDCMISC
Severity:
8
Reason:
The parameter list for one of the extended #TBLSRCH functions was constructed incorrectly. Run PRINT LOG to obtain the task snap. Ensure that a trace is available and contact Technical Support.
Module:
RHDCMISC
Severity:
3
Reason:
A bad parameter was passed to the generic key search. This is a system internal error. Print the dump and contact Technical Support.
Module:
RHDCMISC
Severity:
3
Reason:
The index for the TDT or PDT or OPER's WATCH LTERM list ran out of space. In attempting to expand the index, TBLSRCH could not get enough storage to make a new copy of the index. It also is possible that TBLSRCH could not get enough storage to build the first index for one of the above tables.
Check to see whether one or more programs are using an excessive amount of storage, and correct the program. It may be necessary to reserve more room for the storage pool at system generation time.
Module:
RHDCMISC
Entry point = TBLSREP1
Severity:
0
Reason:
This is an internal error. Contact Technical Support.
Module:
RHDCTABL
Severity:
4
Reason:
This message is issued in a z/OS multitasking environment only. The indicated exit has been defined to be called in system mode using CA IDMS/DC calling conventions, but the required MPMODE was not specified on the #START macro. Reassemble the exit specifying an appropriate MPMODE. Be sure to use the current CA IDMS macro library for the assembly.
Module:
RHDCMISC
Severity:
0
Reason:
This message is issued in the z/OS multitasking environment only. The indicated exit has been defined to be called in system mode using IBM linkage conventions, but does not specify an MPMODE. In the z/OS multitasking system, user exits called in system mode with IBM calling conventions should contain a NOOP at the entry point. Reassemble the exit.
Module:
RHDCMISC
Severity:
0
Reason:
This message accompanies one or more occurrences of message DC050021. Check those messages to determine the specific exit or exits which caused the error. See the description of message DC050021 for the necessary corrective action.
Module:
RHDCMISC
Severity:
8
Reason:
This message accompanies one or more occurrences of message DC050020. Check those messages to determine the specific exit or exits which caused the error. See the description of message DC050020 for the necessary corrective action.
Module:
RHDCMISC
Severity:
8
Reason:
This message is displayed periodically as the trace area fills. Generally, when the reported percent exceeds 70 percent, the ARCHIVE TRACE utility statement should be run to offload trace information and reclaim space in the area.
Module:
RHDCMISC
Severity:
0
Reason:
An error has occurred trying to read the DDLDCTRC area. This error disables the saving of trace information. Examine the log for additional messages that identify the cause of the failure. Once corrective action has been taken, you can resume saving of trace information by issuing a DCMT VARY TRACE SAVE ON command.
Module:
RHDCMISC
Severity:
0
Reason:
An error has occurred trying to write to the DDLDCTRC area and means that some trace information has been lost. If several consecutive writes fail, the saving of trace information is disabled. Examine the log for additional messages that identify the cause of the failure. Once corrective action has been taken, you can resume saving of trace information by issuing a DCMT VARY TRACE SAVE ON command.
Module:
RHDCMISC
Severity:
0
The DDLDCTRC area has filled. Run the ARCHIVE TRACE utility to offload the trace information and reclaim space in the area. No further trace information are saved until this utility executes successfully.
Module:
RHDCMISC
Severity:
0
Reason:
Probable causes of this error are:
Module:
RHDCMISC
Severity:
0
A system internal error has occurred, possibly caused by storage having been overwritten.
RHDCMISC
0
Reason:
The segment containing the DCTRC physical file has been defined with more than 255 records per page. Redefine the segment specifying MAXIMUM RECORDS PER PAGE 255 or define the DCTRC file and its associated area in a segment that has a maximum of 255 record per page.
Module:
RHDCMISC
Severity:
0
Reason:
A request for storage by RHDCSTAT would have caused a deadlock. This condition is usually temporary, allowing successful rerun of the abended tasks.
Module:
RHDCSTAT
Severity:
3
Reason:
An attempt to access transaction statistics has failed either because the block was never bound or because the block has already been freed.
Module:
RHDCSTAT
Severity:
3
Reason:
A system internal error has occurred, possibly caused by storage having been overwritten.
Module:
RHDCSTAT
Severity:
3
Reason:
A BIND, ACCEPT, or END TRANSACTION STATISTICS request cannot be satisfied for either of the following reasons:
Module:
RHDCSTAT
Severity:
3
Reason:
A database error occurred during access to the data dictionary queue area when RHDCSMSG issued a PUT QUEUE for the message. Refer to the accompanying DC076<nnn> message for further information.
Module:
RHDCSMSG
Severity:
3
Reason:
A system internal error has occurred, possibly caused by storage having been overwritten.
Module:
RHDCSMSG
Severity:
3
Reason:
The named destination identifier, user identifier, or logical terminal identifier has not been defined to the DC/UCF system at system generation time.
Module:
RHDCSMSG
Severity:
5
Reason:
A database error has occurred in the DDLDML area. Refer to the indicated user runtime status code for more information.
Module:
RHDCSMSG
Severity:
3
Reason:
Check the system log for further messages and refer to the indicated task abend code for more information.
Module:
RHDCMSTR
Severity:
0
Reason:
This message is the second line for message DC055000 if a system message accompanies the abend code. <Nnnnnn> is a system message number; add the prefix DC and refer to the appropriate message for further information.
Module:
RHDCMSTR
Severity:
0
Reason:
The task currently being initiated is not defined to the system. Define the task either at system generation time or by means of a DCMT VARY DYNAMIC TASK command.
Module:
RHDCMSTR
Severity:
0
Reason:
The user is not authorized to use the specified task code. The user's security class list does not contain the security class for the task. The security class list for a user is established either by the system generation USER statement or by the DDDL compiler. The security class for a task is established either by the system generation TASK statement or by a DCMT VARY TASK SECURITY command.
Module:
RHDCMSTR
Severity:
0
Reason:
The named task has been defined to the system as INTERNAL and therefore can be invoked only by specifying the task code on an ATTACH or DC RETURN. To permit the task to be invoked from a terminal, change the specification of INTERNAL to EXTERNAL in the task definition either at system generation time or by means of a DCMT VARY DYNAMIC TASK command.
Module:
RHDCMSTR
Severity:
0
Reason:
Either the system or an explicit user request has disabled the named task. Contact the system administrator.
Module:
RHDCMSTR
Severity:
0
Reason:
Either the system or an explicit user request has disabled the named program. Contact the system administrator.
Module:
RHDCMSTR
Severity:
0
Reason:
This message is the system prompt for a task code.
Module:
RHDCMSTR
Severity:
0
Reason:
The SHUTDOWN command has been entered and the system has begun its termination processing.
Module:
RHDCMSTR
Severity:
0
Reason:
A command list is being executed with prompting. This message asks whether the user wishes to continue with the next command in the command list.
Module:
RHDCMSTR
Severity:
0
Reason:
This execution of the named task would cause the maximum concurrent limit to be exceeded. Either wait and try again later, or vary the maximum concurrent limit to a higher value by means of a DCMT VARY TASK command.
Module:
RHDCMSTR
Severity:
0
Reason:
The system failed to attach a timer initiated task which was requested by a SET TIMER START TASK <task code> statement. The meaning of the <ATTACH return code> displayed in decimal is given below:
The system will also cancel the ICE (Interval Control Element) associated with the failed attach.
Module:
RHDCMSTR
Severity:
0
Reason:
During initialization, the PL/I runtime system found that the ISA size specified in the program definition was insufficient to start the program. A default size was calculated and used. Increase the ISA size either by using the system generation PROGRAM statement or by means of a DCMT VARY DYNAMIC PROGRAM command.
Module:
RHDCPPLO
Severity:
0
Reason:
A system internal error has occurred. Contact Technical Support. The task abend code is ERRX.
Module:
RHDCPLIB
Severity:
3
Reason:
A system internal error has occurred. Contact Technical Support. The abend code is the PL/I abend code 4000.
Module:
RHDCPLIB
Severity:
3
Reason:
A system internal error has occurred. Contact Technical Support. The abend code is the PL/I abend code 4028.
Module:
RHDCPLIB
Severity:
3
Reason:
An I/O error has occurred during an attempt to loathe PLIDUMPA module. Rerun the job.
NOT FOUND
A #LOAD has been issued for the PLIDUMPA module, but the module cannot be found in the system load library. Link edit the PLIDUMPA module and rerun the job.
LOAD DEADLOCK
A #LOAD deadlock has occurred during an attempt to load the PLIDUMPA module. If this error occurs frequently, increase the size of the program pool.
Module:
IBMBKDMA
Severity:
3
Reason:
A COBOL II, PL/I, or LE370 program has attempted to put out a line of message text to DDNAME <ddname>. The CA IDMS/DC/UCF system has intercepted the message and written it to the DC log file.
Module:
RHDCOSCR
Severity:
0CA IDMS/DC
|
Copyright © 2014 CA.
All rights reserved.
|
|