Library Procedure Error Messages

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

For DBOPEN, error may indicate that database could not be opened. Possible reasons:

For DBOPEN, DBINFO, DBFIND, DBGET, DBUPDATE, DBPUT, and DBDELETE, error may occur if:

Determine which of probable causes applies and either modify application program or see system manager about file system error.

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

This is an exceptional error (should never happen) and is returned only by DBOPEN or DBCLOSE. Indicates a hardware or system software failure.

Notify system manager of error.

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

This is an exceptional error (as -2 above) and is returned by DBOPEN, DBFIND, DBGET, DBUPDATE, DBPUT, DBDELETE.

Notify system manager of error.

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

This is an exceptional error (as -2 above) and is returned by DBOPEN, DBINFO, DBFIND, DBGET, DBUPDATE, DBPUT, DBDELETE.

Notify system manager of error.

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

This exceptional condition could be returned when DBPUT, DBDELETE, DBUPDATE, or DBCLOSE calls FWRITEDIR.

Notify system manager of error.

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

This exceptional condition could be returned when DBPUT, DBDELETE, or DBCLOSE calls FWRITELABEL.

Notify system manager of error.

MPE file error nn returned by FUNLOCK on root file

This exceptional condition could be returned when DBOPENN calls FUNLOCK on a remote database-access file.

Notify system manager of error.

Cannot create control block name: MPE error %nn

This is an exceptional error returned when DBOPEN fails to call HPFOPEN to create a control block.

Notify system manager or HP support personnel.

MPE file error %nn returned by FFILEINFO on root file or data set nn

This is an exceptional error returned when DBOPEN fails to call FFILEINFO on the root file.

Notify system manager or HP support personnel.

Bad base reference

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.

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

intrinsic name called without covering lock in effect (or see below)

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.

Modify program to apply proper lock or change mode.

Database must be in logon group and account (or see above)

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.

Retry call to DBOPEN from group and account containing database.

Not allowed; must be creator of root file or data base

DBOPEN failed because the caller is not the creator of the database and no maintenance word is specified.

Supply the correct maintenance word and retry call to DBOPEN.

Illegal intrinsic in current access mode

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.

Modify program or notify current user that operation cannot be performed.

Setup for RDBA failed

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.

Check your DBA file to make sure the DSLINE and REMOTE HELLO commands are correct.

Bad password (or see below)

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.

Supply correct password and/or maintenance word.

Bad data set reference (or see below)

For DBINFO (modes 104, 201, 202, 301, and 302), DBCLOSE, DBFIND, DBGET, DBUPDATE, DBPUT, DBDELETE, when data set reference is:

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.

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

Bad data item reference (or see above)

For DBINFO (modes 101, 102, and 204), data item reference is:

An erroneous data item name may arise when a terminating semicolon or blank is omitted.

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

Maintenance word required

For DBOPEN, maintenance word is required for non-creator to access the database.

Supply the correct maintenance word.

Data set not writable

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.

Modify access mode set in procedure call or notify current user operation cannot be performed.

Operation not allowed on automatic master data set

For DBPUT, the referenced data set is an automatic master.

Modify data set name in call or in data set type in schema.

ILR enabled and bad access

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.

Open the database with mode 1-8 or disable ILR.

Bad mode

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.

Correct mode in procedure call.

Unobtainable mode

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.

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.

Mode 7 diagnostics not allowed

For DBGET, mode 7 is not appropriate for diagnostics.

Use a different mode for DBGET when diagnostic item list is in effect.

Bad list length

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.

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

Bad list or bad item

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

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

Check procedure call. Correct error in call or parameter.

Missing search or sort item

For DBPUT, a search or sort item of referenced data set is not included in list parameter.

Check procedure call. Correct error in call or parameter.

Illegal file equation on root file

When using a :FILE command with the database name or a database-access file name, only the file designators and DEV= parameters are allowed.

Reenter :FILE command without illegal parameters.

Output Deferred not allowed with ILR enabled

DBCONTROL (mode 1) was used to request deferred output, but deferred output cannot be used when ILR is enabled. Output deferred is not initiated.

Do not use deferred output; or run DBUTIL and disable ILR.

