HP 3000 Manuals HP 3000 Manuals
Library Procedure Error Messages (contd)
Library Procedure Calling Errors (contd)
-95 MESSAGE Database bad - Creation was in process (create
again)
MEANING 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 Database bad - Erase was in process (erase again)
MEANING 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 Database bad - ILR enable in process (enable
again)
MEANING DBOPEN attempted to open a database but prior
disable of ILR was not complete.
ACTION Run DBUTIL with ENABLE command to enable ILR.
---------------------------------------------------------------
-98 MESSAGE Database bad - ILR disable in process (disable
again)
MEANING DBOPEN attempted to open a database, but prior
disable of ILR was not complete.
ACTION Run DBUTIL with DISABLE command to disable ILR.
---------------------------------------------------------------
Return statuses -100 through -107 are communication errors. For -100
through -102, the third element of the calling program's status area is
the MPE failure code returned by DSCHECK intrinsics.
-100 MESSAGE DSOPEN failure
MEANING 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 customer engineer.
---------------------------------------------------------------
-101 MESSAGE DSCLOSE failure
MEANING 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
MEANING A line failure has occurred while attempting an
operation on a remote database. Can 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
MEANING 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
MEANING 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.
MEANING 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
MEANING This is an exceptional error returned by same
intrinsics as -102 (see message listed earlier in
this appendix). It indicates a hardware or system
software failure.
ACTION Notify system manager of problem.
---------------------------------------------------------------
-107 MESSAGE NS 3000 or DS 3000 system error.
MEANING 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.
MEANING This is an internal error encountered during
switching to Compatibility Mode.
ACTION Notify HP support personnel.
---------------------------------------------------------------
-110 MESSAGE MPE OPENLOG intrinsic failure
MEANING OPENLOG returned error number nn to DBOPEN. This
error can occur following a call to DBOPEN when a
database is enabled for logging. Refer to MPE/iX
Intrinsics Manual for listing of second values of
status array and error messages.
ACTION Notify system manager or HP support personnel.
---------------------------------------------------------------
-111 MESSAGE MPE WRITELOG intrinsic failure
MEANING When a database is enabled for logging, this error
can be returned by DBOPEN, DBCLOSE, DBPUT,
DBUPDATE, DBDELETE, DBMEMO, DBBEGIN, DBEND,
DBXBEGIN, DBXEND, DBXUNDO.
ACTION Notify database administrator.
---------------------------------------------------------------
-112 MESSAGE MPE CLOSELOG intrinsic failure
MEANING When a database is enabled for logging, this error
can be returned by DBCLOSE. Or CLOSELOG returned
error number nn to DBCLOSE.
ACTION Consult MPE error message documentation. Or notify
database administrator.
---------------------------------------------------------------
-113 MESSAGE FLUSHLOG returned error number nn to DBEND
MEANING User called DBEND in mode 2 to write the logging
buffer to disk, but the MPE logging facility
returned an error.
ACTION Consult MPE error message documentation.
---------------------------------------------------------------
-114 MESSAGE ROLLBACK without logging
MEANING DBOPEN has detected that ROLLBACK is enabled but
logging is not.
ACTION Notify your database administrator or HP support
personnel.
---------------------------------------------------------------
-121 MESSAGE Descriptor count error
MEANING 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
MEANING 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
MEANING DBLOCK encountered a lock descriptor less than 9
halfwords long.
ACTION Check contents of qualifier array.
---------------------------------------------------------------
-125 MESSAGE Bad set name/number
MEANING 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
MEANING 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
MEANING 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
MEANING 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
MEANING 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
MEANING 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
MEANING 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
MEANING 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
MEANING Lock descriptor value specified to DBLOCK contains
an invalid zoned decimal sign.
ACTION Check qualifier array contents to determine why
data is invalid.
---------------------------------------------------------------
-134 MESSAGE Two descriptors conflict
MEANING DBLOCK has detected two lock descriptors in the
same call that lock the same or part of the same
database entity. (For example, lock on set and
database in same request.)
ACTION Check qualifier array contents for conflicting lock
descriptors.
---------------------------------------------------------------
-135 MESSAGE Second lock without CAP=MR
MEANING A second call to DBLOCK has been made without an
intervening DBUNLOCK call and program does not have
MR capability.
ACTION Read discussion of multiple calls to DBLOCK in
chapter 4 of this manual if you plan to use CAP=MR.
---------------------------------------------------------------
-136 MESSAGE Descriptor list exceeds 4094 bytes
MEANING DBLOCK allows a maximum length of 4094 bytes for
lock descriptor lists (qualifier array).
ACTION Change qualifier array contents so lock descriptor
list is shorter.
---------------------------------------------------------------
-139 MESSAGE Invalid number of base IDs.
MEANING The number of base IDs involved in the multiple
database transaction is greater than 15.
ACTION Modify your application program so that not more
than 15 databases are involved in a multiple
database transaction.
---------------------------------------------------------------
-140 MESSAGE Bad base ID list.
MEANING The base IDs are not correctly formatted for a
multiple database transaction.
ACTION Modify your application program so that the base ID
list is correctly formatted. Refer to the
discussion of DBBEGIN in chapter 5 for more
information.
---------------------------------------------------------------
-141 MESSAGE All MDBX databases must be on same system.
MEANING An attempt was made to begin a multiple database
transaction (MDBX) on remote databases when all
databases were not located on the same system
(node).
ACTION Modify your application program to only perform
multiple database transactions on databases which
are located on the same system.
---------------------------------------------------------------
-142 MESSAGE All MDBX databases must log to the same log file.
MEANING All databases involved in a multiple database
transaction (MDBX) must have synchronized logging
facilities.
ACTION Ask your database administrator or application
programmer to synchronize the logging facilities.
---------------------------------------------------------------
-143 MESSAGE Logging must be enabled or disabled for all MDBX
databases.
MEANING All databases involved in a multiple database
transaction (MDBX) must have synchronized logging
facilities.
ACTION Ask your database administrator or application
programmer to synchronize the logging facilities.
---------------------------------------------------------------
-144 MESSAGE MUSTRECOVER must be enabled or disabled for all
MDBX databases.' ' \MEANING\All databases
involved in a multiple database transaction (MDBX)
must have synchronized logging facilities.
ACTION Ask your database administrator or application
programmer to synchronize the logging facilities.
---------------------------------------------------------------
-145 MESSAGE Roll-back recovery must be enabled or disabled
for all MDBX databases.
MEANING All databases involved in a multiple database
transaction (MDBX) must have synchronized logging
facilities.
ACTION Ask your database administrator or application
programmer to synchronize the logging facilities.
---------------------------------------------------------------
-146 MESSAGE Invalid transaction ID.
MEANING The transaction ID used in a call to DBBEGIN and in
the call to its corresponding DBEND do not match.
ACTION Contact your database administrator or application
programmer.
---------------------------------------------------------------
-147 MESSAGE Mode doesn't match DBBEGIN mode.
MEANING The DBBEGIN mode and its corresponding DBEND mode
must match.
ACTION Contact your database administrator or application
programmer.
---------------------------------------------------------------
-148 MESSAGE Base ID list doesn't match DBBEGIN base ID list.
MEANING The base ID list passed to DBBEGIN for a multiple
database transaction does not match the DBEND base
ID list for the same transaction.
ACTION Contact your database administrator or application
programmer.
---------------------------------------------------------------
-151 MESSAGE Text length greater than 512 bytes
MEANING Text provided to DBBEGIN, DBEND, DBMEMO, DBXBEGIN,
DBXEND, DBXUNDO is too long.
ACTION Modify program.
---------------------------------------------------------------
-152 MESSAGE DBCLOSE called while a transaction is in process;
DBBEGIN called while a transaction is in process;
DBXBEGIN called while a transaction is in progress
MEANING A transaction is in process.
ACTION Call DBEND before DBCLOSE. Call DBEND before the
next DBBEGIN. Call DBXEND before the next DBXBEGIN.
---------------------------------------------------------------
-153 MESSAGE DBEND called while no transaction in progress
MEANING No DBBEGIN precedes the call to DBEND.
ACTION Call DBBEGIN before DBEND.
---------------------------------------------------------------
-160 MESSAGE ILR log file name conflict
MEANING A user file has the same name as the ILR log file
name.
ACTION Replace the user file with a valid MPE ILR log
file.
---------------------------------------------------------------
-161 MESSAGE Cannot check for an ILR log file conflict: file
system error nn
MEANING DBUTIL DISABLE command or call to DBOPEN failed to
open ILR log file.
ACTION Check file system error number.
---------------------------------------------------------------
-166 MESSAGE Cannot purge ILR log file: file system error nn
MEANING DBUTIL DISABLE, PURGE, or ERASE command could not
purge an ILR log file because of a file system
error.
ACTION Check file system error number.
---------------------------------------------------------------
-167 MESSAGE Cannot begin MPE XL XM transaction: XM error nn
MEANING The logical beginning of an MPE transaction failed.
nn represents the error number returned.
ACTION Notify HP support personnel.
---------------------------------------------------------------
-168 MESSAGE Cannot attach n to MPE XL XM: file system error
nn
MEANING Data set n could not be attached to the MPE
transaction recovery mechanism. MPE intrinsic
FILEINFO or FLABELINFO failed.
ACTION Notify HP support personnel.
---------------------------------------------------------------
-169 MESSAGE Invalid mode for XM attach options
MEANING An internal error has occurred.
ACTION Notify HP support personnel.
---------------------------------------------------------------
-170 MESSAGE Cannot open ILR log file: file system error nn
MEANING DBUTIL DISABLE command or call to DBOPEN was not
able to open ILR log file due to file system error.
ACTION Check file system error number.
---------------------------------------------------------------
-172 MESSAGE Cannot read ILR log file: file system error nn
MEANING DBUTIL DISABLE command or call to DBOPEN was not
able to read ILR log file due to file system error.
ACTION Check file system error number.
---------------------------------------------------------------
-173 MESSAGE Unable to obtain write access
MEANING DBOPEN has determined that it is necessary to
perform ILR. The current user does not have write
access to the database.
ACTION Have the database opened by a user with write
access.
---------------------------------------------------------------
-174 MESSAGE Bad mode for ILR
MEANING DBOPEN has determined that it is necessary to
perform ILR. The database must be opened for
writing.
ACTION Open the database in mode 1-4.
---------------------------------------------------------------
-175 MESSAGE Cannot attach n to MPE XL XM: XM error nn
MEANING The data set n could not be attached to the
transaction recovery mechanism. nn is the MPE
error number returned.
ACTION Notify HP support personnel.
---------------------------------------------------------------