iX V6.5 (30391-90011)

Appendix A 591

Error Messages

Utility Error Messages

Two types of error messages are generated by the utility programs. The ﬁrst type is

conditional errors, which occur when a utility cannot begin a function. Conditional errors

do not cause utility program termination; this is discussed in more detail below. The

second type is unconditional errors, which occur when a utility cannot complete a function.

Unconditional errors usually cause program termination.

Conditional errors are associated with accessing the speciﬁed database. If you are in

session mode, conditional errors can be corrected without terminating the run. After

printing the error message, all utility programs, with the exception of DBUTIL, reprompt

with the message "WHICH DATABASE?", allowing you to reenter the database reference. If

you wish to terminate the utility program at this point, you can type a carriage return with

or without leading blanks. DBUTIL, after printing the error message, reprompts with two

greater than symbols (>>) at which point you can exit or enter another command. When

DBUTIL encounters any errors while executing, a job control word (JCW) is set to 99. You

can check the JCW in batch mode to determine whether or not a command was accepted. If

you are in job mode and a conditional error occurs while a function is executing, that

function is terminated.

The messages associated with conditional and unconditional errors are described along

with their meanings in the sections entitled "Utility Program Conditional Messages" and

"Utility Program Unconditional Messages."

Utility Program Conditional Messages

MESSAGE ACCESS DISABLED UNTIL RECOVERY HAS COMPLETED

MEANING Database is disabled for access, and recovery is enabled.

ACTION Users will be able to access the database after the recovery process has

completed.

MESSAGE ACCT NAME MORE THAN 8 CHARACTERS

MEANING The acctname part of DBNAME2 is too long.

ACTION Use EDITOR to change the FILE command.

MESSAGE APPARENT BACKUP/LOGFILE MISMATCH

MEANING A call to DBPUT, DBUPDATE, or DBDELETE, that apparently succeeded

when logging to the original database has failed during recovery.

ACTION Make sure the proper backup database was restored and that the

matching log ﬁle was used for recovery.