E0300 MPE/iX Error Messages Manual Volume III > Chapter 6 TurboIMAGE/XL

Library Procedure Error Messages

	MPE documents
	Complete PDF
	Table of Contents

	E0701 Volume II

	E0300 Volume I
	E0300 Volume II
	E0300 Volume III ♥

	E0394 Volume I
	E0796 Volume II
	E0494 Volume III

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 may 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:

Table 6-1 Status Area Changes for 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 library procedure. Bits 0-3: Zero or access mode in which database is opened.	No change.
7	16-bit address of the database.	First 16 bits of the database address.
8	16-bit address of the data set name or qualifier.	Second 16 bits of database address.
9	Value of the mode parameter.	No change.
10	PB-relative address of the library procedure or the Compatibility Mode switch stub.	0

Abort Conditions

In general, four types of error conditions can cause TurboIMAGE/XL to abort the calling process:

A call from a Compatibility Mode user process with the hardware DB register not pointing to the process stack.
A faulty calling sequence.
An internal error in an MPE/iX file intrinsic which the calling procedure cannot correct.
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/iX 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/iX 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 may appear prior to the standard MPE/iX abort message.

Some of the abort conditions are due to an error in one of the MPE/iX 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/iX file information display listing all of the characteristics of the MPE/iX data set or root file where the error occurred, along with an MPE/iX error number.

I and J Files

When TurboIMAGE/XL detects an internal inconsistency or other abnormal situation, it may 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 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 MPE/iX failure code returned by FCHECK intrinsic. Refer to MPE/iX documentation for meaning of this code.

Messages (-1) - (-10)

-1

MESSAGE

MPE file error nn returned by FOPEN on root file or data set nn

CAUSE

For DBOPEN, error may 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/iX file system error occurred.
MPE/iX file system limit has been reached.

For DBOPEN, DBINFO, DBFIND, DBGET, DBUPDATE, DBPUT, and DBDELETE, error may 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/iX 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
CAUSE: 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
CAUSE: 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
CAUSE: This is an exceptional error (as -2 above) and is returned by DBOPEN, DBINFO, DBFIND, DBGET, DBUPDATE, DBPUT, DBDELETE.
ACTION: Notify system manager of error.

-5

MESSAGE: MPE file error nn returned by FWRITEDIR on root file or data set nn
CAUSE: 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
CAUSE: This exceptional condition could be returned when DBPUT, DBDELETE, or DBCLOSE calls FWRITELABEL.
ACTION: Notify system manager of error.

-8

MESSAGE: MPE file error nn returned by FUNLOCK on root file
CAUSE: This exceptional condition could be returned when DBOPENN calls FUNLOCK on a remote database-access file.
ACTION: Notify system manager of error.

-9

MESSAGE: Cannot create control block name: MPE error %nn
CAUSE: 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
CAUSE: 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

Messages (-11) - (-1003)

-11

MESSAGE: Bad base reference
CAUSE: 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 (or see below)
CAUSE: 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 (or see above)
CAUSE: For DBOPEN, when the database has been opened in access mode 2, the database has to 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 data base
CAUSE: 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
CAUSE: 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
CAUSE: 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 (or see below)
CAUSE: 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 (or see below)

CAUSE

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 may 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 (or see above)

CAUSE

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 may arise when a terminating semicolon or blank is omitted.

ACTION

Check application program's procedure call. Correct error in call.

-22

MESSAGE: Maintenance word required
CAUSE: For DBOPEN, maintenance word is required for non-creator to access the database.
ACTION: Supply the correct maintenance word.

-23

MESSAGE: Data set not writable
CAUSE: For DBPUT and DBDELETE, database has been opened in DBOPEN mode 1, 3, or 4 and user has read but not write access to the referenced data set.
ACTION: Modify access mode set in procedure call or notify current user operation cannot be performed.

-24

MESSAGE: Operation not allowed on automatic master data set
CAUSE: For DBPUT, the referenced data set is an automatic master.
ACTION: Modify data set name in call or in data set type in schema.

