Reason:
Either an Assembler program has attempted to dequeue a resource that the named task has not enqueued, and the program has not specified COND=IDNF on the #DEQ macro; or a system internal error has occurred, possibly caused by storage having been overwritten.
Module:
RHDCEDQ
Severity:
3
Reason:
The parameter list passed to a #ENQ/#DEQ macro contains an invalid field. The probable cause is that the value of the resource-id length parameter is zero. If this condition occurs when the option COND=INVP and INVPXIT is specified on the #ENQ/#DEQ macro, this message is not issued and control is returned to the user program.
Module:
RHDCEDQ
Severity:
3
Reason:
A #XESLOCK OBTAIN/RELEASE function call associated with a global enqueue/dequeue resource has failed. The return code in R15 and the reason code are displayed. Check the IBM documentation for more information on the error codes. This message is followed by message DC070004 that displays the resource-id involved.
Module:
RHDCEDQ
Severity:
0
Reason:
This message follows the message DC070003 that is displayed when a #XESLOCK call associated with a global enqueue/dequeue resource has failed. It displays the name of the resource-id involved.
Module:
RHDCEDQ
Severity:
0
Reason:
This is an internal trace message for enqueue/dequeue activities. The information displayed contains the task-id, the current program name, the type of request, the ECE flag, and the first 32 characters of the resource-id.
Module:
RHDCEDQ
Severity:
0
Reason:
The indicated physical terminal is marked as out of service. Either a DCMT VARY PTERM OFFLINE command has been issued, or a hardware error has occurred. A terminal that is out of service can be varied into service by means of a DCMT VARY PTERM ONLINE command.
Module:
RHDCD00B,RHDCD60B
Severity:
0
Reason:
The indicated physical terminal is marked as out of service. Either a DCMT VARY PTERM OFFLINE command has been issued, or a hardware error has occurred. A terminal that is out of service can be varied into service by means of a DCMT VARY PTERM ONLINE command.
Module:
RHDCD01B,RHDCD61B
Severity:
0
Reason:
The DC execution JCL does not contain a DD statement for a device that matches the named physical terminal, as defined at DC/UCF system generation time.
Module:
RHDCO01B
Severity:
0
Reason:
No corresponding physical terminal exists for the indicated device, as defined by a DD statement in the DC execution JCL. If the device should be supported by the DC system, add the appropriate PTERM statement to DC/UCF system generation statements. If the device should not be supported, remove the DD statement from the JCL.
Module:
RHDCO01B
Severity:
0
Reason:
The DC execution JCL does not contain an ASSGN statement for a device that matches the named physical terminal, as defined at DC/UCF system generation time.
Module:
RHDCO61B
Severity:
0
Reason:
A system internal error has occurred in the DOS/OS BTAMBSC3 line driver. Contact Technical Support.
Module:
RHDCDXDB
Severity:
4
Reason:
A system internal error has occurred in the DOS/OS BTAMBSC3 line driver. Contact Technical Support.
Module:
RHDCDXDB
Severity:
4
Reason:
A system internal error has occurred in the DOS/OS BTAMBSC3 line driver. Contact Technical Support.
Module:
RHDCDXDB
Severity:
4
Reason:
The specified task has requested a #SWITCH WRITREAD or WRITE to a destination that either was not defined during system generation or was not defined as a switch destination.
Module:
RHDCSWIT
Severity:
3
Reason:
The specified task has requested a #SWITCH WRITREAD or WRITE to a destination that is disabled or out of service. Ensure that the destination and the associated logical and physical terminals are in service. Then try the request again.
A destination that was defined as disabled during system generation can be varied into service with the DCMT VARY DESTINATION command. Logical terminals can be varied into service with the DCMT VARY LTERM command. Physical terminals can be varied into service with the DCMT VARY PTERM command.
Module:
RHDCSWIT
Severity:
3
Reason:
The switch driver, RHDCSWIT, has received an unsolicited input message. The user-written module, SWITTASK, specified a task to be attached by RHDCSWIT to handle the unsolicited input. The attach failed and the attach macro returned the specified failure code. For more information on the description of failure return code, see the #ATTACH documentation in the CA IDMS DML Reference Guide for Assembler.
Module:
RHDCSWIT
Severity:
0
Reason:
The specified task has requested a #SWITCH GET, but no switch message is queued to be received.
A #SWITCH GET request can be executed only after the ECB indicated by a previous #SWITCH WRITREAD request has been posted to indicate that the response message was received.
Module:
RHDCSWIT
Severity:
3
Reason:
The maximum size of the input buffer for the #SWITCH GET request is too small. The task should increase the size of the buffer identified by the INAREA and MAXIN parameters of the #SWITCH GET request. Alternatively, OPTNS=LOCATE can be specified on the #SWITCH GET request to prevent this problem from occurring.
Module:
RHDCSWIT
Severity:
3
Reason:
This message indicates that the parameter list for a switch request has not been set up properly. This error should not occur if the #SWITCH macro is used to code switch requests.
Module:
RHDCSWIT
Severity:
3
Reason:
The specified task has requested a #SWITCH WRITE or WRITREAD, but did not specify a destination. Normally, the destination defaults to the destination of the previous switch request. However, in this case, no previous request existed for this task.
Module:
RHDCSWIT
Severity:
3
Reason:
The specified task has issued more than one concurrent #SWITCH WRITREAD request. A single transaction cannot issue multiple #SWITCH WRITREAD requests without an intervening #SWITCH GET or #SWITCH CANCEL request.
Module:
RHDCSWIT
Severity:
3
Reason:
This message is a general error message line for all batch simulator error messages. Refer to the indicated abend code for more information.
Module:
RHDCD63Q
Severity:
2
Reason:
This message is the general console communications identifier. All output to the console has this identifier.
Module:
RHDCD04W
Severity:
0
Reason:
A system internal error has occurred. Contact Technical Support.
Module:
RHDCRUAL
Severity:
0
Reason:
No RCEs or RLEs were available to satisfy the request. A possible cause is that a program either is looping while acquiring resources or is failing to free resources. Check for an error in program logic. Alternatively, the system may be using more resources than expected. In this case, increase the RCE or RLE count specified in the system generation SYSTEM statement.
Module:
RHDCRUAL
Severity:
0
Reason:
A GETRU request has been issued to obtain a new Run-unit Element, but the request failed because no storage was available. If this condition occurs repeatedly, increase the size of the storage pool.
Module:
RHDCRUAL
Severity:
0
Reason:
An attempt has been made to free a system internal run unit, but the run unit was not associated with the requesting task. This is a system internal error. Contact Technical Support.
Module:
RHDCRUAL
Severity:
0
Reason:
A GETRU request has been issued to obtain a new Run-unit Element, but the request failed because TMGR was unable to connect the rununit to the current task.
Action:
This is an internal error. Contact Technical Support.
Module:
RHDCRUAL
Severity:
0
Reason:
A database error has occurred during the BIND of the IDMSNWKS subschema. For more information on this error, examine the contents of the 3957 abend dump and the message text written to the operator's console. For status information, refer to the accompanying DC076<nnn> messages.
Module:
RHDCLGSD
Severity:
0
Reason:
A database error has occurred during the READY of the DDLDCLOG area. For more information on this error, examine the contents of the 3957 abend dump and the message text written to the operator's console. For status information, refer to the accompanying DC076<nnn> messages.
Module:
RHDCLGSD
Severity:
0
Reason:
A database error has occurred during processing of the first verb issued against the DDLDCLOG area. For more information on this error, examine the contents of the 3957 abend dump and the message text written to the operator's console. For status information, refer to the accompanying DC076<nnn> messages.
Module:
RHDCLGSD
Severity:
0
Reason:
A database error has occurred at system shutdown during the FINISH of database logging of a system run unit. For more information on this error, examine the contents of the 3957 abend dump and the message text written to the operator's console. For status information, refer to the accompanying DC076<nnn> messages.
Module:
RHDCLGSD
Severity:
0
BIND of IDMSNWK5 failed - status &01
Reason:
A database error has occurred during the BIND of the IDMSNWK5 subschema by the tracing rununit. The database request resulted in the error status shown in the message. Examine the contents of the log for additional messages that may indicate the reason for the failure. This error prevents trace information from being saved to the DDLDCTRC area.
Module:
RHDCTRSD
Severity:
0
Reason:
A database error has occurred during the READY of the DDLDCTRC area by the tracing rununit. The database request resulted in the error status shown in the message. Examine the contents of the log for additional messages that may indicate the reason for the failure. This error prevents trace information from being saved to the DDLDCTRC area.
Module:
RHDCTRSD
Severity:
0
Reason:
A database error has occurred during processing of the first non-ready verb issued by the tracing rununit. The database request resulted in the error status shown in the message. Examine the contents of the log for additional messages that may indicate the reason for the failure. This error prevents trace information from being saved to the DDLDCTRC area.
Module:
RHDCTRSD
Severity:
0
FINISH of tracing rununit failed - status &01
Reason:
A database error has occurred when attempting to FINISH the tracing run unit. The database request resulted in the error status shown in the message. This failure may result in missing trace information.
Module:
RHDCTRSD
Severity:
0
Trace saving has started. Writing to <area> area.
Reason:
The saving of trace information has begun. Trace data is being written to the area identified in the message.This message is informational only. No action is needed.
Module:
RHDCTRSD
Severity:
0
Trace saving has ended.
Reason:
The saving of trace information has ended. This message is informational only. No action is needed.
Module:
RHDCTRSD
Severity:
0
Reason:
A database error has occurred during an attempt to bind a LOADHDR-156 record, to OBTAIN PRIOR in the LOOAK-LOADHDR set, or to erase a LOADHDR-156 record. For further information about this error, examine the contents of the 3957 abend dump and the message text written to the operator's console. For status information, refer to the accompanying DC076<nnn> messages.
Module:
RHDCRUAL
Severity:
0
Reason:
A database error has occurred during an attempt to FIND/OBTAIN a LOADHDR-156 record. For further information about this error, examine the contents of the 3957 abend dump and the message text written to the operator's console. For status information, refer to the accompanying DC076<nnn> messages.
Module:
RHDCRUAL
Severity:
0
Reason:
A database error has occurred during an attempt to erase a LOADHDR-156 record. For further information about this error, examine the contents of the 3957 abend dump and the message text written to the operator's console. For status information, refer to the accompanying DC076<nnn> messages.
Module:
RHDCRUAL
Severity:
0
Reason:
An attempt to allocate a system run unit has failed on the BIND RUN-UNIT. For further information about this error, refer to the indicated status code.
Module:
RHDCRUAL
Severity:
0
Reason:
An attempt to allocate a system run unit has failed on the READY of the named area. For further information about the error, refer to the indicated status code.
Module:
RHDCRUAL
Severity:
0
Reason:
An attempt to allocate a system run unit has failed. This message is issued following either message DC075020 or message DC075021. For further information about the error, refer to the accompanying message.
Module:
RHDCRUAL
Severity:
0
Reason:
This message provides a time trace for a physical terminal. The three-character function codes and their associated meanings are listed below:
Code Meaning REQ Request SRD Start READ ERD End READ SWR Start WRITE EWR End WRITE SLG Start LOGON ELG End LOGON ATN Attention received SSL Start SIMLOGON ESL End SIMLOGON SCD Start CLSDST ECD End CLSDST
Module:
RHDCD05V,RHDCD65V
Severity:
0
Reason:
The indicated physical terminal is marked as out of service. Either a DCMT VARY PTERM OFFLINE command has been issued, or a hardware error has occurred. A terminal that is out of service can be varied into service by means of a DCMT VARY PTERM ONLINE command.
Module:
RHDCD05V,RHDCD65V
Severity:
0
Reason:
The VTAM line driver has requested the indicated terminal for the indicated line.
Module:
RHDCD05V,RHDCD65V
Severity:
0
Reason:
During open processing for the indicated line, an error has occurred on a VTAM macro. This message provides the VTAM function name, followed by the values returned by VTAM in R0 and R15. Typically, this message indicates an error in the VTAM generation.
Module:
RHDCO05V,RHDCO65V
Severity:
0
Reason:
A DCMT VARY LINE ONLINE command for a previously open line has failed because not enough storage could be acquired for the control blocks. This condition should occur only if the system generation parameters for the line have changed since the line was shut down. Cycle the system to obtain sufficient storage to reopen the line.
Module:
RHDCO05V,RHDCO65V
Severity:
0
Reason:
The indicated line was disabled at system generation time and therefore has not been opened. This is an informational message only.
Module:
RHDCO05V,RHDCO65V
Severity:
0
Reason:
A database error has occurred in the named program. Refer to the indicated status code for more information.
This message and messages DC076002 through DC076007 describe errors encountered by a system run unit during processing on behalf of a task. These messages are followed by a snap dump of the task, the CSA, and the trace table. Note that messages DC076003 through DC076007 are issued only when the record, set, or area names have values other than blanks.
Module:
RHDCRUAL
Severity:
0
Reason:
The indicated database key is the database key of the last record accessed successfully.
Module:
RHDCRUAL
Severity:
0
Reason:
The named record is the last record type accessed successfully.
Module:
RHDCRUAL
Severity:
0
Reason:
The named area is the last area accessed successfully.
Module:
RHDCRUAL
Severity:
0
Reason:
The named set is the set last involved in the operation that produced the error condition.
Module:
RHDCRUAL
Severity:
0
Reason:
The named record is the record last involved in the operation that produced the error condition.
Module:
RHDCRUAL
Severity:
0
Reason:
The named area is the area last involved in the operation that produced the error condition.
Module:
RHDCRUAL
Severity:
0
Reason:
Messages DC076010 through DC076021 describe database errors encountered by a predefined run unit processing on behalf of a task. Messages DC076012, DC076013, and DC076017 through DC076021 are issued only if the corresponding information has a value other than blanks.
Module:
RHDCRUAL
Severity:
0
Reason:
The indicated subschema was in use by the predefined rununit at the time the database error was encountered. This message accompanies DC076010.
Module:
RHDCRUAL
Severity:
0
Reason:
The predefined run unit was bound to the indicated node. This message, which accompanies DC076010, is issued only if the node name is not blank (blanks indicate the local node).
Module:
RHDCRUAL
Severity:
0
Reason:
The predefined run unit was bound using the indicated database name. This message, which accompanies DC076010, is not issued if a blank dbname is specified.
Module:
RHDCRUAL
Severity:
0
Reason:
This message indicates the status returned to the predefined run unit. Please refer to the indicated status for additional information. This message accompanies DC076010.
Module:
RHDCRUAL
Severity:
0
Reason:
The indicated database key is that of the last successfully accessed record. This message accompanies DC076010.
Module:
RHDCRUAL
Severity:
0
Reason:
The indicated key is the database key most recently used for DIRECT access. This message accompanies DC076010.
Module:
RHDCRUAL
Severity:
0
Reason:
The named record was the last record type successfully accessed. This message, which accompanies DC076010, is issued only if the record name is not blank.
Module:
RHDCRUAL
Severity:
0
Reason:
The named area was the last one successfully accessed. This message, which accompanies DC076010, is issued only if the area name is not blank.
Module:
RHDCRUAL
Severity:
0
Reason:
The named set was the last one involved in the operation that caused the error. This message, which accompanies DC076010, is issued only if the set name is not blank.
Module:
RHDCRUAL
Severity:
0
Reason:
The named record was the last record type accessed by the operation that caused the error. This message, which accompanies DC076010, is issued only if the ERROR RECORD value is not blank.
Module:
RHDCRUAL
Severity:
0
Reason:
The named area was the last area accessed by the operation that caused the error. This message, which accompanies DC076010, is issued only if the ERROR AREA value is not blank.
Module:
RHDCRUAL
Severity:
0
Reason:
The ASYNC terminal driver module has been unable to halt an I/O operation on one of its terminals. An occasional occurrence of this message is not significant; however, if this condition coincides with other problems, contact Technical Support.
Module:
RHDCD06E
Severity:
0
Reason:
The indicated physical terminal is marked as out of service. Either a DCMT VARY PTERM OFFLINE command has been issued, or a hardware error has occurred. A terminal that is out of service can be varied into service by means of a DCMT VARY PTERM ONLINE command.
Module:
RHDCD06E, RHDCD66E
Severity:
0
Reason:
A DCMT VARY LINE ONLINE command for a previously open line has failed because not enough storage could be acquired for the control blocks. This condition should occur only if the system generation parameters for the line have changed since the line was shut down. Cycle the system to obtain sufficient storage to reopen the line.
Module:
RHDCO06E, RHDCO66E
Severity:
0
Reason:
The indicated processing module for a particular stop/start device could not be found in CDMSLIB. Contact Technical Support.
Module:
RHDCO06E, RHDCO66E
Severity:
0
Reason:
The operating system control block for the unit associated with the indicated physical terminal could not be located. The probable cause of this error is that the DD statement defining the device was omitted from the DC/UCF execution JCL.
Module:
RHDCO06E
Severity:
0
Reason:
An operating system GETMAIN failed. The partition or region contains insufficient storage to satisfy DC/UCF requirements.
Module:
RHDCD06E
Severity:
0
Reason:
An operating system function failed during the open process for a start/stop line or terminal. Contact Technical Support.
Module:
RHDCD06E
Severity:
0
Reason:
An operating system function failed during the open process for a start/stop line or terminal. Contact Technical Support.
Module:
RHDCD06E
Severity:
0
Reason:
An operating system function failed during the open process for a start/stop line or terminal. Contact Technical Support.
Module:
RHDCD06E
Severity:
0
Reason:
A system internal error has occurred. RHDCDBCO is limited internally to ten run units; typical current usage is less than or equal to three run units. Contact Technical Support.
Module:
RHDCDBCO
Severity:
1
Reason:
A system internal error has occurred. The function code requested was either zero or greater than six. Contact Technical Support.
Module:
RHDCDBCO
Severity:
0
Reason:
A database error has occurred during an attempt to issue a task-level COMMIT, ROLLBACK, or FINISH. This is a system internal error.
Module:
RHDCDBCO
Severity:
3
Reason:
A #GETSTG TYPE=SHORT request has failed. Insufficient storage was available for an I/O parameter area for calls to IDMSDBIO. The amount needed is approximately 1200 bytes. Ensure that an adequate storage pool size is specified at DC/UCF system generation or startup time.
Module:
RHDCDBCO
Severity:
1
Reason:
IDMSDBIO has returned a nonzero status code, which is displayed in the log. Refer to the status code for more information.
Module:
RHDCDBCO
Severity:
3
Reason:
The checkpoint record written for a task-level COMMIT, ROLLBACK, or FINISH is larger than the journal record size. Control is returned to the program that issued the request. For COBOL or PL/I programs, the request will result in a status code of 5097; for Assembler programs, register 15 will contain X'12' after the request. Increase the journal block size in the global DMCL and recompile the DMCL.
Module:
RHDCDBCO
Severity:
3
Reason:
The checkpoint record to be written on a task-level COMMIT or FINISH requires a flush of the current journal buffer, but the attempt to flush the buffer has resulted in a nonzero status code. Control is returned to the program that issued the request. For COBOL or PL/I programs, the request will result in a status code of 5097; for Assembler programs, register 15 will contain X'12' after the request. See the system log for preceding messages that further describe the problem.
Module:
RHDCDBCO
Severity:
3
Reason:
The terminal driver task for the LTERM/PTERM will be terminated. A logical terminal connected to a SYSOUTT type physical terminal must be defined to DC as a printer. Specify PRINTER on the system generation LTERM statement for this logical terminal.
Module:
RHDCD07Q
Severity:
0
Reason:
Zero or a negative number has been specified as the record length in an attempt to place a user journal record in the IDMS journal file. No record will be written. Control is returned to the program that issued the request. For COBOL or PL/I programs, a WRITE JOURNAL request will result in a status code of 5032; for Assembler programs, register 15 will contain X'04' after a #PUTJRNL request.
Module:
RHDCDBCO
Severity:
1
Reason:
In an attempt to place a user journal record in the journal file, a GETSTG request for an IOP (in the DBIO parameter list area) failed. The record will not be written. Control is returned to the program that issued the request. For COBOL or PL/I programs, a WRITE JOURNAL request will result in a status code of 5002; for Assembler programs, register 15 will contain X'08' after a #PUTJRNL request.
Module:
RHDCDBCO
Severity:
1
Reason:
An attempt to place a user journal record in the journal file required a flush of the current journal buffer, but the attempt to flush the buffer has resulted in a nonzero status code. Control is returned to the program that issued the request. For COBOL or PL/I programs, a WRITE JOURNAL request will result in a status code of 5097; for Assembler programs, register 15 will contain X'12' after a #PUTJRNL request. See the system log for preceding messages that further describe the problem.
Module:
RHDCDBCO
Severity:
4
Reason:
A local 3280-type printer has been varied offline. Either three consecutive I/O errors have occurred on the printer, or a user has varied the printer offline by means of a DCMT VARY PTERM command. No further attempt to use the printer will be made until the printer is varied online by means of a DCMT VARY PTERM command.
Module:
RHDCD08B, RHDCD68B
Severity:
0
Reason:
A local 3280-type printer has returned a status of intervention required. The probable cause is either that the printer has been powered down or that it has run out of paper. An attempt will be made to retry the printer every two minutes until an operator either attends to the printer or varies it offline by means of a DCMT VARY PTERM command.
Module:
RHDCD08B, RHDCD68B
Severity:
0
Reason:
Load module RHDCM01B could not be located in CDMSLIB. Contact Technical Support.
Module:
RHDCO68B
Severity:
0
Reason:
RHDCM01B must reside in the Link Pack Area (LPA).
Module:
RHDCO68B
Severity:
0
Reason:
An error has occurred on an operating system function. Contact Technical Support.
Module:
RHDCO68B
Severity:
0
Reason:
The BTAM OPEN for the indicated physical terminal has failed. Contact Technical Support.
Module:
RHDCO68B
Severity:
0
|
Copyright © 2014 CA.
All rights reserved.
|
|