HP 3000 Manuals HP 3000 Manuals
Library Procedure Error Messages
The success of each call to a TurboIMAGE/XL library procedure is
reflected upon return to the user by the condition code and the value of
the return status in the first element of the status area.
If the procedure fails to execute properly, the condition code is set to
CCL (Condition Code Less) and the return status is a negative integer.
In this section, "Library Procedure File System and Memory Management"
describes the negative integers resulting from file system and memory
management failures, while "Library Procedure Calling Errors" describes
the negative integers resulting from calling errors and communications
errors respectively.
If the procedure operates properly but encounters an exceptional
condition, such as end-of-file, the condition code is set to CCG
(Condition Code Greater) and the return status is a positive integer.
"Library Procedure Exceptional Conditions" describes the positive
integers resulting from exceptional conditions. If the procedure
operates properly and normally, the condition code is set to CCE
(Condition Code Equal) and the return status is zero.
In addition to the return status, all TurboIMAGE/XL library procedures
put information about the procedure call into the fifth through tenth
elements of the status area. This information can be useful in debugging
your programs, because it describes the conditions under which the
particular results were obtained. This information is used by DBEXPLAIN
and DBERROR when they are interpreting the results of TurboIMAGE/XL
calls.
In a few cases this information is not returned by the TurboIMAGE/XL
procedure because it uses the same locations in the status area for
returning other data. Specifically, successful execution of DBFIND,
DBGET, DBUPDATE, DBPUT, or DBDELETE puts other information here as
described in chapter 5 of this manual. For all other returns from a
library procedure, the specified elements of the status area have the
following contents:
Status Area Changes for MPE/iX Native Applications
-----------------------------------------------------------------------------------------------
| | | |
| Element | TurboIMAGE/V and Compatibility Mode | TurboIMAGE/XL |
| | | |
-----------------------------------------------------------------------------------------------
| | | |
| 5 | PB-relative address of the caller. | 0 |
| | | |
-----------------------------------------------------------------------------------------------
| | | |
| 6 | Bits 6-15: Intrinsic number of called | No change. |
| | library procedure. | |
| | Bits 0-3: Zero or access mode in | |
| | which database is opened. | |
| | | |
-----------------------------------------------------------------------------------------------
| | | |
| 7 | 16-bit address of the database. | First 16 bits of the database |
| | | address. |
| | | |
-----------------------------------------------------------------------------------------------
| | | |
| 8 | 16-bit address of the data set name or | Second 16 bits of database |
| | qualifier. | address. |
| | | |
-----------------------------------------------------------------------------------------------
| | | |
| 9 | Value of the mode parameter. | No change. |
| | | |
-----------------------------------------------------------------------------------------------
| | | |
| 10 | PB-relative address of the library | 0 |
| | procedure or the Compatibility Mode | |
| | switch stub. | |
| | | |
-----------------------------------------------------------------------------------------------
Abort Conditions
In general, four types of error conditions can cause TurboIMAGE/XL to
abort the calling process:
1. A call from a Compatibility Mode user process with the hardware DB
register not pointing to the process stack.
2. A structurally damaged database.
3. An internal error in an MPE file intrinsic which the calling
procedure cannot correct.
4. An internal inconsistency in the database or the DBG, DBB, or DBU
discovered by a library procedure.
In case 1, the procedure prints the standard MPE run-time abort message.
In cases 2, 3, and 4, TurboIMAGE/XL prints additional information on the
standard list device about the error prior to printing the standard MPE
abort message. The first line of this information is:
ABORT: procedure name ON DATABASE name;
where procedure name is the name of the library procedure which caused
the abort and name is the name of the database being accessed at the time
of the abort. "Library Procedure Abort Condition Messages" describes
additional lines of information which could appear prior to the standard
MPE abort message.
Some of the abort conditions are due to an error in one of the MPE file
intrinsics FOPEN, FREADLABEL, FREADDIR, FWRITELABEL, FWRITEDIR, or
FCLOSE. Aborts of this type generally occur after the procedure has
possibly altered the database so that the database structure has been
damaged in some way. Each of the messages in the section entitled
"Library Procedure Abort Condition Messages," which refer to a
TurboIMAGE/XL data file, are followed by an MPE file information display
listing all of the characteristics of the MPE data set or root file where
the error occurred, along with an MPE error number.
I and J Files
When TurboIMAGE/XL detects an internal inconsistency or other abnormal
situation and the database is enabled for dumping, it can create special
"I" and "J" files before it terminates. The "I" file consists of the
user's stack and procedure call trace markers; the "J" file consists of
the TurboIMAGE/XL database control blocks. TurboIMAGE/XL only creates
these "I" and "J" files if a database user has run DBUTIL and specified
ENABLE database name FOR DUMPING. So, if you want "I" and "J" files, you
must specifically request them through this DBUTIL command. Note that
"I" and "J" files are useful for debugging only if the database is known
to be structurally sound.
Library Procedure File System and Memory Management
For return status values -1 through -6, the second element of the calling
program's status area is the data set number for which file error
occurred (zero indicates root file). The third element is the MPE
failure code returned by the FCHECK intrinsic. Refer to MPE
documentation for meaning of this code.
-----------------------------------------------------------------
-1 MESSAGE MPE file error nn returned by FOPEN on root file
or data set nn
MEANING For DBOPEN, error can indicate that database could
not be opened. Possible reasons:
* Database name string not terminated with
semicolon or blank.
* Database does not exist or is secured
against access by its group or account
security.
* Database is already opened exclusively or in
mode incompatible with requested mode.
* MPE file system error occurred.
* MPE file system limit has been reached.
For DBOPEN, DBINFO, DBFIND, DBGET, DBUPDATE, DBPUT,
and DBDELETE, error can occur if:
* The process has too many files open external
to the database.
* Data set does not exist or is secured
against access.
* Some other MPE file system error has
occurred.
ACTION Determine which of probable causes applies and
either modify application program or see system
manager about file system error.
-----------------------------------------------------------------
-2 MESSAGE MPE file error nn returned by FCLOSE on root file
or data set nn
MEANING This is an exceptional error (should never happen)
and is returned only by DBOPEN or DBCLOSE.
Indicates a hardware or system software failure.
ACTION Notify system manager of error.
-----------------------------------------------------------------
-3 MESSAGE MPE file error nn returned by FREADDIR on root
file or data set nn
MEANING This is an exceptional error (as -2 above) and is
returned by DBOPEN, DBFIND, DBGET, DBUPDATE, DBPUT,
DBDELETE.
ACTION Notify system manager of error.
-----------------------------------------------------------------
-4 MESSAGE MPE file error nn returned by FREADLABEL on root
file or data set nn
MEANING This is an exceptional error (as -2 above) and is
returned by DBOPEN, DBINFO, DBFIND, DBGET,
DBUPDATE, DBPUT, DBDELETE, and DBUNLOCK.
ACTION Notify system manager of error.
-----------------------------------------------------------------
-5 MESSAGE MPE file error nn returned by FWRITEDIR on root
file or data set nn
MEANING This exceptional condition could be returned when
DBPUT, DBDELETE, DBUPDATE, or DBCLOSE calls
FWRITEDIR.
ACTION Notify system manager of error.
-----------------------------------------------------------------
-6 MESSAGE MPE file error nn returned by FWRITELABEL on root
file or data set nn
MEANING This exceptional condition could be returned when
DBPUT, DBDELETE, DBUNLOCK, or DBCLOSE calls
FWRITELABEL.
ACTION Notify system manager of error.
-----------------------------------------------------------------
[REV BEG]
-7 MESSAGE Previous MPE file error nn found in desired
buffer
MEANING This exceptional condition could be returned due to
corrupted buffer for multi-user environment from
DBPUT, DBUPDATE, or DBOPEN.
ACTION Notify your system manager of error.
----------------------------------------------------------------- [REV
END]
-8 MESSAGE MPE file error nn returned by FUNLOCK on root
file
MEANING This exceptional condition could be returned when
DBOPEN calls FUNLOCK on a remote database-access
file.
ACTION Notify system manager of error.
-----------------------------------------------------------------
-9 MESSAGE Cannot create control block name: MPE error %nn
MEANING This is an exceptional error returned when DBOPEN
fails to call HPFOPEN to create a control block.
ACTION Notify system manager or HP support personnel.
-----------------------------------------------------------------
-10 MESSAGE MPE file error %nn returned by FFILEINFO on root
file or data set nn
MEANING This is an exceptional error returned when DBOPEN
fails to call FFILEINFO on the root file.
ACTION Notify system manager or HP support personnel.
-----------------------------------------------------------------
Library Procedure Calling Errors
-----------------------------------------------------------------
-11 MESSAGE Bad base reference
MEANING 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
(See below for additional status code -12 message.)
MEANING 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
(See above for additional status code -12 message.)
MEANING For DBOPEN, when the database has been opened in
access mode -2, the database must 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
database
MEANING 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
MEANING 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
MEANING 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
(See below for additional status code -21
messages.)
MEANING 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
(See above or below for additional status code -21
messages.)
MEANING 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 can 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
(See above for additional status code -21
messages.)
MEANING 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 can arise when a
terminating semicolon or blank is omitted.
ACTION Check application program's procedure call.
Correct error in call.
-----------------------------------------------------------------