-30

MESSAGE: ILR enabled and bad access
CAUSE: The database has been ported from MPE V with ILR enabled. The only allowable access to the database is DBOPEN, mode 1-8, or DBUTIL to disable ILR.
ACTION: Open the database with mode 1-8 or disable ILR.

-31

MESSAGE: Bad mode
CAUSE: This error occurs in all procedures when the mode parameter is invalid. For DBGET, mode is 7 or 8 and referenced data set is a detail, or mode is 5 or 6 and referenced data set is a detail without search items.
ACTION: Correct mode in procedure call.

-32

MESSAGE

Unobtainable mode

CAUSE

For DBOPEN, root file cannot be FOPENed with access options (AOPTIONS) required for the specified mode. Second element of calling program's status area is required AOPTIONS, and third element is the AOPTIONS granted to DBOPEN by MPE/iX file system.

This error usually occurs either due to concurrent database access by other users or due to MPE/iX account or group security provisions.

ACTION

See the MPE/iX Intrinsics Manual (32650-90028) for meaning of AOPTIONS values.

Action depends on program's design. Normally notify user that requested access mode is not available.

-33

MESSAGE: Mode 7 diagnostics not allowed
CAUSE: For DBGET, mode 7 is not appropriate for diagnostics.
ACTION: Use a different mode for DBGET when diagnostic item list is in effect.

-51

MESSAGE

Bad list length

CAUSE

For DBGET, DBUPDATE, and DBPUT, the list is too long. This may occur if list is not terminated with a semicolon or blank. It may also occur for otherwise legitimate lists which are too long for TurboIMAGE/XL's work area.

It will never occur for numeric lists.

ACTION

Shorter list array contents. If necessary, change to numeric list.

-52

MESSAGE

Bad list or bad item

CAUSE

For DBGET, DBUPDATE, or DBPUT, the list parameter is invalid. list either has a bad format or contains a data item reference which:

Is out of range of the number of data items in the database.
References an inaccessible data item.
Duplicates another reference in the list.

For DBFIND, the item parameter contains data item reference which either:

Is out of range of the number of data items in the database.
Is not a search item for referenced data set.

ACTION

Check procedure call. Correct error in call or parameter.

-53

MESSAGE: Missing search or sort item
CAUSE: For DBPUT, a search or sort item of referenced data set is not included in list parameter.
ACTION: Check procedure call. Correct error in call or parameter.

-60

MESSAGE: Illegal file equation on root file
CAUSE: When using a :FILE command with the database name or a database-access file name, only the file designators and DEV= parameters are allowed.
ACTION: Reenter :FILE command without illegal parameters.

-80

MESSAGE: Output Deferred not allowed with ILR enabled
CAUSE: DBCONTROL (mode 1) was used to request deferred output, but deferred output cannot be used when ILR is enabled. Output deferred is not initiated.
ACTION: Do not use deferred output; or run DBUTIL and disable ILR.

-81

MESSAGE: Output Deferred not allowed with ROLLBACK enabled
CAUSE: DBCONTROL (mode 1) was used to request deferred output, but deferred output cannot be used when ROLLBACK is enabled. Output deferred is not initiated.
ACTION: Do not use deferred output; or run DBUTIL and disable ROLLBACK.

-90

MESSAGE: Root file bad: unrecognized state: %octal integer
CAUSE: For DBOPEN, this error is returned if the root file is in an unrecognized state. The octal integer represents an ASCII error code.
ACTION: Restore old copy of the root file for the database.

-91

MESSAGE: Bad root modification level
CAUSE: For DBOPEN, the software version of the DBOPEN procedure is incompatible with version of Schema Processor which created root file.
ACTION: Check with system manager that you have correct TurboIMAGE/XL software. If necessary ask HP support personnel about conversion.

-92

MESSAGE: Data base not created
CAUSE: For DBOPEN, the referenced database has not yet been created and initialized by the DBUTIL program (in CREATE mode).
ACTION: Run DBUTIL to create database. Try application program again.

