HP 3000 Manuals HP 3000 Manuals
Utility Error Messages (contd.)
Utility Program Conditional Messages (contd.)
---------------------------------------------------------------
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
DBSTORE
DBRESTOR
DBLOAD
DBUNLOAD
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.
---------------------------------------------------------------