HP 3000 Manuals HP 3000 Manuals
Library Procedure Error Messages (contd)
Library Procedure Exceptional Conditions
---------------------------------------------------------------
10 MESSAGE Beginning of file
CAUSE DBGET has encountered beginning of file during a
backward serial read. (There are no entries before
the one previously accessed.)
ACTION Appropriate action depends on program design.
---------------------------------------------------------------
11 MESSAGE End of file
CAUSE DBGET has encountered the end of file during a
forward serial read. (There are no entries beyond
the most recently accessed one.)
ACTION Appropriate action depends on program design.
---------------------------------------------------------------
12 MESSAGE Directed beginning of file
CAUSE DBGET has been called for a directed read with a
record number less than 1.
ACTION Appropriate action depends on program design.
---------------------------------------------------------------
13 MESSAGE Directed end of file
CAUSE DBGET has been called for a directed read with a
record number greater than the capacity of data
set.
ACTION Appropriate action depends on program design.
---------------------------------------------------------------
14 MESSAGE Beginning of chain
CAUSE DBGET has encountered end of chain during a
backward chained read.
ACTION Appropriate action depends on program design.
---------------------------------------------------------------
--------------------------------------------------------------
15 MESSAGE End of chain
CAUSE DBGET has encountered end of chain during a forward
chained read.
ACTION Appropriate action depends on program design.
---------------------------------------------------------------
16 MESSAGE Data set full
CAUSE DBPUT has discovered that data set is full.
ACTION Restructure database with larger capacity for this
data set.
---------------------------------------------------------------
17 MESSAGE No master entry ( or see below)
CAUSE DBFIND is unable to locate master data set entry
(chain head) for specified detail data set's search
item value.
ACTION Appropriate action depends on program design.
---------------------------------------------------------------
17 MESSAGE No entry (or see above)
CAUSE DBGET has been called to reread an entry, but no
"current record" has been established or a call to
DBFIND has set the current record to 0. DBGET is
unable to locate master data set entry with
specified key item value.
DBGET has discovered that selected record is empty
(does not contain an entry).
DBUPDATE or DBDELETE was called when the "current
record" was not established or was empty.
ACTION Appropriate action depends on program design.
---------------------------------------------------------------
18 MESSAGE Broken chain
CAUSE For DBGET with mode parameter equal to 5 (forward
chained read), the "next entry" on current chain
(as designated by internally maintained forward
pointer for data set) contains backward pointer
which does not point to most recently accessed
entry (or zero for first member of a chain).
For DBGET with mode parameter equal to 6 (backward
chained read), the "next entry" on current chain in
a backward direction (as designated by internally
maintained backward pointer for data set) contains
a forward pointer which does not point to most
recently accessed entry (or zero for last entry in
a chain).
This error can occur in DBOPEN access modes 1, 5,
and 6 because another user can make database
modifications concurrent with this user's accesses.
When this error occurs, no data is moved to user's
stack, although internal pointers maintained by
TurboIMAGE/XL in the DBB are changed to new
"offending" entry. (It becomes the current entry.)
Note that this error check does not detect all
structural changes. DBGET (mode 5 or 6) makes
check only when preceding call on data set was
successful DBFIND or DBGET.
ACTION Begin reading chain again from first or last entry.
---------------------------------------------------------------
20 MESSAGE Data base locked or contains locks
CAUSE DBLOCK Mode 2: The database cannot be locked.
Refer to value of status element three: if 0,
database already locked; if 1, database contains
locked sets or entries. Mode 4, 6: The lock
cannot be granted because the whole database is
already locked.
ACTION Appropriate action depends on program design.
---------------------------------------------------------------
22 MESSAGE Data set locked by another process
CAUSE DBLOCK has detected that the data set is locked by
another process or this process through a different
access path. Returned in DBLOCK modes 4 and 6
only.
ACTION Appropriate action depends on program design.
---------------------------------------------------------------
23 MESSAGE Entries locked within set
CAUSE DBLOCK has detected that data entries within
requested data set are locked by another process or
this process through a different access path.
Returned in DBLOCK mode 4 only.
ACTION Appropriate action depends on program design.
---------------------------------------------------------------
24 MESSAGE Item conflicts with current locks
CAUSE Lock descriptors passed to DBLOCK specify a data
item that is different than one used to set
existing locks. TurboIMAGE/XL allows no more than
one data item per data set to be used at one time
for locking purposes. Returned in DBLOCK modes 5
and 6 only.
ACTION Appropriate action depends on program design.
---------------------------------------------------------------
25 MESSAGE Entries already locked
CAUSE DBLOCK has detected that data entries requested to
be locked are already locked by another process or
this process through a different access path.
Returned in DBLOCK mode 6 only.
ACTION Appropriate action depends on program design.
---------------------------------------------------------------
41 MESSAGE Critical item
CAUSE DBUPDATE has been asked to change value of search
or sort item.
ACTION Correct call or notify user cannot update item.
---------------------------------------------------------------
42 MESSAGE Read only item
CAUSE DBUPDATE has been asked to change value of a data
item for which the user does not have write access.
ACTION Notify user, cannot update item. Or change
password in program.
---------------------------------------------------------------
43 MESSAGE Duplicate key item value
CAUSE DBPUT has been asked to insert data entry into a
master data set with a key item value which already
exists in data set.
ACTION Appropriate action depends on program design.
---------------------------------------------------------------
44 MESSAGE Can't delete master entry with non-empty detail
chains
CAUSE DBDELETE has been asked to delete master data set
entry which still has one or more non-empty chains.
ACTION Appropriate action depends on program design.
---------------------------------------------------------------
49 MESSAGE Illegal buffer address
CAUSE Calling program's buffer (identified by buffer
parameter) address of DBGET or DBINFO is an
unsupported memory address.
ACTION Correct the buffer parameter with a valid address.
CM user stack, NM user stack, and the NM heap are
valid memory areas in which to create a buffer
parameter.
---------------------------------------------------------------
50 MESSAGE Buffer too small
CAUSE Calling program's buffer (identified by buffer
parameter) is too small to accommodate the amount
of information that DBGET or DBINFO wishes to
return without extending into the parameters area.
This message is returned only if the buffer is the
last item in the user's stack, and will overflow
the stack boundaries.
ACTION Correct procedure call, or change buffer name or
size.
---------------------------------------------------------------
60 MESSAGE Data base access disabled
CAUSE DBOPEN has been called when the database has been
disabled for access.
ACTION Notify database administrator.
---------------------------------------------------------------
61 MESSAGE Data base opened more than 63 times by same
process.
CAUSE DBOPEN has been called when the specified database
has already been opened 63 times by the same
process.
ACTION Correct your program so that DBOPEN does not open
the same database more than 63 times.
---------------------------------------------------------------
62 MESSAGE DBG Control Block is Full
CAUSE Lock area within DBG is full.
ACTION Notify your database administrator.
---------------------------------------------------------------
63 MESSAGE DBG disabled; potential damage; only DBCLOSE
allowed
CAUSE Another process sharing the database has aborted
because of logical inconsistency or internal error
in TurboIMAGE/XL, leaving DBG in potentially
inconsistent state. All user accesses through
existing DBG are disabled (except for DBCLOSE, mode
1). Returned by all intrinsics.
ACTION Issue a DBCLOSE, mode 1.
---------------------------------------------------------------
64 MESSAGE No room for DBG entry in PCBX (MPE/iX portion of
stack)
CAUSE The PCBX is full.
ACTION Try again when system resources are available.
---------------------------------------------------------------
65 MESSAGE Can't grant buffer request
CAUSE DBCONTROL cannot increase the number of buffers as
requested by the user. A current count is
returned.
ACTION Request a smaller number of buffers.
---------------------------------------------------------------
66 MESSAGE DBG pointed to by root file does not match
CAUSE Root file is not compatible with DBG.
ACTION Notify HP Support Representative.
---------------------------------------------------------------
67 MESSAGE DBU disabled; potential damage; only DBCLOSE
allowed
CAUSE The user's control block is in an inconsistent
state.
ACTION Issue a DBCLOSE, mode 1.
---------------------------------------------------------------
68 MESSAGE Bad DBB
CAUSE Another process sharing the database has aborted
because of logical inconsistency or internal error
in TurboIMAGE/XL, leaving DBB in potentially
inconsistent state. All user accesses through
existing DBB are disabled (except for DBCLOSE, mode
1). Returned by all intrinsics.
ACTION Issue a DBCLOSE, mode 1.
---------------------------------------------------------------
69 MESSAGE Bad database
CAUSE AUTODEFER is active, and the database did not close
normally. The database has been corrupted.
ACTION Notify your database administrator.
---------------------------------------------------------------
1nn MESSAGE Missing chain head
CAUSE User has attempted to add detail data entry with a
search item value that does not match any existing
key item value in corresponding manual master data
set. The digits represented by nn identify the
offending path number established by order in which
their search items occur in set part of schema.
ACTION Notify user cannot add entry or add manual master
entry and try again.
---------------------------------------------------------------
2nn MESSAGE Full chain
CAUSE User has attempted to add detail data entry to a
chain which already contains the maximum allowable
(2,147,483,647) entries. The digits represented by
nn identify the offending path number (as described
in 1nn).
ACTION Consult with database manager. May need to delete
some entries from chain or restructure database.
---------------------------------------------------------------
3nn MESSAGE Full master
CAUSE Automatic master data set is full. Therefore, when
the user attempted to add a search item to a detail
data set, the corresponding key value could not be
added to the automatic master data set. The digits
represented by nn identify the offending path
number (as described in 1nn).
ACTION Restructure database, increasing capacity of
automatic master.
---------------------------------------------------------------
944 MESSAGE Warning: Assuming no message catalog
CAUSE No message catalog is available.
ACTION Notify your system administrator.
---------------------------------------------------------------
Others MESSAGE Unrecognized return status: nn
CAUSE Return status could not be recognized.
ACTION Notify HP Support Representative.
---------------------------------------------------------------
Library Procedure Abort Condition Messages in I File
---------------------------------------------------------------
MESSAGE BUFFER SUPPLY CRISIS
CAUSE Internal software inconsistency caused
TurboIMAGE/XL to mismanage its buffer space.
ACTION Notify the system manager and possibly HP Support
Representative. Save FID information if it is
printed. You may need to perform database recovery
procedures.
---------------------------------------------------------------
MESSAGE CRITICAL LABEL READ ERROR ON data set
CAUSE Unable to read label of database file.
ACTION Notify the system manager and possibly HP Support
Representative. Save FID information if it is
printed. You may need to perform database recovery
procedures.
---------------------------------------------------------------
MESSAGE CRITICAL READ ERROR ON data set
CAUSE An MPE/iX file read error encountered while reading
database file.
ACTION Notify the system manager and possibly HP Support
Representative. Save FID information if it is
printed. You may need to perform database recovery
procedures.
---------------------------------------------------------------
MESSAGE ERROR intrinsic name STATUS return status;
DBERROR/DBEXPLAIN FAILED I info S subsys
CAUSE The specified intrinsic encountered an error.
ERROR displays the intrinsic. STATUS is the return
status from the intrinsic. The application called
either DBERROR or DBEXPLAIN. The switch to Native
Mode failed. I is the error number returned by the
subsystem. S is the subsystem that failed.
ACTION Notify HP Support Representative.
---------------------------------------------------------------
MESSAGE ESCAPE FROM TURBOIMAGE/XL; PC: $pcode CODE:
$escape code
CAUSE A hardware or software trap occurred. pcode and
escape code are hex numbers. The first four hex
digits represent the error code; the last four
represent the subsystem number.
ACTION Notify the system manager and HP Support
Representative if necessary. Save the escape code
number.
---------------------------------------------------------------
--------------------------------------------------------------
MESSAGE HPUNLOADCMPROCEDURE FAILED ON intrinsic name INFO
info SUBSYS subsystem
CAUSE A problem was encountered when switching to
Compatibility Mode (CM). INFO is the error returned
by the subsystem. SUBSYS is the subsystem which
failed.
ACTION Notify HP Support Representative.
---------------------------------------------------------------
MESSAGE LABEL WRITE ERROR ON data set
CAUSE Unable to complete the writing of a user label on
database file.
ACTION Notify the system manager and HP Support
Representative if necessary.
---------------------------------------------------------------
MESSAGE LOST FREE SPACE IN data set
CAUSE Internal software inconsistency caused unused
record locations in data set to become lost or
unavailable. File information display is printed
for the data set.
ACTION Notify the system manager and HP Support
Representative if necessary.
---------------------------------------------------------------
MESSAGE NEGATIVE MOVE ATTEMPT: n
CAUSE An internal software inconsistency has been found
while attempting to move data to or from user's
stack.
ACTION Notify the system manager and HP Support
Representative if necessary.
---------------------------------------------------------------
MESSAGE THE intrinsic name parm PARAMETER NOT ALIGNED ON A
16-BIT BOUNDARY
CAUSE The designated parameter, parm, is 8-bit aligned.
ACTION Modify your application so that the parm parameter
is 16-bit (halfword) aligned.
---------------------------------------------------------------
MESSAGE THE USER CANNOT BE IN SPLIT-STACK MODE
CAUSE An application must be running on the user's stack
when calling a TurboIMAGE/XL intrinsic. It is not
permitted to run in split-stack mode. This message
is only applicable if you are running in
Compatibility Mode.
ACTION Modify your Compatibility Mode application so that
it is not running in split-stack mode.
---------------------------------------------------------------
MESSAGE UNABLE TO CLOSE DATA SET
CAUSE Unable to close a database file.
ACTION Modify your application so that the parm parameter
is 16-bit (halfword) aligned.
---------------------------------------------------------------
MESSAGE UNABLE TO OPEN A data set
CAUSE Unable to open database file.
ACTION Modify your application so that the parm parameter
is 16-bit (halfword) aligned.
---------------------------------------------------------------
MESSAGE WRITE ERROR ON data set
CAUSE An MPE/iX file write error found while writing into
database file.
ACTION Modify your application so that the parm parameter
is 16-bit (halfword) aligned.
---------------------------------------------------------------
MESSAGE WRONG NUMBER OF PARAMETERS OR BAD ADDRESS FOR PARAM
#n
CAUSE An address referenced by one of the parameters is
not within the user's stack area in memory. The n
is a positional number of the parameter in the
procedure's calling sequence. The first parameter
is #1, the second #2, and so on.
ACTION Modify your application so that the parm parameter
is 16-bit (halfword) aligned.
---------------------------------------------------------------