Output Deferred not allowed with ROLLBACK enabled

DBCONTROL (mode 1) was used to request deferred output, but deferred output cannot be used when ROLLBACK is enabled. Output deferred is not initiated.

Do not use deferred output; or run DBUTIL and disable ROLLBACK.

Root file bad: unrecognized state: %octal integer

For DBOPEN, this error is returned if the root file is in an unrecognized state. The octal integer represents an ASCII error code.

Restore old copy of the root file for the database.

Bad root modification level

For DBOPEN, the software version of the DBOPEN procedure is incompatible with version of Schema Processor which created root file.

Check with system manager that you have correct TurboIMAGE/XL software. If necessary ask HP support personnel about conversion.

Data base not created

For DBOPEN, the referenced database has not yet been created and initialized by the DBUTIL program (in CREATE mode).

Run DBUTIL to create database. Try application program again.

Data base bad - Output deferred; may not be accessed in mode nn

For DBOPEN, referenced database was damaged while being modified in output deferred mode.

Either DBLOAD from backup tape; or DBUNLOAD to ERASE data and then DBLOAD.

Data base bad - Creation was in process (create again)

For DBOPEN, database was damaged by a file system failure, system failure, or TurboIMAGE/XL abort while DBUTIL CREATE command was creating the database.

Because database was not created, run DBUTIL CREATE command to create the database.

Data base bad - Erase was in process (erase again)

For DBOPEN, database was damaged by a file system failure, system failure, or TurboIMAGE/XL abort while DBUTIL ERASE command was erasing the database.

Because data was not erased, run DBUTIL ERASE command to erase the data from the database.

Data base bad - ILR enable in process (enable again)

DBOPEN attempted to open a database but prior disable of ILR was not complete.

Run DBUTIL with DNABLE command to enable ILR.

Data base bad - ILR disable in process (disable again)

DBOPEN attempted to open a database, but prior disable of ILR was not complete.

Run DBUTIL with DISABLE command to disable ILR.

DSOPEN failure

While executing a DBOPEN, TurboIMAGE/XL has encountered a hardware failure trying to obtain a communications line.

Try opening the database again. If error persists, contact your HP Support Representative.

DSCLOSE failure

This is an exceptional error returned by DBOPEN or DBCLOSE. It indicates a hardware or system software failure.

Notify system manager of problem.

DSWRITE failure

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.

Try calling the procedure again. If error persists, notify system manager.

Remote 3000 stack too small

Command Interpreter on remote HP 3000 cannot obtain stack space necessary to execute a DBOPEN or DBLOCK.

Ask system manager of remote system to increase available stack size.

Remote 3000 does not support TurboIMAGE/XL

This is an exceptional error and is returned by DBOPEN on the remote system.

Notify system manager of problem.

Remote 3000 cannot create TurboIMAGE control block.

This is an exceptional error and is returned by DBOPEN on the remote system.

Notify system manager of problem.

Remote 3000 data inconsistent

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.

Notify system manager of problem.

NS 3000 or DS 3000 system error.

This is an exceptional error returned by same intrinsics as 102 (see above). It indicates a hardware or system software failure.

Notify system manager of problem.

HPUNLOADCMPROCEDURE call failed.

This is an internal error encountered during switching to Compatibility Mode.

Notify HP Support Representative.

MPE OPENLOG intrinsic failure

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 (32650-90028) for listing of second values of status array and error messages.

Notify system manager or HP Support Representative.

MPE WRITELOG intrinsic failure

When a database is enabled for logging, this error may be returned by DBOPEN, DBCLOSE, DBPUT, DBUPDATE, DBDELETE, DBMEMO, DBBEGIN, DBEND.

Notify database administrator.

MPE CLOSELOG intrinsic failure

When a database is enabled for logging, this error may be returned by DBCLOSE. Or CLOSELOG returned error number nn to DBCLOSE.

Notify database administrator.

FLUSHLOG returned error number nn to DBEND

User called DBEND in mode 2 to write the logging buffer to disk, but the MPE/iX logging facility returned an error.

Notify your database administrator.

ROLLBACK without logging

