HP 3000 Manuals HP 3000 Manuals
Utility Error Messages (contd)
Utility Program Conditional Messages (contd)
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
1. Not a database-access file, or
2. It does not contain the valid format and
parameters.
ACTION Either
1. Verify the correct database-access file, or
2. 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.
---------------------------------------------------------------