MPE/iX Error Messages Manual Vol 3 (32650-90880)

276 Chapter7
TurboIMAGE/XL V iii C 5
Utility Error Messages
Utility Error Messages
Two types of error messages are generated by the utility programs. The first type consists
of conditional errors associated with accessing the desired database. For all utility
programs except DBUTIL, errors generating these messages can be corrected without
terminating the run if you are in session mode. DBUTIL errors of this type may terminate
the program. After printing the error message, the DBUTIL program reprompts with two
greater than symbols (>>). Other utilities 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 may type a carriage return with or without leading
blanks. If you are in job mode, conditional errors always cause program termination.
Conditional error messages and their meanings are described in the section entitled
"Utility Program Conditional Messages".
Unconditional errors occur in utility programs after successful execution has already
begun. These errors usually cause program termination. The accompanying messages and
their meanings are described in the section entitled "Utility Program Unconditional
Messages."
Utility Program Conditional Messages
MESSAGE ACCESS DISABLED UNTIL RECOVERY HAS COMPLETED
CAUSE 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
CAUSE The acctname part of DBNAME2 is too long.
ACTION Use the EDITOR to change the FILE command.
MESSAGE APPARENT BACKUP/LOGFILE MISMATCH
CAUSE A call to DBPUT, DBUPDATE, or DBDELETE, that apparently succeeded
when logging has failed during recovery.
ACTION Make sure the proper backup database was restored and that the
matching log file was used for recovery.
MESSAGE AUTODEFER MUST BE DISABLED BEFORE ILR CAN BE ENABLED
CAUSE AUTODEFER option in DBUTIL has been enabled for the database.
ROLLBACK or ILR cannot be enabled while output deferred mode is
enabled.
ACTION Run DBUTIL and >>DISABLE AUTODEFER and >>ENABLE ILR or
ROLLBACK for the database.
MESSAGE AUTODEFER MUST BE DISABLED BEFORE ROLLBACK CAN BE ENABLED
CAUSE The rollback recovery option cannot be used when the database has been
enabled for AUTODEFER.