DBOPEN has detected that ROLLBACK is enabled but logging is not.

Notify your database administrator or HP Support Representative.

Descriptor count error

DBLOCK detected an error in the descriptor count (first element of qualifier array) in locking mode 5 or 6.

Count must be a positive integer.

Illegal relop in a descriptor

DBLOCK encountered a relop field containing characters other than >=, <=, = or =.

Check contents of qualifier array.

Descriptor too short. Must be greater than or equal to 9

DBLOCK encountered a lock descriptor less than 9 halfwords long.

Check contents of qualifier array.

Bad set name/number

DBLOCK qualifier array contains an invalid data set name or number. (Refer to error -21 for rules.)

Check contents of qualifier array. Be sure names are delimited by semicolon or space if less than 16 bytes long.

Bad item name/number

DBLOCK qualifier array contains an invalid data item name or number. (Refer to error 21 for rules.)

Check contents of qualifier array. Be sure names are delimited by semicolon or space if less than 16 bytes long.

Attempt to lock using a compound item

DBLOCK does not allow compound items in lock descriptors.

Modify locking strategy to lock on a non-compound item.

Value field too short in a descriptor

A value field in a DBLOCK lock descriptor must be at least as long as the data item for which it is specified.

Check the length of the value field.

P-type item longer than P28 specified

DBLOCK does not allow P-type data items longer than 28 in lock descriptors (27 digits plus sign).

Modify locking strategy to lock on a different item.

Illegal digit in a P-type value

DBLOCK has encountered a P-type value in a lock descriptor with an invalid packed decimal digit.

Check qualifier array contents to determine why data is invalid.

Lowercase character in type-U value

DBLOCK has encountered a lowercase character in a type-U value specified in a lock descriptor.

Check qualifier array contents to determine why data is invalid.

Illegal digit in type Z value

Lock descriptor value specified to DBLOCK contains an invalid zoned decimal digit.

Check qualifier array contents to determine why data is invalid.

Illegal sign in type Z value

Lock descriptor value specified to DBLOCK contains an invalid zoned decimal sign.

Check qualifier array contents to determine why data is invalid.

Two descriptors conflict

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

Check qualifier array contents for conflicting lock descriptors.

Second lock without CAP=MR

A second call to DBLOCK has been made without an intervening DBUNLOCK call and program does not have MR capability.

Read discussion of multiple calls to DBLOCK in Chapter 4 of this manual if you plan to use CAP=MR.

Descriptor list exceeds 4094 bytes

DBLOCK allows a maximum length of 4094 bytes for lock descriptor lists (qualifier array).

Change qualifier array contents so lock descriptor list is shorter.

Text length greater than 512 bytes

Returned by DBBEGIN, DBEND, or DBMEMO.

Modify program.

DBCLOSE called while a transaction is in process; DBBEGIN called while a transaction is in process

A transaction is in process.

Call DBEND before DBCLOSE. Call DBEND before the next DBBEGIN.

DBEND called while no transaction in progress

No DBBEGIN precedes the call to DBEND.

Call DBBEGIN before DBEND.

ILR log file name conflict

There is a user file with the same name as the ILR log file name.

Replace the user file with a valid MPE/iX ILR log file.

Cannot check for an ILR log file conflict: file system error nn

DBUTIL DISABLE command or call to DBOPEN failed to open ILR log file.

Check file system error number.

Cannot purge ILR log file: file system error nn

DBUTIL DISABLE, PURGE, or ERASE command could not purge an ILR log file because of a file system error.

Check file system error number.

Cannot begin MPE XL XM transaction: XM error nn

The logical beginning of an MPE/iX transaction failed. nn is the error number returned.

Notify HP Support Representative.

Cannot attach n to MPE XL XM: File system error nn

Data set n could not be "attached" to the MPE/iX transaction recovery mechanism. MPE/iX intrinsic FILEINFO or FLABELINFO failed.

Notify HP Support Representative.

Invalid mode for XM attach options

An internal error has occurred.

Notify HP Support Representative.

Cannot open ILR log file: file system error nn

DBUTIL DISABLE command or call to DBOPEN was not able to open ILR log file due to file system error.