-94

MESSAGE: Data base bad - Output deferred; may not be accessed in mode nn
CAUSE: For DBOPEN, referenced database was damaged while being modified in output deferred mode.
ACTION: Either DBLOAD from backup tape; or DBUNLOAD to ERASE data and then DBLOAD.

-95

MESSAGE: Data base bad - Creation was in process (create again)
CAUSE: 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: Data base bad - Erase was in process (erase again)
CAUSE: 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: Data base bad - ILR enable in process (enable again)
CAUSE: DBOPEN attempted to open a database but prior disable of ILR was not complete.
ACTION: Run DBUTIL with DNABLE command to enable ILR.

-98

MESSAGE: Data base bad - ILR disable in process (disable again)
CAUSE: DBOPEN attempted to open a database, but prior disable of ILR was not complete.
ACTION: Run DBUTIL with DISABLE command to disable ILR.

NOTE: Return statuses 100 through 107 are communication errors. For 100 through 102, the third element of calling program's status area is the MPE/IX failure code returned by DSCHECK intrinsics.

-100

MESSAGE: DSOPEN failure
CAUSE: 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 Support Representative.

-101

MESSAGE: DSCLOSE failure
CAUSE: 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
CAUSE: A line failure has occurred while attempting an operation on a remote database. May 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
CAUSE: 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
CAUSE: 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.
CAUSE: 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
CAUSE: This is an exceptional error returned by same intrinsics as 102 (see message listed earlier in this chapter). It indicates a hardware or system software failure.
ACTION: Notify system manager of problem.

-107

MESSAGE: NS 3000 or DS 3000 system error.
CAUSE: 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.
CAUSE: This is an internal error encountered during switching to Compatibility Mode.
ACTION: Notify HP Support Representative.

-110

MESSAGE: MPE OPENLOG intrinsic failure
CAUSE: OPENLOG returned error number nn to DBOPEN. This error may 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 Representative.

-111

MESSAGE: MPE WRITELOG intrinsic failure
CAUSE: When a database is enabled for logging, this error may be returned by DBOPEN, DBCLOSE, DBPUT, DBUPDATE, DBDELETE, DBMEMO, DBBEGIN, DBEND.
ACTION: Notify database administrator.

-112

MESSAGE: MPE CLOSELOG intrinsic failure
CAUSE: When a database is enabled for logging, this error may be returned by DBCLOSE. Or CLOSELOG returned error number nn to DBCLOSE.
ACTION: Notify database administrator.

-113

MESSAGE: FLUSHLOG returned error number nn to DBEND
CAUSE: User called DBEND in mode 2 to write the logging buffer to disk, but the MPE/iX logging facility returned an error.
ACTION: Notify your database administrator.

-114

MESSAGE: ROLLBACK without logging
CAUSE: DBOPEN has detected that ROLLBACK is enabled but logging is not.
ACTION: Notify your database administrator or HP Support Representative.

-121

MESSAGE: Descriptor count error
CAUSE: 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
CAUSE: 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
CAUSE: DBLOCK encountered a lock descriptor less than 9 halfwords long.
ACTION: Check contents of qualifier array.

-125

MESSAGE: Bad set name/number
CAUSE: 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
CAUSE: 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
CAUSE: 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
CAUSE: 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
CAUSE: 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
CAUSE: 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
CAUSE: 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
CAUSE: 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
CAUSE: 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
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.

Library Procedure Exceptional Conditions

Messages 10 - 999

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

Messages

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.; 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.

Schema Processor Error Messages

Chapter 7 TurboIMAGE/XL

Library Procedure Error Messages

MPE documents

Abort Conditions

I and J Files

Library Procedure File System and Memory Management

Messages (-1) - (-10)

Library Procedure Calling Errors

Messages (-11) - (-1003)

Library Procedure Exceptional Conditions

Messages 10 - 999

Library Procedure Abort Condition Messages in I File

Messages