 |
» |
|
|
|
|  | |
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.
- ACTION
Disable AUTODEFER and enable ROLLBACK using DBUTIL.
- MESSAGE
BACKUP DATABASE AND LOG FILE DO NOT MATCH
- CAUSE
The logid of the log file and the logid in the database being recovered do not match;
i.e., the correct log file is not being used for recovery.
- ACTION
Make sure that the database is using the correct log file.
- MESSAGE
BAD DATA BASE REFERENCE
- CAUSE
Data base reference following the utility program
:RUN command has a syntax error.
- ACTION
Correct the error in session mode or press return to terminate
the program.
- MESSAGE
BAD MAINTENANCE WORD
- CAUSE
User invoking the utility is not the creator
of the referenced database and has not supplied the
correct maintenance word.
- ACTION
Correct the error in session mode or press return to terminate
the program.
- MESSAGE
CANNOT ENABLE BREAK KEY
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
CANNOT OPEN DATABASE
- CAUSE
The database cannot be opened at this time. It
may already be open in a mode that does not
allow concurrent access.
- ACTION
Try the DBUTIL command again later.
- MESSAGE
CANNOT PARSE LOG FILE NAME
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
CAN'T RECOVER DATA BASES IN STATISTICAL MODE
- CAUSE
The CONTROL STATS command was entered subsequent to a
RECOVER command.
- ACTION
Rerun DBRECOV without using statistical mode, or use
statistical mode without specifying databases or recovery.
- MESSAGE
CAN'T OPEN DATA BASE- DBERROR message
- CAUSE
Database cannot be opened.
- ACTION
Check the DBERROR message to determine the problem.
- MESSAGE
CHECKSUM FAILURE ON LOG RECORD #n -EOF ASSUMED
- CAUSE
May occur if the system failed and a startup recovery
is not performed. Also may occur if a statistical
recovery is used against an open log file.
- ACTION
You may want to use a warmstart recovery in the future,
but this is not absolutely necessary.
- MESSAGE
COULD NOT FIND OPEN DATABASE IN DATABASE TABLE
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
CURRENT SINGLE TRANSACTION DOESN'T MATCH LOG TRANSACTION
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
CURRENT TRANSACTION DOESN'T MATCH LOG FILE TRANSACTION
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
DATABASE-ACCESS FILE DOES NOT EXIST
- CAUSE
No such file exists in the logon user or account.
- ACTION
Check the files in group to determine the correct file name.
- MESSAGE
DATABASE-ACCESS FILE NAME MAY NOT BE QUALIFIED
- CAUSE
The DBA file name cannot be qualified with group and account.
- ACTION
Log on in the same group and account as the database-access file.
- MESSAGE
DATABASE-ACCESS FILENAME TOO LONG
- CAUSE
The file name has more than six characters.
- ACTION
Rename the file and try DBUTIL again.
- MESSAGE
DATA BASE ALREADY CREATED
- CAUSE
You have invoked DBUTIL in the CREATE mode and
specified the name of a database which already exists.
- ACTION
In session mode, correct the error or press Return
to terminate program.
- MESSAGE
DATA BASE ALREADY DISABLED FOR option
- CAUSE
The option has already been disabled for this database.
- ACTION
Press return to terminate the program.
- MESSAGE
DATA BASE ALREADY ENABLED FOR option
- CAUSE
The option has already been enabled for this database.
- ACTION
Press return to terminate the program.
- MESSAGE
DATA BASE CANNOT BE ERASED UNTIL RECOVERY HAS COMPLETED
- CAUSE
Erasing database is attempted when recovery was started
but not completed, or while recovery is in RESTART mode.
- ACTION
Press return to terminate program. After the recovery process
has completed, the user can run DBUTIL again.
- MESSAGE
DATA BASE CANNOT BE PURGED UNTIL RECOVERY HAS COMPLETED
- CAUSE
Purging the database is attempted when recovery was started
but not completed, or while recovery is in RESTART mode.
- ACTION
Press return to terminate program. After the recovery process
has completed, the user can run DBUTIL again.
- MESSAGE
DATA BASE CONTAINS INVALID LOGGING IDENTIFIER
- CAUSE
The log identifier in the database root file does not
exist in the MPE/iX table.
- ACTION
Use DBUTIL to set a valid log identifier into the database.
- MESSAGE
DATA BASE HAS BEEN MODIFIED SINCE LAST RESTORE
- CAUSE
The DBSTORE flag has not been reset. This may mean
a backup database has not been restored, or that
there have been modifications since the last restoration.
- ACTION
Restore the backup database, or use the CONTROL NOSTORE
option and reenter the RECOVER command.
- MESSAGE
DATA BASE n HASN'T BEEN CREATED YET
- CAUSE
The database creator must run DBUTIL and CREATE the database.
- ACTION
In session mode, correct the error or Return to terminate the program.
- MESSAGE
DATA BASE IN USE
- CAUSE
Utility program cannot get exclusive access to the
referenced database due to other current users.
- ACTION
In session mode, press Return to terminate the program.
- MESSAGE
DATA BASE IS NOT EMPTY. LANGUAGE CANNOT BE CHANGED
- CAUSE
The language can be changed only on a virgin root file or
an empty database.
- ACTION
In session mode, press return to terminate the program.
- MESSAGE
DATA BASE IS REMOTE
- CAUSE
You must be logged on to the same group and account
containing the root file to use DBUTIL.
- ACTION
Do a remote logon and run DBUTIL from your remote session.
- MESSAGE
DATA BASE NAME MAY NOT BE QUALIFIED
- CAUSE
The database name cannot be qualified with group and account.
- ACTION
Log on to the same group and account as the database and reenter
the command.
- MESSAGE
DATA BASE NAME TOO LONG
- CAUSE
The database name you specified has more than
six characters.
- ACTION
Try the command again with the correct name.
- MESSAGE
DATA BASE NOT ENABLED FOR RECOVERY
- CAUSE
The recovery flag in the database root file is disabled.
- ACTION
Be sure you are running recovery against the appropriately
restored database. You can override the disable flag with
DBUTIL if necessary.
- MESSAGE
DATA BASE LANGUAGE NOT SYSTEM SUPPORTED
- CAUSE
The language of the database is not currently
configured on your system.
- ACTION
Notify the system manager.
- MESSAGE
DATABASE OR ACCESS FILE DOES NOT EXIST
- CAUSE
No such file exists in logon group or account.
- ACTION
Check the files in your group to find the correct file name.
- MESSAGE
DATA BASE OR FILE ACCESS NAME REQUIRED
- CAUSE
The command must include the database or access
file name.
- ACTION
Reenter the command.
- MESSAGE
DATA BASE OR FILE ACCESS NAME TOO LONG
- CAUSE
File name has more than six characters.
- ACTION
Reenter the command with the correct name.
- MESSAGE
DATA BASE REQUIRES CREATION
- CAUSE
The database creator must run the DBUTIL program in CREATE
mode prior to executing DBUNLOAD, DBLOAD, or DBUTIL in
ERASE mode.
- ACTION
In session mode, correct the error or press return
to terminate the program.
- MESSAGE
DATABASE TABLE OVERFLOWED
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
DATABASE TABLE TRANSACTION COUNT IS NEGATIVE
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
DATA SET n IS MISSING
- CAUSE
The data set may have been purged, or was not restored.
- ACTION
Contact your database administrator or system manager.
- MESSAGE
DBBEGIN FOUND AN ALREADY ACTIVE TRANSACTION
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
DBBEGIN FOUND PROCESS ALIVE, BUT NOT ACTIVE
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
DBEND FOUND TRANSACTION STILL ALIVE AND ACTIVE
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
DBEND FOUND TRANSACTION WHICH ALREADY ENDED
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
DBNAME DBSTORE OF TIME, DATE REQUIRED
- CAUSE
DBSTORE timestamp in database does not match those in
DBOPEN records.
- ACTION
Restore the proper database or use the proper log file.
You can also use the NOSTAMP option in recovery.
- MESSAGE
DBLOAD TO DIFFERENT DATABASE NAME MAINTENANCE WORD IS NOT ALLOWED
- CAUSE
The DBLOAD database name and maintenance word must be the
same as those used for DBUNLOAD.
- ACTION
Use a database name and maintenance word which were used for
the DBUNLOAD.
- MESSAGE
DBLOAD TO DIFFERENT GROUP OR ACCOUNT IS NOT ALLOWED.
- CAUSE
DBLOAD must be done from the same group and account as the
DBUNLOAD file.
- ACTION
Log on to the same group and account from which the DBUNLOAD
was done. Then use DBLOAD again.
- MESSAGE
DUPLICATE FILE NAME
- CAUSE
The required file name is already assigned to another
file. Example: If the ORDERS database requires six data
sets (ORDERS01-ORDERS06), then a previously defined
file ORDERS03 will trigger this message. This can
occur if a database is not purged before running DBRESTOR.
- ACTION
In session mode, correct the error or press return to
terminate the program.
- MESSAGE
DBNAME1 MORE THAN SIX CHARACTERS
- CAUSE
dbname1 is too long.
- ACTION
Use EDITOR to change the FILE command.
- MESSAGE
'DEV' MISSING
- CAUSE
Either the keyword DEV or the following "=" was
not found.
- ACTION
Use EDITOR to change the FILE command.
- MESSAGE
DEVICE NOT 'DISC'
- CAUSE
The string following the "#" sign was not "DISC."
- ACTION
Use EDITOR to change the FILE command.
- MESSAGE
DSDEVICE DOESN'T MATCH FILE COMMAND
- CAUSE
The dsdevice name in the DSLINE command was not the
same as the dsdevice name in the FILE command.
- ACTION
Use EDITOR to change the command which is in error.
- MESSAGE
DSDEVICE NAME MORE THAN 8 CHARACTERS
- CAUSE
The dsdevice name is too long.
- ACTION
Use EDITOR to change the command which is in error.
- MESSAGE
EMBEDDED BLANK IN DBNAME2
- CAUSE
One of the periods separating the user name from the group name
or the group name from the account name was preceded or followed
by a blank.
- ACTION
Use EDITOR to change the file command.
- MESSAGE
ERROR READING ROOT FILE LABEL
- CAUSE
DBUTIL is unable to read the root file.
- ACTION
Contact your HP systems engineer.
- MESSAGE
ERROR READING ROOT FILE RECORD
- CAUSE
DBUTIL is unable to read a root file record.
- ACTION
Contact your HP systems engineer.
- MESSAGE
ERROR WRITING ROOT FILE LABEL
- CAUSE
DBUTIL found an error while writing the root file label.
- ACTION
Contact your HP systems engineer.
- MESSAGE
ERROR WRITING ROOT FILE RECORD
- CAUSE
DBUTIL found an error while writing to a root file
record.
- ACTION
Contact your HP systems engineer.
- MESSAGE
EXCEEDS ACCOUNT DISC SPACE
- CAUSE
Amount of space required by the database plus the space
already assigned to other files exceeds the disk space
available to the account.
- ACTION
Request system manager to increase account's disk space.
- MESSAGE
EXCEEDS GROUP DISC SPACE
- CAUSE
The amount of disk space required by the database plus the space assigned to other files in
the group exceeds the amount of disk space
available to the account.
- ACTION
Request the system manager to increase the
group's disk space.
- MESSAGE
EXPECTED DATABASE STATE TO BE "CLOSED"
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
FCHECK FAILURE FCLOSE FAILURE FCONTROL FAILURE FENTRY FAILURE FGETINFO FAILURE - CAUSE
These are exceptional errors indicating a
hardware or software failure.
- ACTION
Notify your system manager of the failure.
- MESSAGE
FFILEINFO INTRINSIC FAILED
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
FGETINFO CANNOT VERIFY THAT FILE IS TYPE "LOG"
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
FGETINFO INTRINSIC FAILED
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
FILE CODE IS NOT 0.
- CAUSE
The database-access file to be activated has a
file code of other than 0.
- ACTION
Be sure you have the correct EDITOR file.
- MESSAGE
FILE EQUATES ARE ILLEGAL FOR DATA BASE AND DATA BASE ACCESS FILE
- CAUSE
DBUTIL does not allow you to equate the name of the
database or database-access file to another file
with the :FILE command.
- ACTION
Use the :RESET command to cancel the :FILE command.
You can either break and resume execution or exit
DBUTIL and run it again.
- MESSAGE
FILE file name RECSIZE TOO SMALL: LOG(S)
TRUNCATED.
- CAUSE
User recovery file size is too small to hold the
largest log record.
- ACTION
Increase record size or use variable length records.
- MESSAGE
FILE NAME MAY NOT BE QUALIFIED
- CAUSE
The file name may not be qualified with group and account.
- ACTION
Log on to the same group and account and reenter the command.
- MESSAGE
FILE NAME MORE THAN SIX CHARACTERS
- CAUSE
The file name part of dbname2 is too long.
- ACTION
Use the EDITOR to change the FILE command.
- MESSAGE
FOPEN FAILURE ON logfilename:ferrmsg
- CAUSE
You cannot open the log file.
- ACTION
Examine ferrmsg to determine the cause.
- MESSAGE
FREAD ERROR ON ASCII ACCESS FILE
- CAUSE
Exceptional errors indicate a hardware or
software failure.
- ACTION
Notify the system manager of the error.
- MESSAGE
FWRITE ERROR ON filename:ferrmsg
- CAUSE
FWRITE failure on user recovery file.
- ACTION
Check ferrmsg to determine the cause.
- MESSAGE
GROUP NAME MORE THAN 8 CHARACTERS
- CAUSE
The group name part of dbname2 is too long.
- ACTION
Use the EDITOR to change the FILE command.
- MESSAGE
ILR MUST BE DISABLED BEFORE AUTODEFER CAN BE ENABLED
- CAUSE
Output deferred option (AUTODEFER) cannot be used when
the database has been enabled for ILR or ROLLBACK.
- ACTION
Disable ILR or ROLLBACK and enable AUTODEFER using DBUTIL.
(Refer to the appropriate documentation for more information on AUTODEFER.)
- MESSAGE
INCOMPLETE
- CAUSE
The operation was interrupted while in process.
- ACTION
Contact your system manager.
- MESSAGE
INCOMPLETE DBNAME2
- CAUSE
The file name or group name is followed by a period
and the rest of the record is empty. Or the next
character is a semicolon (;).
- ACTION
Use the EDITOR to change the FILE command.
- MESSAGE
INCOMPLETE LOCAL PART
- CAUSE
The period following the local user name was missing,
or the account name was missing, or a comma followed the
account name and the group name was missing.
- ACTION
Use the EDITOR to change the HELLO command.
- MESSAGE
INCOMPLETE REMOTE PART
- CAUSE
The period following the rusername was missing,
or the raccountname was missing, or the raccountname
was followed by a comma and the rgroupname was missing.
- ACTION
Use the EDITOR to change the HELLO command.
- MESSAGE
INSUFFICIENT DISC SPACE
- CAUSE
The amount of disk space required for the database
is not available on the system.
- ACTION
Consult with the system manager about disk space
requirements.
- MESSAGE
INSUFFICIENT VIRTUAL MEMORY
- CAUSE
Not enough virtual memory is available to
open and access the database.
- ACTION
Try running the utility later when the system is not as busy.
- MESSAGE
INTERNAL ERROR—CURRENT TRANSACTION COUNT IS NEGATIVE
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
INTERNAL ERROR—DATABASE CONTAINS INVALID LOGGING IDENTIFIER
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
INTERNAL ERROR—DATABASE SHOULD NOT BE OPEN AT THIS TIME
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
INTERNAL ERROR—DBBEGIN FOUND PROCESS ALIVE, BUT TRAN STATE INACTIVE
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
INTERNAL ERROR—EXPECTED DATABASE TO BE OPEN FOR THIS PROCESS
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
INTERNAL ERROR—FOPEN FAILS IN F'HEADLOG
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
INTERNAL ERROR—FREADLABEL FAILS IN F'HEADLOG
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
INTERNAL ERROR—HEAP STAGING AREA OVERFLOWED
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
INTERNAL ERROR—INVALID DATABASE TABLE ADDRESS
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
INTERNAL ERROR—INVALID DBTAB'PROC'TAIL
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
INTERNAL ERROR—INVALID PASSWORD FOR DATABASE LOGGING IDENTIFIER
- CAUSE
Log password does not correspond with the log identifier in the log file.
- ACTION
Contact your system manager.
- MESSAGE
INTERNAL ERROR—INVALID PROCTABLE INDEX FOUND IN PROC'ACTIVELINK
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
INTERNAL ERROR—INVALID RECOVERY TABLE ADDRESS
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
INTERNAL ERROR—LOGID'TO'FNAME FAILURE
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
INTERNAL ERROR—NO PROCESS TABLE ENTRY EXISTS
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
INTERNAL ERROR—PROBLEM RETURNING HEAP
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
INTERNAL ERROR—PROCESS NOT IN PROCESS TABLE
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
INTERNAL ERROR—PROCESS TABLE IS FULL
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
INTERNAL ERROR—RECORD TABLE IS FULL
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
INTERNAL ERROR—UNABLE TO ALLOCATE THE HEAP
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
INVALID ACCESS CLASS NUMBER
- CAUSE
The access class should be a number between 1 and 63.
- ACTION
Reenter with a valid access class number.
- MESSAGE
INVALID CHARACTER IN PASSWORD
- CAUSE
Password does not consist of allowed characters.
- ACTION
Check the password specified and reenter the command.
- MESSAGE
INVALID COMMAND
- CAUSE
Command is unknown to the utility.
- ACTION
Check spelling or see manual for legal commands.
- MESSAGE
INVALID CONTENTS OF ASCII ACCESS FILE
ACTIVATION / DEACTIVATION FAILED
- CAUSE
The file specified is either
Not a database-access file, or
It does not contain the valid format and parameters.
- ACTION
Either
Verify the correct database-access file, or
Use EDITOR to
make the required changes and try accessing again.
- MESSAGE
INVALID DATA BASE CONTROL BLOCK
- CAUSE
TurboIMAGE/XL encountered an inconsistency in the control blocks.
- ACTION
Contact your system engineer.
- MESSAGE
INVALID DATA BASE ACCESS FILE NAME
- CAUSE
The file name or database name must be 1 to 6 characters
starting with a letter.
- ACTION
Reenter the command with the correct name.
- MESSAGE
INVALID DATA BASE NAME
- CAUSE
The file name or database name must be 1 to 6 characters
starting with a letter.
- ACTION
Reenter the command with the correct name.
- MESSAGE
INVALID DATA BASE NAME OR ACCESS FILE NAME
- CAUSE
The file name or database name must be 1 to 6 characters
starting with a letter.
- ACTION
Reenter the command with the correct name.
- MESSAGE
INVALID DB INTRINSIC CODE IN LOG RECORD CODE FIELD
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
INVALID DELIMITER
- CAUSE
The command or a space is incorrectly positioned.
- ACTION
Use HELP to check command syntax and reenter the
command.
- MESSAGE
INVALID FIRST LOG FILE NAME
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
INVALID FIRST LOG FILE SEQUENCE NUMBER
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
INVALID FIRST LOG FILE TIMESTAMP
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
INVALID IMAGE LOG RECORD DETECTED
- CAUSE
DBRECOV encountered an undefined log record code.
- ACTION
Notify the system manager and HP Support Representative.
- MESSAGE
INVALID LANGUAGE
- CAUSE
Language name or number has invalid characters.
- ACTION
Retype the correct language name or number.
- MESSAGE
INVALID LOG CODE IN LOG RECORD
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
INVALID LOG DEVICE TYPE IN LOG RECORD
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
INVALID LOG FILE DEVICE TYPE
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
INVALID MAINTENANCE WORD
- CAUSE
An incorrect maintenance word was used.
- ACTION
Check the maintenance word specified and reenter the command.
- MESSAGE
INVALID NUMBER OF BUFFERS SPECIFIED
- CAUSE
The number of buffers must be between 4 and 255.
- ACTION
Reenter DBUTIL >>SET command with a valid number.
- MESSAGE
INVALID NUMBER OF USERS SPECIFIED
- CAUSE
The minimum number of users allowed is 1 and the maximum
is 120. The ranges of users specified must be in ascending
order.
- ACTION
Reenter DBUTIL >>SET command with a valid number.
- MESSAGE
INVALID PARAMETER
- CAUSE
You specified an incorrect parameter.
- ACTION
Use HELP to check the command format and reenter
the command.
- MESSAGE
INVALID PASSWORD FOR DATA BASE LOGGING IDENTIFIER
- CAUSE
Log password does not correspond with the log identifier
used with the GETLOG command.
- ACTION
Use DBUTIL to set the valid log identifier password
into the database.
- MESSAGE
INVALID SUBSYSTEM ACCESS FLAG IN ROOT FILE
- CAUSE
TurboIMAGE/XL detected an invalid value for the subsystem access
in the root file. Valid accesses are READ, R/W, and NONE.
- ACTION
Reset the subsystem access flag using DBUTIL >>SET command.
- MESSAGE
INVALID TRANSACTION SEQUENCE DETECTED
- CAUSE
Internal error. The transaction numbers are not consecutive.
- ACTION
Notify your system manager and HP Support Representative.
- MESSAGE
INVALID (x) IN COLUMN y
- CAUSE
The x represents the invalid character found in
column y.
- ACTION
Use the EDITOR to change the database-access file record
which returns the error message.
- MESSAGE
LANGUAGE MUST NOT BE LONGER THAN 16 CHARACTERS
- CAUSE
The language name is too long.
- ACTION
Retype the correct language name.
- MESSAGE
LANGUAGE NOT SUPPORTED
- CAUSE
The language is not supported on your system or is not
a valid language name.
- ACTION
Check with your system manager for the configuration of
the language, or enter a valid language name or number.
- MESSAGE
LESS THAN 3 RECORDS IN FILE!
- CAUSE
The database-access file does not contain a FILE, DSLINE,
and HELLO command.
- ACTION
Use the EDITOR to create the missing records.
- MESSAGE
LOCAL ACCT NAME IS TOO LONG
- CAUSE
lacctname is more than eight characters.
- ACTION
Use the EDITOR to change the lacctname.
- MESSAGE
LOCAL GROUP NAME IS TOO LONG
- CAUSE
lgroupname has more than eight characters.
- ACTION
Use the EDITOR to change the lgroupname.
- MESSAGE
LOCAL USER NAME TOO LONG
- CAUSE
lusername has nore than eight characters.
- ACTION
Use EDITOR to change the lusername.
- MESSAGE
LOG BUFFER OVERFLOW
- CAUSE
There is insufficient buffer space to build the log record.
- ACTION
Notify the system manager and HP Support Representative.
- MESSAGE
LOG BUFFER OVERFLOW DURING GET NEXT LOGICAL LOG RECORD
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
LOG FILE AND DATABASE IDs DO NOT MATCH
- CAUSE
Internal error. Database is not using the correct log file.
- ACTION
Contact your system manager.
- MESSAGE
LOGFILE AND DATA BASE LOGID'S DO NOT MATCH
- CAUSE
The restored database does not match the log file.
- ACTION
Be sure the log file and the backup database are
properly attached.
- MESSAGE
LOG FILE HEADER RECORD IS NOT FIRST RECORD
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
LOGFILE IS EMPTY
- CAUSE
The log file has no records.
- ACTION
Be sure you have correctly identified the log file.
- MESSAGE
LOG FILE OPEN FAILED
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
LOG FILE RECORD SIZE IS IMPROPER
- CAUSE
Internal error. The records are not 256 bytes with a fixed length.
- ACTION
Be sure this file is actually a log file. Contact your system manager.
- MESSAGE
LOGID:logid IS INVALID
- CAUSE
The database logid has been removed from the MPE/iX table.
- ACTION
Set the database to an existing logid, or use the GETLOG
command to establish the database logid on the MPE/iX table.
- MESSAGE
LOGID MUST NOT BE LONGER THAN 8 CHARACTERS
- CAUSE
The logid name is too long.
- ACTION
Retype the correct logid to set into the database.
- MESSAGE
LOGID PASSWORD IS INCORRECT
- CAUSE
The password has been altered, or you are using the
wrong password.
- ACTION
Set the logid with the correct password into the
database.
- MESSAGE
LOGGING IS ENABLED, CAN NOT CLEAR LOGID
- CAUSE
The logid cannot be changed while logging is in process
in order to ensure validity of recovery and logging.
- ACTION
Change the logid after the recovery process has completed.
- MESSAGE
LOG PERIOD DOES NOT EQUAL ONE (1)
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
MAINTENANCE WORD CANNOT BE CHANGED UNTIL RECOVERY HAS COMPLETED
- CAUSE
Changing maintenance word was attempted when recovery was
enabled.
- ACTION
After the recovery process has completed use the DBUTIL>>SET
command to change the maintenance word.
- MESSAGE
MAINTENANCE WORD REQUIRED
- CAUSE
The user invoking the utility is not the creator of the
referenced database and has not supplied a maintenance
word.
- ACTION
If DBUTIL, reenter the command with the maintenance word.
Otherwise correct the error or press return to
terminate the program.
- MESSAGE
MAINTENANCE WORD TOO LONG
- CAUSE
The specified maintenance word has more than
eight characters.
- ACTION
Reenter the command with the correct maintenance word.
- MESSAGE
MAXIMUM ERROR COUNT HAS BEEN EXCEEDED
- CAUSE
DBRecov keeps track of all the errors that were encountered. If the number goes past a certain threshold (default is 0, but can be configured up to a maximum of 3000), DBRecov will abort.
- ACTION
Correct the problems causing the errors. If the user specifies an error count, this count could also be increased.
- MESSAGE
MAXIMUM WARNING COUNT HAS BEEN EXCEEDED
- CAUSE
DBRecov keeps track of all the warnings that were encountered. If the number goes past a certain threshold, DBRecov will abort.
- ACTION
If the user specifies a warning count, this count could be increased.
- MESSAGE
MISSING!!
- CAUSE
The key word FILE is not found in the first record; or
the keyword DSLINE is not found in the second record;
or the keyword HELLO is not found in any of the remaining
records.
- ACTION
Use the EDITOR to modify the record in the database-access
file that returned the error message.
- MESSAGE
MISSING DBNAME1
- CAUSE
An equal sign (=), semicolon (;), or end of line
followed the keyword FILE.
- ACTION
Use the EDITOR to change the FILE command.
- MESSAGE
MISSING DBNAME2
- CAUSE
dbname1= followed by a semicolon (;) or end of line.
- ACTION
Use EDITOR to change the FILE command.
- MESSAGE
MISSING DSDEVICE
- CAUSE
DEV= was followed by a semicolon (;), #, or the
rest of the record was blank.
- ACTION
Use the EDITOR to change the FILE command.
- MESSAGE
MISSING LOCAL PART
- CAUSE
No characters preceded the =HELLO.
- ACTION
Use the EDITOR to change the HELLO command.
- MESSAGE
MISSING REMOTE PART
- CAUSE
The remote-ID-sequence of the database-access file is missing.
- ACTION
Use the EDITOR to add the remote part.
- MESSAGE
MISSING REMOTE PASWD
- CAUSE
HELLO was not followed by text, or was followed
by a semicolon (;).
- ACTION
Using the EDITOR, change the HELLO command.
- MESSAGE
MISSING SEMI-COLON
- CAUSE
DEV= was not preceded by a semicolon (;)
- ACTION
Use the EDITOR to change the FILE command.
- MESSAGE
MISSING # SIGN
- CAUSE
dsdevice was not followed by a #.
- ACTION
Use the EDITOR to change the FILE command.
- MESSAGE
MORE THAN ONE (1) LOG FILE HEADER RECORD IS FOUND
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
MULTIPLE LOG IDENTIFIERS NOT ALLOWED
- CAUSE
You tried to simultaneously recover databases that
logged to different log files.
- ACTION
Run DBRECOV once for each log file.
- MESSAGE
NEGATIVE CURRENT RECORD NUMBER IN BACKSPACE REQUEST
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
NEGATIVE NUMBER OF BACKSPACES REQUESTED
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
NLS RELATED ERROR
- CAUSE
An error was returned by NLS/3000 on a DBOPEN on
the database.
- ACTION
Notify the system manager.
- MESSAGE
NLINFO FAILURE
- CAUSE
An error was returned by NLS/3000
- ACTION
Notify system manager.
- MESSAGE
NO DATA BASE HAS BEEN SPECIFIED FOR RECOVERY
- CAUSE
RUN command has been entered and no databases
have been specified for recovery.
- ACTION
Use the RECOVER command to specify database(s) or
EXIT to terminate.
- MESSAGE
NON-CREATOR ACCESS NOT PERMITTED
- CAUSE
You must be the database creator to perform this
function, or you must use the maintenance word.
- ACTION
Log on as the database creator, or use the maintenance
word with the command. If the maintenance word is not set, have the
creator set one.
- MESSAGE
NONEXISTENT LOGID
- CAUSE
You are trying to set an unrecognized logid into
the database, or the database logid has been
removed from MPE/iX.
- ACTION
Use GETLOG to put the database logid into the MPE/iX
table, or set an existing logid into the database.
- MESSAGE
NO SUCH DATA BASE
- CAUSE
Specified database does not exist in users logon group.
- ACTION
Check base name and logon account and group.
Press return to terminate the program.
- MESSAGE
NOT A DATA BASE ACCESS FILE
- CAUSE
The specified file is not a database-access file.
- ACTION
Check the file name and try the command again.
- MESSAGE
NOT A DATA BASE OR DATA BASE ACCESS FILE
- CAUSE
The specified database is invalid, or the specified file is not a database-access file.
- ACTION
Check the database or file name and try the
command again.
- MESSAGE
NOT A DATA BASE ROOT FILE
- CAUSE
The specified file is not a database root file.
- ACTION
Check the specified database name and try the
command again.
- MESSAGE
NOT A PRIVILEGED DATA BASE ACCESS FILE
- CAUSE
The database-access file has not been activated.
- ACTION
Check the command and reenter it correctly.
- MESSAGE
NOT ALLOWED; MUST BE CREATOR
- CAUSE
The user invoking the utility is not the
creator of the database and the database
has no maintenance word.
- ACTION
Log on with correct user name, account and group.
- MESSAGE
NOT AN UNPRIVILEGED DATA BASE ACCESS FILE
- CAUSE
The database-access file is already activated.
- ACTION
Check the command and reenter it if necessary.
- MESSAGE
OUTMODED ROOT
- CAUSE
The root file of the specified database corresponds
to a different version of IMAGE software and is
not compatible with the utility program currently
executing.
- ACTION
Consult with your system manager to verify
the correct version of the software. Ask HP
Support Representative about conversion process.
- MESSAGE
PARAMETER EXPECTED
- CAUSE
The command you specified calls for another
parameter.
- ACTION
Use HELP to find the correct command syntax.
- MESSAGE
PARAMETER MUST BE A COMMAND
- CAUSE
Only command names may be specified with the
HELP command.
- ACTION
Reenter the command.
- MESSAGE
PARAMETER SPECIFIED TWICE
- CAUSE
The command specified requires only one parameter entry.
- ACTION
Reenter the command.
- MESSAGE
PARSE OF FILE REFERENCE FAILED
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
PASSWORD IS INCORRECT
- CAUSE
The logid password in the database is not the same
as the password in the MPE/iX table.
- ACTION
Set the logid and correct password into the database.
Or, use the MPE/iX ALTLOG command to alter the password
in the MPE/iX table so it matches the one in the database.
- MESSAGE
PASSWORD MUST NOT BE LONGER THAN 8 CHARACTERS
- CAUSE
The password is too long so it is incorrect.
- ACTION
Retype the correct logid and password.
- MESSAGE
PREMATURE EOF ON ASCII ACCESS FILE
- CAUSE
DBUTIL encountered an end of file mark before
at least one =HELLO record in the database-access file.
- ACTION
Use the EDITOR to change the ASCII
file.
- MESSAGE
PROCESS TABLE OVERFLOW
- CAUSE
At some point more than 180 processes
were logging at the same time.
- ACTION
Notify your system manager and HP Support Representative.
- MESSAGE
RECORD SIZE EXCEEDS 128 CHARACTERS!
- CAUSE
The longest record in the database-access file
exceeds the allowable length.
- ACTION
Use the EDITOR to modify the database-access file.
- MESSAGE
RECORDS ARE NUMBERED!
- CAUSE
The database-access file is numbered.
- ACTION
Use the EDITOR to keep the file unnumbered.
- MESSAGE
RECORD TABLE OVERFLOW
- CAUSE
More than 1000 detail records have been added and
they have been given relative record numbers
different from those originally assigned.
Wrong database may have been restored, or not all modifications to
the database were logged.
- ACTION
Run DBRECOV without the NOABORTS option or recover to a point
before the occurrence of the error.
Or restore the correct database. Or restore database and
perform DBUNLOAD/DBLOAD.
- MESSAGE
RECOVERY TABLE IS FULL
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
RECOVERY TABLE OVERFLOW
- CAUSE
You tried to specify more than 100 user recovery files.
- ACTION
Reduce the number of recovery files needed.
- MESSAGE
RELEASE OF ENTRY FROM RECOVERY TABLE FAILED
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
REMOTE ACCT racctname TOO LONG
- CAUSE
racctname is more than eight characters long.
- ACTION
Use the EDITOR to change the HELLO command.
- MESSAGE
REMOTE ACCT PASSWORD TOO LONG
- CAUSE
rupasw is more than eight characters.
- ACTION
Use the EDITOR to change the HELLO command.
- MESSAGE
REMOTE GROUP rgroupname TOO LONG
- CAUSE
rgroupname is more than eight characters.
- ACTION
Use the EDITOR to change the HELLO command.
- MESSAGE
REMOTE GROUP PASSWORD TOO LONG
- CAUSE
rgpasw is more than eight characters.
- ACTION
Use the EDITOR to change the HELLO command.
- MESSAGE
REMOTE USER rusername TOO LONG
- CAUSE
rusername is more than eight characters.
- ACTION
Use the EDITOR to change the HELLO command.
- MESSAGE
REMOTE USER PASSWORD TOO LONG
- CAUSE
rupasw is more than eight characters.
- ACTION
Use the EDITOR to change the HELLO command.
- MESSAGE
RESTART FILE OPEN FAILED
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
ROLLBACK MUST BE DISABLED BEFORE AUTODEFER CAN BE ENABLED
- CAUSE
Output deferred option (AUTODEFER) cannot be used when the database has been enabled for ROLLBACK.
- ACTION
Disable ROLLBACK and enable AUTODEFER using DBUTIL. (Refer to
the appropriate documentation for more information on AUTODEFER.)
- MESSAGE
ROLLBACK MUST BE DISABLED BEFORE LOGGING CAN BE DISABLED
- CAUSE
An attempt was made to disable logging while rollback
was still enabled.
- ACTION
Use DBUTIL >>DISABLE to disable the database for ROLLBACK, then logging.
- MESSAGE
ROOT FILE DOES NOT EXIST
- CAUSE
A root file with the name of the specified database
does not exist in the logon group and account.
- ACTION
Check the database name you specified and reenter the command.
- MESSAGE
SEQUENCE ERROR ON LOG RECORD #n - EOF ASSUMED
- CAUSE
Log record numbers are out of sequence.
- ACTION
Notify the system manager and HP Support Representative.
- MESSAGE
STAGING FILE OVERFLOW
- CAUSE
The staging file is not large enough.
- ACTION
Use a file equation to increase the file size.
- MESSAGE
TIMESTAMP OUT OF SEQUENCE ON LOG RECORD #n - EOF ASSUMED.
- CAUSE
Log record timestamps are out of sequence.
- ACTION
Notify the system manager and HP Support Representative.
- MESSAGE
TOO MANY PARAMETERS
- CAUSE
Too many parameters were entered with the command.
- ACTION
Reenter the command with the correct number of parameters.
- MESSAGE
UNABLE TO COPY GLOBAL AND TABLE INFORMATION TO RESTART FILE
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
UNABLE TO GET NEXT LOGICAL LOG RECORD
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
UNABLE TO GET PRIOR LOGICAL LOG RECORD
- CAUSE
Internal error.
- ACTION
Contact your system manager.
- MESSAGE
UNKNOWN COMMAND, TRY HELP
- CAUSE
DBUTIL does not recognize the command you specified.
- ACTION
Enter the HELP command to get the list of DBUTIL commands.
- MESSAGE
USER IS NOT CREATOR OF LOGGING IDENTIFIER
- CAUSE
A function or activity was attempted by someone other
than the creator of the log identifier.
- ACTION
Log on to the system as the user who created the log
identifier or as a user with system manager (SM) or operator (OP) capability.
- MESSAGE
WARNING: DATA BASE MODIFIED AND NOT DBSTORED
- CAUSE
The database has been enabled for logging but a
backup copy has not been made by executing DBSTORE.
- ACTION
Execute DBSTORE to make a backup copy of the database.
- MESSAGE
WARNING: THE LANGUAGE OF THE DATA BASE IS DIFFERENT
FROM THE LANGUAGE FOUND ON THE DBLOAD MEDIA.
CONTINUE DBLOAD OPERATION / (Y/N):
- CAUSE
The user has changed language of database
between DBUNLOAD and DBLOAD. DBLOAD wants user
to be aware of potential differences in sorted chains
of the collating sequence of the two languages.
(The language of database on disk and database
on tape are different).
In session mode you are asked if you want to continue
operation. In job mode, DBLOAD will
terminate execution.
- ACTION
After looking at the information, DBLOAD returns
with the result on the sorted chains in the database.
Continue the operation by answering Y (yes).
- MESSAGE
WARNING: THE NUMBER OF DATA SETS DEFINED IN THE SCHEMA IS
LESS THAN (OR GREATER THAN) THE NUMBER OF DATA SETS FOUND
ON THE DBLOAD MEDIA.
- CAUSE
You have added or deleted data sets from the database between a
DBUNLOAD and a DBLOAD. DBLOAD will continue with the
load, but data may be lost or put into the wrong sets
due to an invalid set change.
- ACTION
Stop the DBLOAD, correct the schema, and perform DBLOAD again.
Or, if you are sure the database is not corrupt, allow
DBLOAD to continue.
Utility Program Unconditional Messages | |
- MESSAGE
AUTOMATIC MASTER IS FULL ON PATH #n
- CAUSE
DBLOAD is unable to load a detail entry because the automatic
master set associated with path n of the detail set is full.
- ACTION
Re-create the root file with a larger capacity for automatic
master. Rerun the necessary utilities.
- MESSAGE
***BAD DATA BASE***
- CAUSE
This message is issued by DBSTORE, DBRESTOR, and
DBUNLOAD. It means the database is flagged "bad"
because of a known structural error due to an abnormal
termination or to a system crash during DBLOAD or some
other "output deferred" operation. The current operation
(DBSTORE, DBRESTOR, DBUNLOAD) continues to function
normally. DBLOAD additionally prints the message
"SERIAL UNLOAD FOLLOWS" and automatically operates in
serial mode. The database on disk retains its "bad"
flag and cannot be accessed through DBOPEN.
- ACTION
The database is not usable in its current state.
Purge it and restore a backup copy, or erase it and then load
a tape written by DBUNLOAD or another external
copy of the data.
- MESSAGE
BROKEN FILE EQUATION CHAIN FOR TAPE FILE
- CAUSE
Issued by DBSTORE if, in a chain of file equations,
the actual device designator cannot be found.
- ACTION
Check your :FILE commands and reenter them correctly
before running DBSTORE.
- MESSAGE
CANNOT GET EXTRA DATA SEGMENT NECESSARY FOR RESTORE OPERATION
- CAUSE
DBRESTOR was unable to get the extra data segment
it needed for the buffers used in the restore
operation.
- ACTION
Wait until system resources are available and then try again.
- MESSAGE
CANNOT OPEN TERMINAL,
TERMINATING
- CAUSE
DBUTIL is unable to access the terminal.
- ACTION
Call HP Support Representative.
- MESSAGE
CAN'T CREATE NEW COPY OF FILE x (FS ERROR #)
- CAUSE
MPE/iX intrinsic FOPEN failed while creating a temporary file.
- ACTION
Check the file system error.
Possible reasons: The specified device does not
exist, or there may be insufficient space on the device
specified.
- MESSAGE
CAN'T GET SPECIFICATIONS VIA FGETINFO FOR THIS FILE x
(FS error #)
- CAUSE
MPE/iX intrinsic FGETINFO failed. DBUTIL cannot get information
for the specified file.
- ACTION
Check the file system error to determine cause.
- MESSAGE
CAN'T OPEN FILE x (FS ERROR #)
- CAUSE
MPE/iX intrinsic FOPEN failed.
- ACTION
Check the file system error to determine cause.
- MESSAGE
CAN'T PURGE OLD COPY OF FILE x (FS ERROR #)
- CAUSE
MPE/iX intrinsic FCLOSE failed while purging the "old" file.
- ACTION
Check the file system error to determine cause.
- MESSAGE
CAN'T RESET MOVE FLAG FOR FILE x IN THE ROOT FILE
- CAUSE
Error occurred while writing root file label to reset the database return status.
- ACTION
Contact your system manager.
- MESSAGE
CAN'T SAVE NEW COPY OF FILE x (FS ERROR #)
- CAUSE
MPE/iX intrinsic FCLOSE failed while saving the temporary file.
- ACTION
Check file system error to determine the cause.
- MESSAGE
CAN'T SET MOVE FLAG FOR FILE x IN ROOT FILE
- CAUSE
DBUTIL set the root file flag, and an error
occurred while writing the root file label.
- ACTION
Contact your system manager.
- MESSAGE
CHAIN IS FULL ON PATH #n
- CAUSE
DBLOAD is unable to load a detail entry because the
chain count for path number n of detail set exceeds 231
-1 (or 2,147,483,647 entries).
- ACTION
Delete some of the entries and reload or change the
database design.
- MESSAGE
***COPY FAILED***
- CAUSE
An error occurred while copying the file. DBUTIL has
encountered a problem reading or writing the files. (It
is possible the disk pack is bad.)
- ACTION
Restore the database and try the move again. Contact your
system manager if the copy fails again.
- MESSAGE
COULD NOT ATTACH DATA SET n TO XM LOG FILE: FILE SYSTEM ERROR nn
- CAUSE
The data set could not be "attached" to the MPE/iX transaction recovery
mechanism. nn is the file system error number returned.
- ACTION
Notify HP Support Representative.
- MESSAGE
COULD NOT ATTACH DATA SET n TO XM LOG FILE: XM ERROR nn
- CAUSE
The data set n could not be "attached" to the MPE/iX transaction
recovery mechanism. nn is the error number returned.
- ACTION
Notify HP Support Representative.
- MESSAGE
COULD NOT DETACH DATA SET n FROM XM LOG FILE: FILE SYSTEM ERROR nn
- CAUSE
The data set n could not be "detached" from the MPE/iX transaction
recovery mechanism. The MPE/iX intrinsic FLABELOPEN failed. nn
is the file system error number returned.
- ACTION
Notify HP Support Representative.
- MESSAGE
COULD NOT DETACH DATA SET n FROM XM LOG FILE:
XM ERROR nn
- CAUSE
The data set n could not be "detached" from the MPE/iX transaction
recovery mechanism. nn is the error number returned.
- ACTION
Notify HP Support Representative.
- MESSAGE
COULDN'T OPEN THE DATABASE
- CAUSE
There is no root file for the specified file. It is
possible that the file specified is not part of the database.
- ACTION
Check the file or database. Try the operation again with
the correct file name.
- MESSAGE
DATA BASE STATE DOES NOT ALLOW MOVE TO BE DONE
- CAUSE
The database is in a state in which MOVE cannot be performed.
- ACTION
Check the database. If the database has not been created,
run DBUTIL >>CREATE. If the database is
damaged, run recovery.
- MESSAGE
DATA SET FULL
- CAUSE
Data set currently being loaded is full.
- ACTION
Re-create root file, increase the data set's capacity
and run the utilities again.
- MESSAGE
***DBSTORE FAILED - NO DATA BASE STORED***
- CAUSE
A file error or other message follows explaining the problem.
- ACTION
Contact your HP Support Representative.
- MESSAGE
EOF SEEN, PROGRAM TERMINATING
- CAUSE
An :EOF has been entered.
- ACTION
Run DBUTIL again.
- MESSAGE
FGETINFO FAILURE
- CAUSE
DBUTIL received an error when calling MPE/iX FGETINFO.
- ACTION
Contact your system manager.
- MESSAGE
FILE EQUATE FOR ONLY MAY USE DEV
- CAUSE
If you specify an input/output file with a :FILE
command for any of these utility programs, only the
file designators and DEV= parameters are allowed.
- ACTION
Enter :FILE command again and rerun program.
- MESSAGE
FILE NOT ON TAPE
- CAUSE
Issued by DBRESTOR if the database to be restored is not on the tape.
- ACTION
Check your :FILE command and/or the tape you mounted.
- MESSAGE
FILE x ALREADY RESIDES ON DEVICE x
- CAUSE
The file specified already resides on the device.
- ACTION
Continue with the next desired command, or exit from DBUTIL.
- MESSAGE
FREADDIR FAILURE
- CAUSE
This is an MPE/iX exceptional failure and is returned when DBUTIL calls FREADDIR.
- ACTION
Contact your system manager.
- MESSAGE
HARD TERMINAL READ ERROR, TERMINATING
- CAUSE
DBUTIL cannot read input from terminal.
- ACTION
Notify HP Support Representative.
- MESSAGE
***INVALID SET COUNT***
- CAUSE
TurboIMAGE/XL found an inconsistency in the data set count.
- ACTION
Notify HP Support Representative.
- MESSAGE
MOVE OF FILE x NOT ALLOWED: FILE IS NOT CORRECT
TYPE (FILE CODE #)
- CAUSE
The file specified is not a database file.
- ACTION
Try the MOVE operation again with the correct file name.
- MESSAGE
NO MANUAL ENTRY FOR DETAIL ON PATH #n
- CAUSE
DBLOAD is attempting to load detail data set entry n,
which is the number of the detail data set path referencing
the manual master in question.
- ACTION
Add entry to manual master with application program or
QUERY. Run DBLOAD again.
- MESSAGE
RECSIZE MUST BE <=xxxx AND EVENLY DIVISIBLE BY 256.
- CAUSE
Issued if REC= recsize parameter for DBSTORE specified
a record size not modulo 256 halfwords, or greater than the
configured record size of the device.
- ACTION
Check the REC= recsize parameter and correct it
before running DBSTORE again.
- MESSAGE
ROLLBACK LOG FILE MUST BE IN THE SAME VOLUME SET AS THE DATABASE
- CAUSE
MPE/iX transaction recovery requires that the MPE/iX user log file must
reside on the same volume set as the database.
- ACTION
Build the MPE/iX user log file in the same volume set as the database.
NOTE: Because all files in a group are in the same volume set, the MPE/iX
command LISTGROUP indicates the volume set where the database resides.
- MESSAGE
SWITCH TO NM TO ATTACH DATABASE TO XM LOG FILE FAILED: XM ERROR nn
- CAUSE
It is necessary to switch to NM to "attach" the database to the MPE/iX
recovery system. The switch failed. nn is the switch to NM error
number returned.
- ACTION
Notify HP Support Representative.
- MESSAGE
SWITCH TO NM TO DETACH DATABASE FROM XM LOG FAILED: SWITCH ERROR nn
- CAUSE
It is necessary to switch to NM to "detach" the database from
the MPE/iX transaction recovery mechanism. The switch failed. nn
is the switch to NM error number returned.
- ACTION
Notify HP Support Representative.
- MESSAGE
UNABLE TO CONTINUE
- CAUSE
DBUTIL program (operating in PURGE mode) cannot
continue execution due to exceptional error in file system.
This information is followed by MPE/iX file information
display.
- ACTION
Save the file information. Consult with system manager
and HP Support Representative.
- MESSAGE
UNABLE TO OBTAIN FILE LABEL INFORMATION FOR FILE x
- CAUSE
MPE/iX internal procedure failed. DBUTIL cannot obtain information
for the specified file.
- ACTION
Contact your system manager.
- MESSAGE
UNEXPECTED ROOT FILE STATE
- CAUSE
The MOVE process was unable to reset the database flag. The
database may be in an inconsistent state.
- ACTION
Contact your system manager.
- MESSAGE
WARNING: USER LOG FILE IS NOT IN THE SAME VOLUME SET AS THE DATABASE
- CAUSE
MPE/iX transaction recovery requires that the MPE/iX user log file must
reside on the same volume set as the database.
- ACTION
Build the MPE/iX user log file in the same volume set as the database. NOTE: Because all files in a group are in the same volume set, the MPE/iX command LISTGROUP indicates the volume set where the database resides.
Extended Utility Program Unconditional Messages | |
A set of messages may be returned when an unusual condition
causes TurboIMAGE/XL to fail while a TurboIMAGE/XL utility is executing. In
each of the following messages, the value
xxxxx is the location where TurboIMAGE/XL failed. Error messages 401 through 414 are all TurboIMAGE/XL
utility failures caused by failure of the TurboIMAGE/XL
intrinsic specified in the message. - -3
- MESSAGE
TURBOIMAGE FAILURE (FREADDIR FAILURE ON ROOT FILE AT xxxxx)
- CAUSE
Root file was not readable. Problem may be in
hardware.
- ACTION
Notify the system manager of the error.
- -4
- MESSAGE
TURBOIMAGE FAILURE (FREADLABEL FAILURE ON ROOT FILE AT xxxxx) - CAUSE
User's label was not readable. Problem may be in
hardware.
- ACTION
Notify the system manager of the error.
-64
- MESSAGE
SET NUMBERS ARE OUT OF SEQUENCE. TURBOIMAGE FAILED AT xxxxx
- CAUSE
The next set number on the backup volume was not
what DBLOAD expected. Status element 0 has the
expected set number; status element 1 has the next set number on
the backup volume.
- ACTION
The schema may have been changed since the last DBUNLOAD
and this DBLOAD. Add any new set the the end of the schema.
- -66
- MESSAGE
BLOCK NUMBERS ARE OUT OF SEQUENCE. TURBOIMAGE FAILED AT xxxxx. - CAUSE
The next block on the backup volume was not what DBLOAD expected. Status elements 0,1 have the expected block number; elements 2,3 have the actual next block number; element 4 has the set number. - ACTION
An error for a known value that was written to
tape with FWRITE was found. There may be a defect
in the tape or the tape drive.
- -70
- MESSAGE
ENTRY NUMBERS ARE OUT OF SEQUENCE. TURBOIMAGE FAILED AT xxxxx - CAUSE
The next block on the backup volume was not what
DBLOAD expected. Status elements 0,1 have the expected
block number; elements 2,3 have the actual next block
number; element 4 has the set number.
- ACTION
An error for a known value that was written to
tape with FWRITE was found. There may be a defect
in the tape or the tape drive.
- -74
- MESSAGE
THE RECORD JUST READ IS UNRECOGNIZABLE TURBOIMAGE FAILED AT xxxxx
- CAUSE
The record just read from the backup volume was not what
DBLOAD expected. The record could be an EOF, EOT, etc.
The status element 0 has one of the following codes for
the record expected:
- 0 -
tape head
- 1 -
data file head
- 2 -
data file block
- 3 -
data file end
- 4 -
tape end
- ACTION
An error for a known value that was written to
tape with FWRITE was found. There may be a defect
in the tape or the tape drive.
- 97
- MESSAGE
ZSIZE ERROR WHILE CONTRACTING AT xxxxx
- CAUSE
A TurboIMAGE utility called ZSIZE to contract the Z to DB
area of the stack. xxxxx is the octal location where
TurboIMAGE failed.
- ACTION
Notify HP Support Representative.
- 98
- MESSAGE
ZSIZE ERROR WHILE EXPANDING AT xxxxx
- CAUSE
A TurboIMAGE utility called ZSIZE to expand the Z to DB
area of the stack. xxxxx is the octal location
where TurboIMAGE failed.
- ACTION
Notify HP Support Representative.
- 101
- MESSAGE
DBRESTOR FAILURE IN DBRESTOR AT xxxxx
- CAUSE
The DBRESTOR utility called MPE/iX RESTORE which encountered
problems while restoring the database. A detailed error
message should follow this message.
- ACTION
Take appropriate action depending on the detail
message.
- 401
- MESSAGE
DBOPEN FAILURE AT xxxxx
- CAUSE
A detailed error message can be retrieved by calling DBEXPLAIN.
- ACTION
For more information "Library Procedure
Error Messages" earlier in this chapter.
- 402
- MESSAGE
DBINFO FAILURE AT xxxxx
- CAUSE
A detailed error message can be retrieved by calling DBEXPLAIN.
- ACTION
For more information see "Library Procedure
Error Messages" earlier in this chapter.
- 403
- MESSAGE
DBCLOSE FAILURE AT xxxxx
- CAUSE
A detailed error message can be retrieved by calling DBEXPLAIN.
- ACTION
For more information see "Library Procedure
Error Messages" earlier in this chapter.
- 404
- MESSAGE
DBFIND FAILURE AT xxxxx
- CAUSE
A detailed error message can be retrieved by calling DBEXPLAIN.
- ACTION
For more information see "Library Procedure
Error Messages" earlier in this chapter.
- 405
- MESSAGE
DBGET FAILURE AT xxxxx
- CAUSE
A detailed error message can be retrieved by calling DBEXPLAIN.
- ACTION
For more information see "Library Procedure
Error Messages" earlier in this chapter.
- 406
- MESSAGE
DBUPDATE FAILURE AT xxxxx
- CAUSE
A detailed error message can be retrieved by calling DBEXPLAIN.
- ACTION
For more information see "Library Procedure
Error Messages" earlier in this chapter.
- 407
- CAUSE
DBPUT FAILURE AT xxxxx
- CAUSE
A detailed error message can be retrieved by calling DBEXPLAIN.
- ACTION
For more information see "Library Procedure
Error Messages" earlier in this chapter.
- 408
- MESSAGE
DBDELETE FAILURE AT xxxxx
- CAUSE
A detailed error message can be retrieved by calling DBEXPLAIN.
- ACTION
For more information see "Library Procedure
Error Messages" earlier in this chapter.
- 409
- MESSAGE
DBLOCK FAILURE AT xxxxx
- CAUSE
A detailed error message can be retrieved by calling DBEXPLAIN.
- ACTION
For more information see "Library Procedure
Error Messages" earlier in this chapter.
- 410
- MESSAGE
DBUNLOCK FAILURE AT xxxxx
- CAUSE
A detailed error message can be retrieved by calling DBEXPLAIN.
- ACTION
For more information see "Library Procedure
Error Messages" earlier in this chapter.
- 411
- MESSAGE
DBCONTROL FAILURE AT xxxxx
- CAUSE
A detailed error message can be retrieved by calling DBEXPLAIN.
- ACTION
For more information see "Library Procedure
Error Messages" earlier in this chapter.
- 412
- MESSAGE
DBBEGIN FAILURE AT xxxxx
- CAUSE
A detailed error message can be retrieved by calling DBEXPLAIN.
- ACTION
For more information see "Library Procedure
Error Messages" earlier in this chapter.
- 413
- MESSAGE
DBEND FAILURE AT xxxxx
- CAUSE
A detailed error message can be retrieved by calling DBEXPLAIN.
- ACTION
For more information see "Library Procedure
Error Messages" earlier in this chapter.
- 414
- MESSAGE
DBMEMO FAILURE AT xxxxx
- CAUSE
A detail error message can be retrieved by calling DBEXPLAIN.
- ACTION
For more information see "Library Procedure
Error Messages" earlier in this chapter.
|