Check file system error number.

Cannot read ILR log file: file system error nn

DBUTIL DISABLE command or call to DBOPEN was not able to read ILR log file due to file system error.

Check file system error number.

Unable to obtain write access

DBOPEN has determined that it is necessary to perform ILR. The current user does not have write access to the database.

Have the database opened by a user with write access.

Bad mode for ILR

DBOPEN has determined that it is necessary to perform ILR. The database must be opened for writing.

Open the database in mode 1-4.

Cannot attach n to MPE XL XM: XM error nn

The data set n could not be "attached" to the transaction recovery mechanism. nn is the MPE/iX error number returned.

Notify HP Support Representative.

Cannot detach n from MPE XL XM: XM error nn.

The data set n could not be "detached" from the transaction recovery mechanism. nn is the MPE/iX error number returned.

Notify HP Support Representative.

MPE log file is not in the same volume set as the database.

MPE/IX transaction recovery requires that the user log file must reside in the same volume set as the database.

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.

Cannot detach n from MPE XL XM: file system error nn

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.

Notify HP Support Representative.

Cannot begin MPE XL transaction for attach: XM error nn

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.

Notify HP Support Representative.

ILR log invalid - internal file name does not match root file

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.

Use DBRESTOR to restore database.

ILR log file invalid - internal group name does not match root file

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

Use DBRESTOR to restore database.

ILR log invalid - internal account name does not match root file

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

Use DBRESTOR to restore database.

ILR log invalid - internal creation date does not match root file

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.

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.

ILR log invalid - internal last access data access data does not match root file

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.

Always store database with DBSTORE and restore with DBRESTOR to assure consistent dates in root file and log file.

ILR is already enabled for this database

DBUTIL ENABLE command attempted to enable a database for ILR when ILR was already enabled.

Warning only.

ILR is already disabled for this database

DBUTIL DISABLE command attempted to disable a database for ILR when ILR was already disabled.

Warning only.

Cannot begin MPE XL transaction for detach: XM error nn

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.

Notify HP Support Representative.

Bad DBS

The Database System Control Block has been corrupted.

Notify HP Support Representative.

The DBS is full

DBOPEN has detected that there is no more room in the DBS to hold any more DBG entries.

Notify HP Support Representative.

Invalid DBU

The database user local control block has been corrupted.

Notify HP Support Representative.

DBU control block is full

The database user local control block is full.

Notify HP Support Representative.

Invalid DBB

The database buffer control block has been corrupted.

Notify HP Support Representative.

Invalid DBG

The database global control block has been corrupted.

Notify HP Support Representative.

DBB control block is full

The database buffer control block is full.

Notify HP Support Representative.

DBG control block is full

The database global control block is full.

Notify HP Support Representative.

Total DBOPEN count/user exceeds limit

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.

Notify HP Support Representative.

Cannot end MPE XL XM transaction: XM error nn

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.

Notify system manager.

Data base language not system supported

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.

Notify system manager.

Native Language Support not installed

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.

Notify system manager.

MPE Native Language Support error nn returned by NLINFO

The error number given was returned by NLS/3000 on a NLINFO call in DBOPEN.

Notify system manager.

Data base exceeds limits

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.

Access the remote TurboIMAGE/XL database from another local node which also supports TurboIMAGE/XL.

MPE error nn returned by FLABELINFO for MPE XL XM

The MPE/iX file system error nn was returned by the intrinsic FLABELINFO.

Notify HP Support Representative.

Invalid mode for MPE XL XM DETACH

An internal error has occurred.

Notify HP Support Representative.

MPE error nn on log file name

MPE/iX file system error nn was returned while trying to obtain the user log file name.

Notify HP Support Representative.

Internal error returned

Internal error nn occurred while in an intrinsic.

Notify HP Support Representative.

Switch failure, INFO nn, SUBSYS nn

The switch to Native Mode failed. SUBSYS nn is the subsystem that failed. INFO nn is the error number returned from that subsystem.

Notify HP Support Representative.

Switch to CM failed on CX'PCBXIMAGE

Internal error. This error is returned when DBOPEN calls CM CX'PCBXIMAGE and encounters a switch to CM failure.

