Previous Topic: CA IDMS/DC Messages DC050001 - DC057005Next Topic: CA IDMS/DC Messages DC070001 - DC078113


CA IDMS/DC Messages DC060001 - DC067001

DC061001

TASK: <task-code> PROG: <program-name>; CURRENCY SAVE/RESTORE INTERNAL ERROR CODE IS <code-number>

Reason:

A system internal error has occurred. Contact Technical Support. Code numbers and their associated meanings are shown below:

Code   Meaning

1      SAVING AREA CURRENCY, NO RECS IN SUBSCHEMA
2      AREA CREC ID NOT IN CURRENT LIST ON SAVE
3      SET CREC NOT IN MR53 OR OR52 ON RESTORE
4      AREA CREC NOT IN SUBSCHEMA
5      BAD STATUS FROM DBMS READ OF RECORD PREFIX
6      ERROR ON NATIVE VSAM RESTORE
7      DBKEY DEADLOCK ENCOUNTERED DURING CURRENCY RESTORE
8      NO LKS FOR LTE ON CURRENCY SAVE/RESTORE

Module:

RHDCCURS

Severity:

3

DC061002

TASK: <task-code> PROG: <program-name>: CURRENCY SAVE/RESTORE DEADLOCK ERROR CODE IS <code-number> RUN UNIT WILL BE ROLLED OUT

Reason:

A DBKEY deadlock has occurred during currency restore. The RUN UNIT will be terminated and rolled out and a 0029 will be returned to the dialog.

Module:

RHDCCURS

Severity:

0

DC061003

TASK: <task-code> PROG: <program-name>; CURRENCY RESTORE ERROR CODE IS <code-number>

Reason:

An error has been detected during currency restore. The error is caused because an area has been varied since currencies were saved. Possible error codes are:

Code   Meaning

1      UNABLE TO REREADY AN AREA WHEN RESUMING A SUSPENDED
       TABLE PROCEDURE                          '
2      UNABLE TO RESTORE UNRELIABLE CURRENCIES FOR AN AREA
       READIED IN UPDATE MODE

Module:

RHDCCURS

Severity:

5

DC063001

DRIVER <pterm-id> DISCONNECTED FROM <node-name>.

Reason:

The link between the host DC/UCF node and the target DC/UCF node has been broken. This condition usually indicates that the target node has been brought down. When the target node is brought back up, it will be reconnected to the target node automatically.

Module:

RHDCNODE

Severity:

0

DC066001

OPERATOR COMMAND NOT RECOGNIZED

Reason:

An invalid command or reply number has been entered at the operator's console. Check the command syntax, verify the reply number, and retry the command.

Module:

RHDCWTL

Severity:

0

DC066002

COMMAND OUTPUT AREA OVERFLOWED--INPUT IGNORED

Reason:

The length of the message or command issued exceeds the maximum length allowed (150 characters).

Module:

RHDCWTL

Severity:

0

DC066003

LOGIC ERROR DETECTED IN WTLEP2

Reason:

A system internal error has occurred, possibly caused by storage having been overwritten.

Module:

RHDCWTL

Severity:

0

DC066004

PREVIOUS MESSAGE STILL UNPROCESSED

Reason:

A previous message or command with the same reply identifier is still being processed. Wait until the previous message or command is completed before entering another request.

Module:

RHDCWTL

Severity:

0

DC066005

NO SUCH REPLY OUTSTANDING

Reason:

The entered message or command specifies a reply identifier that is not currently present. It is possible that the DC/UCF system is still processing the previous command. In this case, wait until the DC/UCF system finishes processing the command and displays a command entry prompt (for example, ENTER NEXT TASK CODE or REPLY WITH RQUEST). Then, reenter the message or command.

Module:

RHDCWTL

Severity:

0

DC066006

WTL FAILED--#GETRU FAILED

Reason:

A database error has occurred during access of the DDLDCMSG area. Refer to the accompanying DC076<nnn> message for further information.

Module:

RHDCWTL

Severity:

0

DC066007

WTL FAILED--@BIND FAILED

Reason:

A write-to-log has failed during an attempt to bind a record in the DDLDCMSG area. The write-to-log will be completed without using text from the message dictionary. Refer to the accompanying DC076<nnn> message for further information.

Module:

RHDCWTL

Severity:

0

DC066008

WTL FAILED--@OBTAIN FAILED

Reason:

A write-to-log has failed during an attempt to obtain message text from the DDLDCMSG area. The write-to-log will be completed without using text from the message dictionary. Refer to the accompanying DC076<nnn> message for further information.

Module:

RHDCWTL

Severity:

0

DC067001

TASK: <task-code>, PROG: <program-name>;DEADLOCK OCCURRED WHILE TRYING TO ACQUIRE LTE <lterm-id>

Reason:

The named program has attempted to acquire the named logical terminal (printer or nonprinter), but the logical terminal was unavailable and waiting would have caused a deadlock. Reinvoke the task.

Module:

RHDCTERM

Severity:

3