HP 3000 Manuals HP 3000 Manuals
Library Procedure Error Messages (contd)
Library Procedure Calling Errors
---------------------------------------------------------------
-11 MESSAGE Bad base reference
CAUSE For DBOPEN, the first two characters in base are
not blank, or database name contains special
characters other than period. For all other
procedures, either first two characters in base do
not contain the value assigned by DBOPEN or the
parameters passed to the procedure are incorrect in
type, sequence, or quantity.
ACTION Check application program's procedure call.
Correct error in call.
---------------------------------------------------------------
-12 MESSAGE intrinsic name called without covering lock in
effect (or see below)
CAUSE For DBUPDATE, DBPUT, and DBDELETE, database has
been opened in DBOPEN mode 1 but there is no lock
to cover entry. DBPUT or DBDELETE to master
requires data set or database be locked. In all
other cases, entry, set, or database can be locked.
ACTION Modify program to apply proper lock or change mode.
---------------------------------------------------------------
-12 MESSAGE Database must be in logon group and account (or
see above)
CAUSE For DBOPEN, when the database has been opened in
access mode 2, the database has to be in the user's
logon group and account.
ACTION Retry call to DBOPEN from group and account
containing database.
---------------------------------------------------------------
-13 MESSAGE Not allowed; must be creator of root file or data
base
CAUSE DBOPEN failed because the caller is not the creator
of the database and no maintenance word is
specified.
ACTION Supply the correct maintenance word and retry call
to DBOPEN.
---------------------------------------------------------------
--------------------------------------------------------------
-14 MESSAGE Illegal intrinsic in current access mode
CAUSE DBPUT and DBDELETE cannot be used with DBOPEN mode
2, 5, 6, 7, or 8. DBUPDATE cannot be used with
DBOPEN mode 5, 6, 7, or 8.
ACTION Modify program or notify current user that
operation cannot be performed.
---------------------------------------------------------------
-15 MESSAGE Setup for RDBA failed
CAUSE DBOPEN will issue a DSLINE command and a REMOTE
HELLO on behalf of the user if a DBA file is being
used for RDBA. One of these commands failed.
ACTION Check your DBA file to make sure the DSLINE and
REMOTE HELLO commands are correct.
---------------------------------------------------------------
-21 MESSAGE Bad password (or see below)
CAUSE For DBOPEN, user class granted does not permit
access to any data in database. This is usually
due to an incorrect or null password or maintenance
word.
ACTION Supply correct password and/or maintenance word.
---------------------------------------------------------------
-21 MESSAGE Bad data set reference (or see below)
CAUSE For DBINFO (modes 104, 201, 202, 301, and 302),
DBCLOSE, DBFIND, DBGET, DBUPDATE, DBPUT, DBDELETE,
when data set reference is:
* Numeric but out of range of the number of
data sets in database
* An erroneous data set name
* A reference to data set which is
inaccessible to user class established when
database opened
For DBFIND, this error is also returned if
referenced data set is a master. Erroneous data
set name may arise when a terminating semicolon or
blank is omitted.
ACTION Check application program's procedure call.
Correct error in call.
---------------------------------------------------------------
-21 MESSAGE Bad data item reference (or see above)
CAUSE For DBINFO (modes 101, 102, and 204), data item
reference is:
* Numeric but out of range of the number of
data items in database
* An erroneous data item name
* A reference to data item which is
inaccessible to user class established when
database opened.
An erroneous data item name may arise when a
terminating semicolon or blank is omitted.
ACTION Check application program's procedure call.
Correct error in call.
---------------------------------------------------------------
-22 MESSAGE Maintenance word required
CAUSE For DBOPEN, maintenance word is required for
non-creator to access the database.
ACTION Supply the correct maintenance word.
---------------------------------------------------------------
-23 MESSAGE Data set not writable
CAUSE For DBPUT and DBDELETE, database has been opened in
DBOPEN mode 1, 3, or 4 and user has read but not
write access to the referenced data set.
ACTION Modify access mode set in procedure call or notify
current user operation cannot be performed.
---------------------------------------------------------------
-24 MESSAGE Operation not allowed on automatic master data
set
CAUSE For DBPUT, the referenced data set is an automatic
master.
ACTION Modify data set name in call or in data set type in
schema.
---------------------------------------------------------------
-30 MESSAGE ILR enabled and bad access
CAUSE The database has been ported from MPE V with ILR
enabled. The only allowable access to the database
is DBOPEN, mode 1-8, or DBUTIL to disable ILR.
ACTION Open the database with mode 1-8 or disable ILR.
---------------------------------------------------------------
-31 MESSAGE Bad mode
CAUSE This error occurs in all procedures when the mode
parameter is invalid. For DBGET, mode is 7 or 8
and referenced data set is a detail, or mode is 5
or 6 and referenced data set is a detail without
search items.
ACTION Correct mode in procedure call.
---------------------------------------------------------------
-32 MESSAGE Unobtainable mode
CAUSE For DBOPEN, root file cannot be FOPENed with access
options (AOPTIONS) required for the specified mode.
Second element of calling program's status area is
required AOPTIONS, and third element is the
AOPTIONS granted to DBOPEN by MPE/iX file system.
This error usually occurs either due to concurrent
database access by other users or due to MPE/iX
account or group security provisions.
ACTION See the MPE/iX Intrinsics Manual (32650-90028) for
meaning of AOPTIONS values.
Action depends on program's design. Normally
notify user that requested access mode is not
available.
---------------------------------------------------------------
-33 MESSAGE Mode 7 diagnostics not allowed
CAUSE For DBGET, mode 7 is not appropriate for
diagnostics.
ACTION Use a different mode for DBGET when diagnostic item
list is in effect.
---------------------------------------------------------------
-51 MESSAGE Bad list length
CAUSE For DBGET, DBUPDATE, and DBPUT, the list is too
long. This may occur if list is not terminated
with a semicolon or blank. It may also occur for
otherwise legitimate lists which are too long for
TurboIMAGE/XL's work area.
It will never occur for numeric lists.
ACTION Shorter list array contents. If necessary, change
to numeric list.
---------------------------------------------------------------
-52 MESSAGE Bad list or bad item
CAUSE For DBGET, DBUPDATE, or DBPUT, the list parameter
is invalid. list either has a bad format or
contains a data item reference which:
* Is out of range of the number of data items
in the database.
* References an inaccessible data item.
* Duplicates another reference in the list.
For DBFIND, the item parameter contains data item
reference which either:
* Is out of range of the number of data items
in the database.
* Is not a search item for referenced data
set.
ACTION Check procedure call. Correct error in call or
parameter.
---------------------------------------------------------------
-53 MESSAGE Missing search or sort item
CAUSE For DBPUT, a search or sort item of referenced data
set is not included in list parameter.
ACTION Check procedure call. Correct error in call or
parameter.
---------------------------------------------------------------
-60 MESSAGE Illegal file equation on root file
CAUSE When using a :FILE command with the database name
or a database-access file name, only the file
designators and DEV= parameters are allowed.
ACTION Reenter :FILE command without illegal parameters.
---------------------------------------------------------------
-80 MESSAGE Output Deferred not allowed with ILR enabled
CAUSE DBCONTROL (mode 1) was used to request deferred
output, but deferred output cannot be used when ILR
is enabled. Output deferred is not initiated.
ACTION Do not use deferred output; or run DBUTIL and
disable ILR.
---------------------------------------------------------------
-81 MESSAGE Output Deferred not allowed with ROLLBACK enabled
CAUSE DBCONTROL (mode 1) was used to request deferred
output, but deferred output cannot be used when
ROLLBACK is enabled. Output deferred is not
initiated.
ACTION Do not use deferred output; or run DBUTIL and
disable ROLLBACK.
---------------------------------------------------------------
-90 MESSAGE Root file bad: unrecognized state: %octal
integer
CAUSE For DBOPEN, this error is returned if the root file
is in an unrecognized state. The octal integer
represents an ASCII error code.
ACTION Restore old copy of the root file for the database.
---------------------------------------------------------------
-91 MESSAGE Bad root modification level
CAUSE For DBOPEN, the software version of the DBOPEN
procedure is incompatible with version of Schema
Processor which created root file.
ACTION Check with system manager that you have correct
TurboIMAGE/XL software. If necessary ask HP
support personnel about conversion.
---------------------------------------------------------------
-92 MESSAGE Data base not created
CAUSE For DBOPEN, the referenced database has not yet
been created and initialized by the DBUTIL program
(in CREATE mode).
ACTION Run DBUTIL to create database. Try application
program again.
---------------------------------------------------------------
-94 MESSAGE Data base bad - Output deferred; may not be
accessed in mode nn
CAUSE For DBOPEN, referenced database was damaged while
being modified in output deferred mode.
ACTION Either DBLOAD from backup tape; or DBUNLOAD to
ERASE data and then DBLOAD.
---------------------------------------------------------------
-95 MESSAGE Data base bad - Creation was in process (create
again)
CAUSE For DBOPEN, database was damaged by a file system
failure, system failure, or TurboIMAGE/XL abort
while DBUTIL CREATE command was creating the
database.
ACTION Because database was not created, run DBUTIL CREATE
command to create the database.
---------------------------------------------------------------
-96 MESSAGE Data base bad - Erase was in process (erase
again)
CAUSE For DBOPEN, database was damaged by a file system
failure, system failure, or TurboIMAGE/XL abort
while DBUTIL ERASE command was erasing the
database.
ACTION Because data was not erased, run DBUTIL ERASE
command to erase the data from the database.
---------------------------------------------------------------
-97 MESSAGE Data base bad - ILR enable in process (enable
again)
CAUSE DBOPEN attempted to open a database but prior
disable of ILR was not complete.
ACTION Run DBUTIL with DNABLE command to enable ILR.
---------------------------------------------------------------
-98 MESSAGE Data base bad - ILR disable in process (disable
again)
CAUSE DBOPEN attempted to open a database, but prior
disable of ILR was not complete.
ACTION Run DBUTIL with DISABLE command to disable ILR.
---------------------------------------------------------------
NOTE Return statuses 100 through 107 are communication errors. For 100
through 102, the third element of calling program's status area is
the MPE/IX failure code returned by DSCHECK intrinsics.
---------------------------------------------------------------
-100 MESSAGE DSOPEN failure
CAUSE While executing a DBOPEN, TurboIMAGE/XL has
encountered a hardware failure trying to obtain a
communications line.
ACTION Try opening the database again. If error persists,
contact your HP Support Representative.
---------------------------------------------------------------
-101 MESSAGE DSCLOSE failure
CAUSE This is an exceptional error returned by DBOPEN or
DBCLOSE. It indicates a hardware or system software
failure.
ACTION Notify system manager of problem.
---------------------------------------------------------------
-102 MESSAGE DSWRITE failure
CAUSE A line failure has occurred while attempting an
operation on a remote database. May be returned by
DBOPEN, DBFIND, DBGET, DBPUT, DBUPDATE, DBDELETE,
DBLOCK, DBUNLOCK, DBINFO, or DBCLOSE.
ACTION Try calling the procedure again. If error
persists, notify system manager.
---------------------------------------------------------------
-103 MESSAGE Remote 3000 stack too small
CAUSE Command Interpreter on remote HP 3000 cannot obtain
stack space necessary to execute a DBOPEN or
DBLOCK.
ACTION Ask system manager of remote system to increase
available stack size.
---------------------------------------------------------------
-104 MESSAGE Remote 3000 does not support TurboIMAGE/XL
CAUSE This is an exceptional error and is returned by
DBOPEN on the remote system.
ACTION Notify system manager of problem.
---------------------------------------------------------------
-105 MESSAGE Remote 3000 cannot create TurboIMAGE control
block.
CAUSE This is an exceptional error and is returned by
DBOPEN on the remote system.
ACTION Notify system manager of problem.
---------------------------------------------------------------
-106 MESSAGE Remote 3000 data inconsistent
CAUSE This is an exceptional error returned by same
intrinsics as 102 (see message listed earlier in
this chapter). It indicates a hardware or system
software failure.
ACTION Notify system manager of problem.
---------------------------------------------------------------
-107 MESSAGE NS 3000 or DS 3000 system error.
CAUSE This is an exceptional error returned by same
intrinsics as 102 (see above). It indicates a
hardware or system software failure.
ACTION Notify system manager of problem.
---------------------------------------------------------------
-108 MESSAGE HPUNLOADCMPROCEDURE call failed.
CAUSE This is an internal error encountered during
switching to Compatibility Mode.
ACTION Notify HP Support Representative.
---------------------------------------------------------------
-110 MESSAGE MPE OPENLOG intrinsic failure
CAUSE OPENLOG returned error number nn to DBOPEN. This
error may occur following a call to DBOPEN when a
database is enabled for logging. Refer to MPE/iX
Intrinsics Manual (32650-90028) for listing of
second values of status array and error messages.
ACTION Notify system manager or HP Support Representative.
---------------------------------------------------------------
-111 MESSAGE MPE WRITELOG intrinsic failure
CAUSE When a database is enabled for logging, this error
may be returned by DBOPEN, DBCLOSE, DBPUT,
DBUPDATE, DBDELETE, DBMEMO, DBBEGIN, DBEND.
ACTION Notify database administrator.
---------------------------------------------------------------
-112 MESSAGE MPE CLOSELOG intrinsic failure
CAUSE When a database is enabled for logging, this error
may be returned by DBCLOSE. Or CLOSELOG returned
error number nn to DBCLOSE.
ACTION Notify database administrator.
---------------------------------------------------------------
-113 MESSAGE FLUSHLOG returned error number nn to DBEND
CAUSE User called DBEND in mode 2 to write the logging
buffer to disk, but the MPE/iX logging facility
returned an error.
ACTION Notify your database administrator.
---------------------------------------------------------------
-114 MESSAGE ROLLBACK without logging
CAUSE DBOPEN has detected that ROLLBACK is enabled but
logging is not.
ACTION Notify your database administrator or HP Support
Representative.
---------------------------------------------------------------
-121 MESSAGE Descriptor count error
CAUSE DBLOCK detected an error in the descriptor count
(first element of qualifier array) in locking mode
5 or 6.
ACTION Count must be a positive integer.
---------------------------------------------------------------
-123 MESSAGE Illegal relop in a descriptor
CAUSE DBLOCK encountered a relop field containing
characters other than >=, <=, =_ or _=.
ACTION Check contents of qualifier array.
---------------------------------------------------------------
-124 MESSAGE Descriptor too short. Must be greater than or
equal to 9
CAUSE DBLOCK encountered a lock descriptor less than 9
halfwords long.
ACTION Check contents of qualifier array.
---------------------------------------------------------------
-125 MESSAGE Bad set name/number
CAUSE DBLOCK qualifier array contains an invalid data set
name or number. (Refer to error -21 for rules.)
ACTION Check contents of qualifier array. Be sure names
are delimited by semicolon or space if less than 16
bytes long.
---------------------------------------------------------------
-126 MESSAGE Bad item name/number
CAUSE DBLOCK qualifier array contains an invalid data
item name or number. (Refer to error 21 for
rules.)
ACTION Check contents of qualifier array. Be sure names
are delimited by semicolon or space if less than 16
bytes long.
---------------------------------------------------------------
-127 MESSAGE Attempt to lock using a compound item
CAUSE DBLOCK does not allow compound items in lock
descriptors.
ACTION Modify locking strategy to lock on a non-compound
item.
---------------------------------------------------------------
-128 MESSAGE Value field too short in a descriptor
CAUSE A value field in a DBLOCK lock descriptor must be
at least as long as the data item for which it is
specified.
ACTION Check the length of the value field.
---------------------------------------------------------------
-129 MESSAGE P-type item longer than P28 specified
CAUSE DBLOCK does not allow P-type data items longer than
28 in lock descriptors (27 digits plus sign).
ACTION Modify locking strategy to lock on a different
item.
---------------------------------------------------------------
-130 MESSAGE Illegal digit in a P-type value
CAUSE DBLOCK has encountered a P-type value in a lock
descriptor with an invalid packed decimal digit.
ACTION Check qualifier array contents to determine why
data is invalid.
---------------------------------------------------------------
-131 MESSAGE Lowercase character in type-U value
CAUSE DBLOCK has encountered a lowercase character in a
type-U value specified in a lock descriptor.
ACTION Check qualifier array contents to determine why
data is invalid.
---------------------------------------------------------------
-132 MESSAGE Illegal digit in type Z value
CAUSE Lock descriptor value specified to DBLOCK contains
an invalid zoned decimal digit.
ACTION Check qualifier array contents to determine why
data is invalid.
---------------------------------------------------------------
-133 MESSAGE Illegal sign in type Z value
CAUSE Lock descriptor value specified to DBLOCK contains
an invalid zoned decimal sign.
ACTION Check qualifier array contents to determine why
data is invalid.
---------------------------------------------------------------