Notify HP Support Representative.

HPLOADCMPROCEDURE failed on CX'PCBXIMAGE

Internal error. This error is returned when DBOPEN calls HPLOADCMPROCEDURE for CM CX'PCBXIMAGE and fails.

Notify HP Support Representative.

Switch to NM failed on DBxxx, INFO nn SUBSYS nn

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.

Notify HP Support Representative.

Beginning of file

DBGET has encountered beginning of file during a backward serial read. (There are no entries before the one previously accessed.)

Appropriate action depends on program design.

End of file

DBGET has encountered the end of file during a forward serial read. (There are no entries beyond the most recently accessed one.)

Appropriate action depends on program design.

Directed beginning of file

DBGET has been called for a directed read with a record number less than 1.

Appropriate action depends on program design.

Directed end of file

DBGET has been called for a directed read with a record number greater than the capacity of data set.

Appropriate action depends on program design.

Beginning of chain

DBGET has encountered end of chain during a backward chained read.

Appropriate action depends on program design.

End of chain

DBGET has encountered end of chain during a forward chained read.

Appropriate action depends on program design.

Data set full

DBPUT has discovered that data set is full.

Restructure database with larger capacity for this data set.

No master entry ( or see below)

DBFIND is unable to locate master data set entry (chain head) for specified detail data set's search item value.

Appropriate action depends on program design.

No entry (or see above)

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.

Appropriate action depends on program design.

Broken chain

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.

Begin reading chain again from first or last entry.

Data base locked or contains locks

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.

Appropriate action depends on program design.

Data set locked by another process

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.

Appropriate action depends on program design.

Entries locked within set

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.

Appropriate action depends on program design.

Item conflicts with current locks

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.

Appropriate action depends on program design.

Entries already locked

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.

Appropriate action depends on program design.

Critical item

DBUPDATE has been asked to change value of search or sort item.

Correct call or notify user cannot update item.

Read only item

DBUPDATE has been asked to change value of a data item for which the user does not have write access.

Notify user, cannot update item. Or change password in program.

Duplicate key item value

DBPUT has been asked to insert data entry into a master data set with a key item value which already exists in data set.

Appropriate action depends on program design.

Can't delete master entry with non-empty detail chains

DBDELETE has been asked to delete master data set entry which still has one or more non-empty chains.

Appropriate action depends on program design.

Illegal buffer address

Calling program's buffer (identified by buffer parameter) address of DBGET or DBINFO is an unsupported memory address.

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.

Buffer too small

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.

Correct procedure call, or change buffer name or size.

Data base access disabled

DBOPEN has been called when the database has been disabled for access.

Notify database administrator.

Data base opened more than 63 times by same process.

DBOPEN has been called when the specified database has already been opened 63 times by the same process.

Correct your program so that DBOPEN does not open the same database more than 63 times.

DBG Control Block is Full

Lock area within DBG is full.

Notify your database administrator.

DBG disabled; potential damage; only DBCLOSE allowed

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.

Issue a DBCLOSE, mode 1.

No room for DBG entry in PCBX (MPE/iX portion of stack)

The PCBX is full.

Try again when system resources are available.

Can't grant buffer request

DBCONTROL cannot increase the number of buffers as requested by the user. A current count is returned.

Request a smaller number of buffers.

DBG pointed to by root file does not match

Root file is not compatible with DBG.

Notify HP Support Representative.

DBU disabled; potential damage; only DBCLOSE allowed

The user's control block is in an inconsistent state.

Issue a DBCLOSE, mode 1.

Bad DBB

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.

Issue a DBCLOSE, mode 1.

Bad database

AUTODEFER is active, and the database did not close normally. The database has been corrupted.

Notify your database administrator.

Missing chain head

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.

Notify user cannot add entry or add manual master entry and try again.

Full chain

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

Consult with database manager. May need to delete some entries from chain or restructure database.

Full master

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

Restructure database, increasing capacity of automatic master.

Warning: Assuming no message catalog

No message catalog is available.

Notify your system administrator.

Unrecognized return status: nn

Return status could not be recognized.

Notify HP Support Representative.