HP 3000 Manuals HP 3000 Manuals
Library Procedure Error Messages (contd.)
Library Procedure Calling Errors (contd.)
-134 MESSAGE Two descriptors conflict
CAUSE 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
CAUSE 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
CAUSE 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.
---------------------------------------------------------------
-151 MESSAGE Text length greater than 512 bytes
CAUSE Returned by DBBEGIN, DBEND, or DBMEMO.
ACTION Modify program.
---------------------------------------------------------------
-152 MESSAGE DBCLOSE called while a transaction is in process;
DBBEGIN called while a transaction is in process
CAUSE A transaction is in process.
ACTION Call DBEND before DBCLOSE. Call DBEND before the
next DBBEGIN.
---------------------------------------------------------------
-153 MESSAGE DBEND called while no transaction in progress
CAUSE No DBBEGIN precedes the call to DBEND.
ACTION Call DBBEGIN before DBEND.
---------------------------------------------------------------
-160 MESSAGE ILR log file name conflict
CAUSE There is a user file with the same name as the ILR
log file name.
ACTION Replace the user file with a valid MPE/iX ILR log
file.
---------------------------------------------------------------
-161 MESSAGE Cannot check for an ILR log file conflict: file
system error nn
CAUSE 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
CAUSE 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
CAUSE The logical beginning of an MPE/iX transaction
failed. nn is the error number returned.
ACTION Notify HP Support Representative.
---------------------------------------------------------------
-168 MESSAGE Cannot attach n to MPE XL XM: File system error
nn
CAUSE Data set n could not be "attached" to the MPE/iX
transaction recovery mechanism. MPE/iX intrinsic
FILEINFO or FLABELINFO failed.
ACTION Notify HP Support Representative.
---------------------------------------------------------------
-169 MESSAGE Invalid mode for XM attach options
CAUSE An internal error has occurred.
ACTION Notify HP Support Representative.
---------------------------------------------------------------
-170 MESSAGE Cannot open ILR log file: file system error nn
CAUSE 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
CAUSE 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
CAUSE 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
CAUSE 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
CAUSE The data set n could not be "attached" to the
transaction recovery mechanism. nn is the MPE/iX
error number returned.
ACTION Notify HP Support Representative.
---------------------------------------------------------------
-176 MESSAGE Cannot detach n from MPE XL XM: XM error nn.
CAUSE The data set n could not be "detached" from the
transaction recovery mechanism. nn is the MPE/iX
error number returned.
ACTION Notify HP Support Representative.
---------------------------------------------------------------
-177 MESSAGE MPE log file is not in the same volume set as the
database.
CAUSE MPE/IX transaction recovery requires that the user
log file must reside in the same volume set as the
database.
ACTION Build the MPE/iX user log file in same volume set
as database.
NOTE: Because all files in a group are in same
volume set, :LISTGROUP indicates the volume set
where a database resides.
---------------------------------------------------------------
-178 MESSAGE Cannot detach n from MPE XL XM: file system error
nn
CAUSE The data set n could not be "detached" from the
MPE/iX transaction recovery mechanism. The MPE/iX
intrinsic FLABELINFO failed. nn is the file system
error number returned.
ACTION Notify HP Support Representative.
---------------------------------------------------------------
-179 MESSAGE Cannot begin MPE XL transaction for attach: XM
error nn
CAUSE Before "attaching" the entire database to the
MPE/iX transaction recovery mechanism, a logical
beginning of a transaction is specified. The
beginning of the transaction failed. nn is the
error number returned.
ACTION Notify HP Support Representative.
---------------------------------------------------------------
-180 MESSAGE ILR log invalid - internal file name does not
match root file
CAUSE DBUTIL DISABLE command or call to DBOPEN attempted
to open ILR log file, but file names inconsistent.
Unlikely to occur unless disk corrupted, or
TurboIMAGE/XL root file or ILR log file altered by
privileged mode user.
ACTION Use DBRESTOR to restore database.
---------------------------------------------------------------
-181 MESSAGE ILR log file invalid - internal group name does
not match root file
CAUSE DBUTIL DISABLE command or call to DBOPEN attempted
to open ILR log file, but group names do not match.
(See error -180 for possible cause.)
ACTION Use DBRESTOR to restore database.
---------------------------------------------------------------
-182 MESSAGE ILR log invalid - internal account name does not
match root file
CAUSE DBUTIL DISABLE command or call to DBOPEN attempted
to open ILR log file, but account names do not
match. (See error -180 for possible cause.)
ACTION Use DBRESTOR to restore database.
---------------------------------------------------------------
-183 MESSAGE ILR log invalid - internal creation date does not
match root file
CAUSE DBUTIL DISABLE command or call to DBOPEN was unable
to open ILR log file because its creation date was
not the same as the creation date of the
TurboIMAGE/XL root file. Could be caused by
storing the database followed by a partial restore
with MPE/iX :RESTORE that excluded either the root
file or the ILR log file. If there was an
intervening ENABLE or DISABLE, the creation dates
will not match and only a partial DBSTORE/DBRESTOR
occurred.
ACTION To avoid this problem always store database with
DBSTORE and restore with DBRESTOR. Using these
utilities assures that root file and ILR log file
are consistent.
---------------------------------------------------------------
-184 MESSAGE ILR log invalid - internal last access data
access data does not match root file
CAUSE DBUTIL DISABLE command or call to DBOPEN was unable
to open ILR log file because its last access date
does not match the date in the root file. Possibly
caused by a store and then a partial restore (using
MPE/iX :RESTORE) of database.
ACTION Always store database with DBSTORE and restore with
DBRESTOR to assure consistent dates in root file
and log file.
---------------------------------------------------------------
-187 MESSAGE ILR is already enabled for this database
CAUSE DBUTIL ENABLE command attempted to enable a
database for ILR when ILR was already enabled.
ACTION Warning only.
---------------------------------------------------------------
-188 MESSAGE ILR is already disabled for this database
CAUSE DBUTIL DISABLE command attempted to disable a
database for ILR when ILR was already disabled.
ACTION Warning only.
---------------------------------------------------------------
-189 MESSAGE Cannot begin MPE XL transaction for detach: XM
error nn
CAUSE Before "detaching" the entire database from the
MPE/iX transaction recovery mechanism, a logical
ending of a transaction is specified. The ending
of the transaction failed. nn is the error number
returned.
ACTION Notify HP Support Representative.
---------------------------------------------------------------
-190 MESSAGE Bad DBS
CAUSE The Database System Control Block has been
corrupted.
ACTION Notify HP Support Representative.
---------------------------------------------------------------
-191 MESSAGE The DBS is full
CAUSE DBOPEN has detected that there is no more room in
the DBS to hold any more DBG entries.
ACTION Notify HP Support Representative.
---------------------------------------------------------------
-192 MESSAGE Invalid DBU
CAUSE The database user local control block has been
corrupted.
ACTION Notify HP Support Representative.
---------------------------------------------------------------
-193 MESSAGE DBU control block is full
CAUSE The database user local control block is full.
ACTION Notify HP Support Representative.
---------------------------------------------------------------
-194 MESSAGE Invalid DBB
CAUSE The database buffer control block has been
corrupted.
ACTION Notify HP Support Representative.
---------------------------------------------------------------
-195 MESSAGE Invalid DBG
CAUSE The database global control block has been
corrupted.
ACTION Notify HP Support Representative.
---------------------------------------------------------------
-196 MESSAGE DBB control block is full
CAUSE The database buffer control block is full.
ACTION Notify HP Support Representative.
---------------------------------------------------------------
-197 MESSAGE DBG control block is full
CAUSE The database global control block is full.
ACTION Notify HP Support Representative.
---------------------------------------------------------------
-198 MESSAGE Total DBOPEN count/user exceeds limit
CAUSE The DBU index table, the DBUX, is full. This table
is used to map the baseid to the user's DBU. The
DBUX holds a maximum of 127 entries.
ACTION Notify HP Support Representative.
---------------------------------------------------------------
-199 MESSAGE Cannot end MPE XL XM transaction: XM error nn
CAUSE The logical ending of an MPE/iX transaction failed.
nn is the error number returned. Any writes done
on behalf of the intrinsic will be rolled out.
NOTE: This error is only possible from DBPUT,
DBDELETE, or DBUPDATE.
ACTION Notify system manager.
---------------------------------------------------------------
-200 MESSAGE Data base language not system supported
CAUSE DBOPEN attempted to open the database and found
that the language of the database is not currently
configured. The collating sequence of the language
is unavailable; DBOPEN cannot open the database.
ACTION Notify system manager.
---------------------------------------------------------------
-201 MESSAGE Native Language Support not installed
CAUSE NLS/3000 internal structures have not been built at
system start-up. The collating sequence table of
the language of the database is unavailable; DBOPEN
cannot open the database.
ACTION Notify system manager.
---------------------------------------------------------------
-202 MESSAGE MPE Native Language Support error nn returned by
NLINFO
CAUSE The error number given was returned by NLS/3000 on
a NLINFO call in DBOPEN.
ACTION Notify system manager.
---------------------------------------------------------------
-206 MESSAGE Data base exceeds limits
CAUSE DBOPEN has detected that the remote TurboIMAGE/XL
database exceeds the local IMAGE limitations.
Remote database access cannot be completed. A
TurboIMAGE/XL database can only be accessed from a
local node (which has IMAGE) if and only if the
remote database has not exceeded the IMAGE/3000
data set and data item limitations.
ACTION Access the remote TurboIMAGE/XL database from
another local node which also supports
TurboIMAGE/XL.
---------------------------------------------------------------
-208 MESSAGE MPE error nn returned by FLABELINFO for MPE XL XM
CAUSE The MPE/iX file system error nn was returned by the
intrinsic FLABELINFO.
ACTION Notify HP Support Representative.
---------------------------------------------------------------
-209 MESSAGE Invalid mode for MPE XL XM DETACH
CAUSE An internal error has occurred.
ACTION Notify HP Support Representative.
---------------------------------------------------------------
-210 MESSAGE MPE error nn on log file name
CAUSE MPE/iX file system error nn was returned while
trying to obtain the user log file name.
ACTION Notify HP Support Representative.
---------------------------------------------------------------
-3nn MESSAGE Internal error returned
CAUSE Internal error nn occurred while in an intrinsic.
ACTION Notify HP Support Representative.
---------------------------------------------------------------
-1000 MESSAGE Switch failure, INFO nn, SUBSYS nn
CAUSE The switch to Native Mode failed. SUBSYS nn is the
subsystem that failed. INFO nn is the error number
returned from that subsystem.
ACTION Notify HP Support Representative.
---------------------------------------------------------------
-1001 MESSAGE Switch to CM failed on CX'PCBXIMAGE
CAUSE Internal error. This error is returned when DBOPEN
calls CM CX'PCBXIMAGE and encounters a switch to CM
failure.
ACTION Notify HP Support Representative.
---------------------------------------------------------------
-1002 MESSAGE HPLOADCMPROCEDURE failed on CX'PCBXIMAGE
CAUSE Internal error. This error is returned when DBOPEN
calls HPLOADCMPROCEDURE for CM CX'PCBXIMAGE and
fails.
ACTION Notify HP Support Representative.
---------------------------------------------------------------
-1003 MESSAGE Switch to NM failed on DBxxx, INFO nn SUBSYS nn
CAUSE The switch to Native Mode failed. DBxxx is the
TurboIMAGE/XL intrinsic. SUBSYS nn is the
subsystem that failed. INFO nn is the error number
returned from that subsystem.
ACTION Notify HP Support Representative.
---------------------------------------------------------------