Library Procedure Error Messages (contd) [ TurboIMAGE/XL Database Management System Reference Manual ] MPE/iX 5.0 Documentation
TurboIMAGE/XL Database Management System Reference Manual
Library Procedure Error Messages (contd)
Library Procedure Calling Errors (contd)
-259 MESSAGE Invalid mode for index
MEANING This message is returned if you are using
third-party indexing (TPI). The mode is not
applicable to this type of index.
ACTION Consult your third-party vendor documentation.
---------------------------------------------------------------
-260 MESSAGE No previous list of qualified data entries
MEANING This message is returned if you are using
third-party indexing (TPI). The DBFIND mode
specified can only be used if a qualified set of
entries exists.
ACTION Consult your third-party vendor documentation.
---------------------------------------------------------------
-3nn MESSAGE Internal error returned
MEANING Internal error nn occurred while in an intrinsic.
ACTION Notify HP support personnel.
---------------------------------------------------------------
-1000 MESSAGE Switch failure, INFO nn, SUBSYS nn
MEANING 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 personnel.
---------------------------------------------------------------
-1001 MESSAGE Switch to CM failed on CX'PCBXIMAGE
MEANING Internal error. This error is returned when DBOPEN
calls CM CX'PCBXIMAGE and encounters a switch to CM
failure.
ACTION Notify HP support personnel.
---------------------------------------------------------------
-1002 MESSAGE HPLOADCMPROCEDURE failed on CX'PCBXIMAGE
MEANING Internal error. This error is returned when DBOPEN
calls HPLOADCMPROCEDURE for CM CX'PCBXIMAGE and
fails.
ACTION Notify HP support personnel.
---------------------------------------------------------------
-1003 MESSAGE Switch to NM failed on DBxxx, INFO nn SUBSYS nn
MEANING 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 personnel.
---------------------------------------------------------------
-1004 MESSAGE HPLOADNMPROC FAILED ON CM intrinsic name
MEANING An internal error has occurred.
ACTION Notify HP support personnel.
---------------------------------------------------------------
Library Procedure Exceptional Conditions
---------------------------------------------------------------
10 MESSAGE Beginning of file
MEANING DBGET has encountered beginning of file during a
backward serial read. (No entries exist before the
one previously accessed.)
ACTION Appropriate action depends on program design.
---------------------------------------------------------------
11 MESSAGE End of file
MEANING DBGET has encountered the end of file during a
forward serial read. (No entries exist beyond the
most recently accessed one.)
ACTION Appropriate action depends on program design.
---------------------------------------------------------------
12 MESSAGE Directed beginning of file
MEANING 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
MEANING 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
MEANING DBGET has encountered end of chain during a
backward chained read.
ACTION Appropriate action depends on program design.
---------------------------------------------------------------
--------------------------------------------------------------
15 MESSAGE End of chain
MEANING DBGET has encountered end of chain during a forward
chained read.
ACTION Appropriate action depends on program design.
---------------------------------------------------------------
[REV BEG]
16 MESSAGE Data set full
MEANING DBPUT has discovered that data set is full and
cannot add a record as requested. (Message
received when return status word 1 is 16, and word
3 is 0.)
ACTION Restructure database with larger capacity for this
data set. (See chapter 8 for information on
changing data set capacity in conjunction with
DBUNLOAD and DBLOAD.)
---------------------------------------------------------------
16 MESSAGE DBPUT cannot expand dataset#: Data set at maximum
capacity
MEANING The current capacity is at the maximum allowed, the
data set cannot be expanded. (Message received
when return status word 1 is 16, and word 3 is 1.)
ACTION If necessary, use DBChange Plus or third party
software to increase the maximum capacity. (See
MPE/iX Release 5.0 Communicator for information on
using DBChange Plus. See chapter 3 for information
on detail data set capacity parameters and chapter
5 for DBPUT.)
---------------------------------------------------------------
16 MESSAGE DBPUT dataset# incomplete expansion: File system
error #
MEANING DBPUT cannot expand to the incremental amount due
to a file system error. (Message received when
return status word 1 is 16, and word 3 is 2.)
ACTION Determine the file system error (see file system
manual) and correct the problem identified. (See
chapter 3 for information on detail data set
capacity parameters and chapter 5 for DBPUT.)
---------------------------------------------------------------
16 MESSAGE DBPUT cannot expand dataset#: Out of disc space
(FSERR #)
MEANING There is no disc space for DBPUT to expand the data
set. (Message received when return status word 1
is 16, and word 3 is 3.)
ACTION Increase disc space and rerun your application.
(See chapter 3 for information on detail data set
capacity parameters and chapter 5 for DBPUT.)
--------------------------------------------------------------- [REV END]
17 MESSAGE No master entry
(See below for additional status code 17 message.)
MEANING 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
(See above for additional status code 17 message.)
MEANING DBGET mode 1 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) when called with mode
4.
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
MEANING 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 Database locked or contains locks
MEANING 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
MEANING 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
MEANING 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 or 6 only.
ACTION Appropriate action depends on program design.
---------------------------------------------------------------
24 MESSAGE Item conflicts with current locks
MEANING 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
MEANING 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.
---------------------------------------------------------------
26 MESSAGE Lock not performed since deadlock would result.
MEANING If it is a self-deadlock, the database or data set
is already locked by the same process but with a
different open count.
If it is locked by another process, it is because
of the DBLOCK call from a SQL user that the real
deadlock is encountered.
ACTION To avoid the the self-deadlock, modify the program.
If it is a real deadlock caused by another process,
call DBUNLOCK.
---------------------------------------------------------------
41 MESSAGE DBUPDATE attempted to modify value of critical
item--key, search or sort
(See below for additional status code 41 messages.)
MEANING DBUPDATE has been asked to change the value of a
master data set key item or a detail data set
search or sort item. For master data sets and
regardless of the critical item update (CIUPDATE)
option settings for the database and the current
process, this message is always returned if you
attempt to use DBUPDATE on key items. For detail
data sets, this message is returned when you
attempt to use DBUPDATE on a search or sort item
and the CIUPDATE option setting for the database or
a particular process does not permit this type of
modification.
ACTION Correct call, or notify user that item cannot be
updated. For detail data sets only, the
application can be redesigned to use the CIUPDATE
option.
---------------------------------------------------------------
41 MESSAGE DBUPDATE: No chain head (master entry) for path
decimal integer: nn
(See above and below for additional status code 41
messages.)
MEANING User has called DBUPDATE to update a detail data
set entry with a search item value that does not
match any existing key item value in the
corresponding manual master data set. The digits
nn identify the offending path number established
by the sequence in which the detail data set search
items appear in the set part of the schema. This
message is associated with the critical item update
(CIUPDATE) option; see chapter 4 for information
about this option.
ACTION Notify user that the new data item value must
already exist in the associated manual master data
set. If the new value is to be allowed, add the
manual master data set entry and try again.
---------------------------------------------------------------
41 MESSAGE DBUPDATE: Full chain for path decimal integer:
nn (contains 2,147,483,647 entries
(See above and below for additional status code 41
messages.)
MEANING User has called DBUPDATE to update a detail data
set entry associated with an automatic master data
set chain that already contains 2,147,483,647
values, the maximum allowable entries. The digits
nn identify the offending path number established
by the sequence in which the detail data set search
items appear in the set part of the schema. This
message is associated with the critical item update
(CIUPDATE) option; see chapter 4 for information
about this option.
ACTION Consult with your database administrator to ensure
the database has no structural damage. It is
likely that the database contains an invalid chain
count.
---------------------------------------------------------------
41 MESSAGE DBUPDATE: Full automatic master for path decimal
integer: nn
(See above and below for additional status code 41
messages.)
MEANING Automatic master data set is full. User has called
DBUPDATE to update a search item in a detail data
set, and the corresponding key item value could not
be added to the automatic master data set. The
digits nn identify the offending path number
established by the sequence in which the detail
data set search items appear in the set part of the
schema. This message is associated with the
critical item update (CIUPDATE) option; see chapter
4 for information about this option.
ACTION Your database administrator needs to restructure
the database, increasing the capacity of the
automatic master data set. Refer to chapter 8 in
this manual for information on database
restructuring.
---------------------------------------------------------------
41 MESSAGE DBUPDATE: Full automatic master synonym chain
for path decimal integer: nn
(See above for additional status code 41 messages.)
MEANING User has called DBUPDATE to update a detail data
set search item associated with an automatic master
data set that cannot accommodate another new value
on the synonym chain for that path number. The
digits nn identify the offending path number
established by the sequence in which the detail
data set search items appear in the set part of the
schema. This message is associated with the
critical item update (CIUPDATE) option; see chapter
4 for information about this option.
ACTION Ask your database administrator to verify that the
synonym chain is indeed full and inspect your
database for possible structural damage.
---------------------------------------------------------------
42 MESSAGE Read only item
MEANING DBUPDATE has been asked to change the 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
MEANING DBPUT has been asked to insert a data entry into a
master data set with a key item value which already
exists in the data set.
ACTION Appropriate action depends on program design.
---------------------------------------------------------------
44 MESSAGE Can't delete master entry with non-empty detail
chains
MEANING DBDELETE has been asked to delete a 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
MEANING 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
MEANING 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 Database access disabled
MEANING DBOPEN has been called when the database has been
disabled for access.
ACTION Notify database administrator.
---------------------------------------------------------------
61 MESSAGE Database opened more than 63 times by same
process.
MEANING 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
MEANING Lock area within DBG is full.
ACTION Notify your database administrator.
---------------------------------------------------------------
63 MESSAGE DBG disabled; potential damage; only DBCLOSE
allowed
MEANING 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.
If the database has been enabled for dumping, an I
and a J file should exist. These files can help
determine the cause of the error. The database
should be recovered. This error has the same
effect on a database as a system failure.
ACTION Issue a DBCLOSE, mode 1.
---------------------------------------------------------------
64 MESSAGE No room for DBG entry in PCBX (MPE portion of
stack)
MEANING The PCBX is full.
ACTION Try again when system resources are available.
---------------------------------------------------------------
65 MESSAGE Can't grant buffer request
MEANING 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
MEANING Root file is not compatible with DBG.
ACTION Notify HP support personnel.
---------------------------------------------------------------
67 MESSAGE DBU disabled; potential damage; only DBCLOSE
allowed
MEANING The user's control block is in an inconsistent
state.
ACTION Issue a DBCLOSE, mode 1.
---------------------------------------------------------------
68 MESSAGE Bad DBB
MEANING 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.
If the database has been enabled for dumping, an I
and a J file should exist. These files can help
determine the cause of the error. The database
should be recovered. This error has the same
effect on a database as a system failure.
ACTION Issue a DBCLOSE, mode 1.
---------------------------------------------------------------
69 MESSAGE Bad database
MEANING AUTODEFER is active, and the database did not close
normally. The database has been corrupted.
ACTION Notify your database administrator.
---------------------------------------------------------------
1nn MESSAGE No chain head (master entry) for path decimal
integer: nn
MEANING 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 the order in
which the search items occur in the set part of the
schema.
ACTION Notify user cannot add entry or add manual master
entry and try again.
---------------------------------------------------------------
2nn MESSAGE Full chain for path decimal integer: nn (contains
2,147,483,647 entries)
MEANING 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 established
by the order in which the search items occur in the
set part of the schema.
ACTION Consult with the database manager. The database
could contain an invalid chain count.
---------------------------------------------------------------
3nn MESSAGE Full automatic master for path decimal integer:
nn
MEANING 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 established by the order in which the search
items occur in the set part of the schema.
ACTION Restructure database, increasing capacity of
automatic master. (See chapter 8).
---------------------------------------------------------------
4nn MESSAGE Full automatic master synonym chain for path
decimal integer: nn
MEANING User has attempted to add a detail data set search
item associated with an automatic master data set
that cannot accommodate another new value on the
synonym chain for that path number. The digits nn
identify the offending path number established by
the sequence in which the detail data set search
items appear in the set part of the schema.
ACTION Ask your database administrator to verify that the
synonym chain is indeed full and inspect your
database for possible structural damage.
---------------------------------------------------------------
944 MESSAGE Warning: Assuming no message catalog
MEANING No message catalog is available.
ACTION Notify your system administrator.
---------------------------------------------------------------
Others MESSAGE Unrecognized return status: nn
MEANING Return status could not be recognized.
ACTION Notify HP support personnel.
---------------------------------------------------------------
MPE/iX 5.0 Documentation