Error Messages

The following error messages may appear on the ODT and on the station running an accessory linked to DBEngine. These messages may also appear in the accessory’s report file.

All error messages are displayed by the default error handler in DBSupport. If desired, you can write a custom error handling routine to perform an action when a particular error is encountered. For example, you could write an error handling routine so that when the Server Accessory encounters an error trying to notify a client system, the Server Accessory will retry the notification. Refer to the DATABridge Programmer’s Reference for information about creating a custom error handling routine.

0000 DATABridge Engine: OK

This is a notification that the last call to a DBEngine entry point was completed without error.

0001 DATABridge Engine: Commit transaction group

This is a notification that DBEngine encountered the end of a transaction group. The accessory should now commit all updates it has received for this group.

0002 DATABridge Engine: Abort transaction group

DBEngine has encountered an indication that the current transaction group was aborted. The accessory should discard all updates it has received in this transaction group.

0003 DATABridge Engine: Caller cancelled

An accessory’s callback procedure returned a FALSE, which indicates that it does not want to receive any more callbacks.

0004 DATABridge Engine: Invalid database name: name

An accessory passed an invalid database name to an entry point. Check the input to the accessory and try again.

0005 DATABridge Engine: Invalid dataset name: name

An accessory passed an invalid data set name to an entry point. Check the input to the accessory and try again.

0006 DATABridge Engine: Invalid data item name: name

An accessory passed an invalid data item name to an entry point. Check the input to the accessory and try again.

0007 DATABridge Engine: message

where message is one of the following messages:

Active (usercode)database audit file filenumber is unavailable

The audit file is still in use by the Accessroutines. This is normal and indicates that the accessory should stop.

Active (usercode)database audit file filenumber has no more audit available

DATABridge Plus has gathered all of the updates from the current audit file up to the last QPT.

(usercode)database Audit file filenumber is an incorrect audit file number

DBEngine was given an AFN less than one or greater than 9999. Check the values that the accessory passes to DBEngine to make sure they’re not invalid.

Another program opened (usercode)database audit file filenumber EXCLUSIVE

A different program has opened the audit file with the EXCLUSIVE attribute set to TRUE. Rerun the accessory when that program has finished.

(usercode)database Audit file filenumber was not found

An operator entered a mixnumberNF command to indicate that the audit file is not available. Reload the audit file and run the accessory again.

(usercode) database Audit file filenumber missing section

Reload the missing sections of the audit file and run the accessory again.

(usercode)database Audit file filenumber is offline

The audit file is archived offline. Retrieve the audit file, load it, and run the accessory again.

(usercode)database Audit file filenumber is unavailable (no family packname)

The pack that contains the audit file is unavailable. Make the pack ready and rerun the accessory.

(usercode)database Audit file filenumber does not exist because the database was never updated.

DBEngine was given an audit file number for a file that has not yet been created. Check the values that the accessory passes to DBEngine and rerun the accessory.

0008 DATABridge Engine: Missing DESCRIPTION file for Audit file update level updatelevel

DBEngine cannot find a DMSII DESCRIPTION file that is compatible with the audit file. updatelevel gives the DMSII update level for the audit file. Therefore, copy the DESCRIPTION file that does have the compatible update level from a backup (such as one of the following) and run the accessory again:

DESCRIPTION/databasename/updatelevel

—or—

updatelevel/DESCRIPTION/databasename

0009 DATABridge Engine: Audit file filenumber: Unexpected end-of-file

DBEngine encountered an unexpected end-of-file error while reading the audit file given by filenumber. Most likely the audit file is corrupted. Use COPYAUDIT to reload the audit file from a backup and then rerun the accessory.

0010 DATABridge Engine: Data set structurenumber not selected

An accessory requested information for a data set that it had not previously selected via the DBSELECT entry point. structurenumber is the structure number of the data set that was not previously selected. This typically indicates a problem in a user-written accessory. Check the user-written source code and try again.

0011 DATABridge Engine: Invalid audit location for value_1; value_2 must be from value_3 to value_4

An accessory tried to select a data set but gave an invalid audit location:

value_1 indicates the data set.
value_2 is the name of the audit location component that is invalid.
value_3 and value_4 give the legal range for that component.

Check the input to the accessory. If the accessory is Span, check the Span Accessory parameter file to make sure that all of the audit locations have legal values. Correct any illegal values and try again.

0012 DATABridge Engine: Invalid dataset structure number: number

An accessory passed an invalid data set structure number to an entry point. number in this case is not a data set in the DMSII database. Instead, it could be one of the following:

The structure number for a set. In this case, check the input to the accessory and correct the structure number.
If the accessory specified a logical database, it could be a data set that exists in the physical database but not in the logical database. In this case, select a different logical or physical database.

0013 DATABridge Engine: Out of room in array arrayname

DBEngine was unable to allocate more memory for one of its internal arrays. If this error occurs consistently, report this error to Technical Support.

0014 DATABridge Engine: Invalid attribute number attrnum

The accessory requested file attribute information but gave an invalid file attribute number.

0015-0018 N/A

These numbers are not currently used.

0019 DATABridge Engine: No datasets or remaps selected

An accessory requested updates from DBEngine, but it did not previously select any data sets or remaps.

0020 DATABridge Engine: Table reorganization required for datasetname; DMS dataset level = updatelevel, Table level = clienttablelevel

The DMSII update (format) level for datasetname does not match the update level for the corresponding client table. After making any necessary changes to the table in the client database, update the client table level information to match the DMSII update level for datasetname. See Span Accessory. This message applies to any accessory that calls the DBREAD entry point in DBEngine.

0021 DATABridge Engine: Table purge required for clienttablename

The audit trail contains a record indicating a selected data set was initialized (using DMUTILITY). Purge the table in the client database and then set the mode value back to normal (2) for that table.This message applies to any accessory that calls the DBREAD entry point in DBEngine.

0022 DATABridge Engine: Database timestamp mismatch: Audit file has timestamp, DESCRIPTION file has timestamp

The database timestamp in the audit file does not match the database timestamp in the DESCRIPTION file. Find the correct DESCRIPTION file and make it available to DATABridge.

0023 DATABridge Engine: Array is too short: arrayname

An accessory passed an array as a parameter to one of the DBEngine entry points, but the array was shorter than DBEngine expected. Typically, this error occurs when an accessory is not recompiled with the current version of the DATABridge Interface. Recompile the accessory with the current DATABridge interface and try again.

0024 DATABridge Engine: filetitle is not available

DBEngine could not locate the database CONTROL file. Locate the DMSII database CONTROL file and make it available to DATABridge. Make sure you check security access restrictions.

0025 DATABridge Engine: databasename is not an audited database

The requested database is not an audited database. DATABridge can use only audited databases.

0026 DATABridge Engine: modevalue is an invalid mode for datasetname

An accessory tried to select a data set with an invalid mode value. (The mode value indicates whether the data set should be cloned, processed normally, etc.) In this case, set the mode to the correct value, as follows:

Mode = 0 The data set needs to be cloned.
Mode = 1 The data set is in the fix up phase.
Mode = 2 The data set is in the update phase.
Mode = 3 The data set was reorganized.
Mode = 4 The data set was purged.

This message applies to any accessory that calls the DBSELECT entry point in DBEngine.

Note: Mode values also apply to the DATABridge Clients. In the DATABridge Client's Administrator’s Guide, look for ds_mode in the client control tables.

0027 DATABridge Engine: datasetname does not have a set with a unique key

An accessory tried to initiate cloning for a data set that does not have a NO DUPLICATES set. Cloning of certain types of data sets requires a NO DUPLICATES set. One option is to define a primary key for the data set. See Creating a Primary Key.

0028 DATABridge Engine: DATABridge not initialized

The accessory called an entry point in DBEngine that requires a previous (successful) call of DBINITIALIZE, which determines the database being replicated. Check your user-written accessory to make sure you initialize DBEngine before you call any other entry points.

0029 DATABridge Engine: DMS Error: subtype

subtype contains the text of a DMS error message. Consult your Unisys DMSII manuals for more information on this message.

0030 DATABridge Engine: Invalid set structure number: number

An accessory passed an invalid set structure number to an entry point. number in this case is not a set in the DMSII database. Instead, it could be one of the following:

The structure number for a data set. In this case, check the input to the accessory and correct the structure number.
If the accessory specified a logical database, it could be a set that exists in the physical database but not in the logical database. In this case, select a different logical or physical database.

0031 DATABridge Engine: Invalid data item number: number not found in dataset

The accessory passed an invalid data item number to an entry point. The data set does not have a data item with that number. Most likely, the accessory passed the wrong data set and/or item number to the DBNULL entry point. Correct the user-written accessory. Note that the DBLAYOUT entry point returns information about individual data items, including their item numbers.

0032 DATABridge Engine: Invalid variable format record type number for dataset #structurenumber

The accessory passed an invalid record type number for a variable format data set. Check your user-written accessory for the variable format record type number. The DBDATASETS and DBDATASETINFO entry points return information about valid record types.

0033 DATABridge Engine: tablename: Audit location mismatch, subtype = value is wrong. Check for DMS rollback. The call to DBSELECT contained an audit location that is incorrect.

tablename is the accessory-supplied name, which defaults to the dataset name.
subtype indicates which component of the audit location is incorrect, for example, the ABSN or INX.
value contains the value of that component.

This error could indicate that the DMSII database was rolled back. If so, roll back the client database as well. This message applies to any accessory that uses the DBSELECT entry point. This error can also occur if you attempt a roll back but have an invalid timestamp. See Manual Recovery from a Rollback.

0034 DATABridge Engine: internal error: Invalid node in DESCRIPTION file

DBEngine encountered an error reading the DESCRIPTION file. If this error occurs consistently, report this error to Technical Support.

0035 DATABridge Engine: Internal error: Invalid STR index in value_1

DBEngine generated an invalid array index. If this error occurs consistently, report this error to Technical Support.

0036 DATABridge Engine: Embedded dataset not supported: #value_1 value_2

An accessory tried to select an embedded data set for processing. DATABridge does not support certain types of embedded data sets at this time. In order to clone an ORDERED or COMPACT data set, NO DUPLICATES must be set.

value_1 contains the structure number of the embedded data set.
value_2 contains the embedded data set name.

0037 DATABridge Engine: Database does not have a global record

An accessory tried to select the global data set for processing but the database does not have a global data set.

0038 DATABridge Engine: Set value does not have any keys

An accessory requested the keys for a set but the set does not have a key. value contains the set name. This is an informational message.

0039 DATABridge Engine: Invalid structure index: number

An accessory requested the name of a structure but gave an invalid number for the structure index. (The structure index is not the same as the structure number. It is the unique number returned by DBSELECT.) In this case, correct the user-written accessory to request a valid number for the structure index.

0040 DATABridge Engine: Database name databasename not found

An accessory requested a database, but DBEngine could not find the database indicated by databasename. In this case, check the following:

Spelling of databasename
Usercode for DATABridge and database
Usercode specified by CONTROL file and DASDL

0041 DATABridge Engine: Access to databasename denied until day @ time

DATABridge Engine: Access to databasename denied by operator QUIT

DATABridge Engine: Access to databasename denied by guardfile

databasename indicates the logical or physical database name. This error can occur in any of the following cases:

The DBEngine parameter file limits database access to certain hours of the day and the current time is outside of that time period
The host operator stopped the DBEngine by issuing the AX QUIT command
The database guardfile does not allow the accessory to access the database

For more information about setting up guardfiles, see the DATABridge Installation Guide.

0042 DATABridge Engine: Missing DMSUPPORTlibrary for update level updatelevel

DBEngine could not locate the DMSUPPORT library that corresponds to the indicated update level. DBEngine first reads the DMSUPPORT file title specified in the DASDL. The default is DMSUPPORT/databasename. It tries to link to DMSUPPORT using the following titles in order until it finds the one with the correct update level and update timestamp:

normalname/updatelevel

updatelevel/normal

normalname

The error indicates that these files do not exist or they have the wrong update level and/or timestamp. To resolve this, find the correct DMSUPPORT library and copy it as normalname/updatelevel or updatelevel/normalname where DBEngine can find it.

0043 DATABridge Engine: Parent of value must be selected

value indicates the name of an embedded data set. This occurs when an accessory tries to use the DBSELECT entry point without first selecting the parent of the embedded data set. To resolve this error, correct the user-written accessory to use DBSELECT for the parent data set first. In the Span Accessory, make sure the parameter file entries for parents precede the corresponding entries for embedded data sets.

0044 DATABridge Engine: DBTWINCONTROL data items are incorrect

The DBTWINCONTROL data set for DATABridge Twin Client must have a certain layout of data items. This error indicates that the data set does not have the proper layout. See the DATABridge Twin Client Administrator’s Guide for more information. (DATABridge Twin is purchased separately.)

0045 DATABridge Engine: Error reading file: value

This error indicates an I/O error on a file. value is the name of the file. Possible reasons are as follows:

If this is a disk file and the error persists, the file may be corrupted. Reload it from a backup and run the accessory again.
If this is COMMPORT, there is a possibility that a network channel was broken. Try rerunning the accessory.

0047 DATABridge Engine: Database must have the INDEPENDENTTRANS option set

This message applies to DATABridge Twin. Modify the DASDL to set INDEPENDENTTRANS to on and then recompile the DASDL. DATABridge Twin supports databases only when the INDEPENDENTTRANS and AUDIT options are set.

0048 DATABridge Engine: Missing audit location information. Please run DBTwin with the LOAD or LOCATION command.

This message applies to DATABridge Twin and indicates that there are no records in the DBTWINCONTROL data set. See the DATABridge Twin Administrator’s Guide.

0049 DATABridge Engine: Missing Database-Stack-Terminate record at end of audit file value_1

This message applies to DATABridge Twin and indicates that DBTwinInitialize could not find the DBST (Database-Stack-Terminate) record at the end of the audit file. value_1 is the audit file name. Make sure the primary database is down before you copy the current audit file to the client system and before you run DBTwinInitialize.

0050 DATABridge Engine: Checksum error on Audit file nnnn ABSN mmmm

DBEngine has detected a checksum error in the audit file number nnnn at audit block serial number mmmm. This indicates that the audit file is corrupted. To resolve this, use COPYAUDIT to reload a valid copy of the audit file from backup.

0051 DATABridge Engine: Internal error: Structure #nnnn not found in SIB

DBEngine could not find the structure indicated by nnnn in the Structure Information Block (SIB) of the database. This is an internal error in DBEngine. Report this to Technical Support.

0052 DATABridge Engine: DESCRIPTION file property level is too old

The database DESCRIPTION file you are trying to read was generated with an old version of DMSII. You must recompile the database with more current DMSII software before you can use DATABridge.

0053 DATABridge Engine: Audit file format Level is too old

The database audit file DATABridge is trying to read was generated with an old version of DMSII. You must recompile the database with more current DMSII software before you can use DATABridge.

0054 DATABridge Engine: DESCRIPTION file property level is value_1 but DATABridge is value_2

The database DESCRIPTION file you are trying to use was generated with a newer version of DMSII than DATABridge was compiled for. DATABridge might continue to work properly or it might not. Contact Technical Support for a newer version of DATABridge.

0055 DATABridge Engine: DESCRIPTION file was compiled with DASDL n.n

This message is displayed with the previous message (0054) for diagnostic purposes. It indicates the SSR of the DASDL compiler that built the DESCRIPTION file.

0056 DATABridge Engine: DATABridge is not qualified on this DMSII release

DATABridge has not been tested using the version of DMSII you have. Contact Technical Support for a newer version of DATABridge.

0057 DATABridge Engine: Internal error: procedurename reference not initialized

This is an internal error in the DBEngine. Report this to Technical Support.

0058 DATABridge Engine: DMUTILITY failed This message applies to DATABridge Twin.

DATABridge Twin tried to run DMUTILITY to initialize a data set but DMUTILITY failed. Contact the database administrator to determine the cause.

0059 DATABridge Engine: Repositioning tape from word value_1 to word value_2

This is an informational message that indicates DBEngine is rewinding the audit tape to an earlier block. On some tape drives, for example, compressing drives, this would normally cause errors because they cannot read backwards or position to an earlier block. DBEngine will rewind the tape and attempt to read forward to the block you want.

0060 DATABridge Engine: Bad current block size in Audit value_1 and SEG value_2

DBEngine attempted to read the next audit block but found an invalid size for the current audit block. This could be the result of a corrupted audit file or an accessory passing an invalid audit location to DBEngine when calling DBSELECT.

value_1 is audit file number.
value_2 is segment number.

To resolve this message, try the following:

If the audit file is corrupted, reload it from backup using COPYAUDIT.
If an accessory passed DBEngine an incorrect audit location, correct the location and rerun the accessory.

0061 DATABridge Engine: Audit file value_1 format level is value_2 but DATABridge is value_3

The database audit file you are trying to use was generated with a newer version of DMSII than DATABridge was compiled for. DATABridge might continue to work properly or it might not. Contact Technical Support for a newer version of DATABridge.

value_1 is audit file number.
value_2 is audit file format level number.
value_3 is audit file format level when DATABridge was compiled.

0062 DATABridge Engine: Audit file was generated with DMSII n.n

This message is displayed with message 0061 for diagnostic purposes. It indicates the SSR of the Accessroutines that wrote the audit file.

0063 DATABridge Engine: Extracting for datasetname

DBEngine has started reading records in datasetname. This is an informational message. If a DATABridge Client fails with this error, either DATABridge can not access a DMSII file or the host database needs to be recompiled.

0064 DATABridge Engine: Reading fixup records

DBEngine completed reading records from the database and is now applying the audit records that were generated during the extract phase. This is an informational message only.

0065 DATABridge Engine: Finished reading fixup records

DBEngine completed reading the audit records generated during the extract phase. This is an informational message.

0066 DATABridge Engine: Audit location: AFN = value_1 ABSN = value_2 (value_3%)

This message applies to DATABridge Twin. It is an information message in response to a AX command to DATABridge Twin and indicates DATABridge Twin’s location in the primary database audit file.

value_1 is audit file number.
value_2 is audit block serial number.
value_3 is percentage of audit file processed.'

0067 DATABridge Engine: Audit time: value_1

This message applies to DATABridge Twin. It is an informational message in response to a AX command to DATABridge Twin and indicates DATABridge Twin’s location in the primary database audit file. value_1 is the timestamp of the audit location.

0068 DATABridge Engine: subtype Create: value_1 Modify: value_2 Delete: value_3

This message applies to DATABridge Twin. It is an informational message in response to a AX STATUS command to DATABridge Twin. It indicates the number of records replicated to the client database.

value_1 is the number of new records.
value_2 is the number of updated records.
value_3 is the number of deleted records.

0069 DATABridge Engine: Waiting for AFN value to become available

DBEngine is waiting for an audit file to become available. Typically this occurs when DBEngine attempts to read an audit file that is in use by the Accessroutines.

0070 DATABridge Engine: Terminating at end of transaction group

This is an informational message that indicates the accessory will stop at the end of the current transaction group. This is in response to an operator request to terminate the accessory (for example, mixnumber AX QUIT to terminate the Span Accessory).

0071 DATABridge Engine: Started timestamp

timestamp indicates when DBEngine started running.

0072 DATABridge Engine: Ended timestamp

timestamp indicates when DBEngine finished running.

0073 DATABridge Engine: Version version compiled timestamp

version indicates the release and patch level of DBEngine and timestamp indicates when DBEngine was compiled.

0074 DATABridge Engine: Filter filtername not found in libraryname

The filter specified by filtername does not exist in the library specified by libraryname. Check the spelling of each and check the library to make sure it actually contains the filter.

0075 DATABridge Engine: datasetname does not have a set

DATABridge Twin requires a set for each data set that is replicated. It continues, however, replicating all of the other data sets that do have sets. If you want DATABridge Twin to replicate datasetname, add a set to that data set in both the primary and secondary databases.

0076 DATABridge Engine: Entry point not supported in TwinEngine. You must have the complete version.

To use this entry point, you must have the DBEngine that is part of the complete DATABridge host release. The accessory you are using is linking to the DBTwinEngine, which is part of the DATABridge Twin release and does not support all of the entry points in the standard DBEngine.

0077 DATABridge Engine: Guardfile missing: value

Check your guardfiles, as explained in the DATABridge Installation Guide.

0078 DATABridge Engine: Unknown NULL type: value

DATABridge does not recognize the NULL type displayed for value. This is an internal error; if it occurs consistently, report it to Technical Support.

0079 DATABridge Engine: Invalid structure number: structurenumber

The structure number you requested is invalid or does not exist. Check your entry and check the DASDL for the correct structure number. You can also use the Lister Accessory report to determine the correct structure number.

0080 DATABridge Engine: Invalid year: year

The year you entered is invalid. Check your entry and the format specified in the parameter file and try again. This message applies to any program (for example, Snapshot Accessory, Span Accessory, and DATABridge Twin) that uses timestamps.

0081 DATABridge Engine: Invalid month: month

The value you entered for months is invalid. Check your entry and the format specified in the parameter file and try again. This message applies to any program (for example, Snapshot Accessory, Span Accessory, and DATABridge Twin) that uses timestamps.

0082 DATABridge Engine: Invalid day: day

The value you entered for days is invalid. Check your entry and the format specified in the parameter file and try again. This message applies to any program (for example, Snapshot Accessory, Span Accessory, and DATABridge Twin) that uses timestamps.

0083 DATABridge Engine: Invalid hour: hour

The value you entered for hours is invalid. Check your entry and the format specified in the parameter file and try again. This message applies to any program (for example, Snapshot Accessory, Span Accessory, and DATABridge Twin) that uses timestamps.

0084 DATABridge Engine: Invalid minute: minute

The value you entered for minutes is invalid. Check your entry and the format specified in the parameter file and try again. This message applies to any program (for example, Snapshot Accessory, Span Accessory, and DATABridge Twin) that uses timestamps.

0085 DATABridge Engine: Invalid second: second

The value you entered for seconds is invalid. Check your entry and the format specified in the parameter file and try again. This message applies to any program (for example, Snapshot Accessory, Span Accessory, and DATABridge Twin) that uses timestamps.

0086 DATABridge Engine: Compile of value_1 failed

An accessory (for example, Span) tried to recompile a tailored Support library because a filter or format had the wrong update level. The compile failed, however, so you must compile the Support library by following the instructions in DATABridge Support Library. After the library is successfully compiled, rerun the accessory.

0087 DATABridge Engine: DESCRIPTION file descriptionfilename is unavailable; Result code: subtype

Check the usercode and pack where the DESCRIPTION file resides and make sure that DBEngine has access to that usercode and pack.

0088 DATABridge Engine: Starting online_or_offline extract

This status message indicates that DBEngine is starting an online or offline extract. This message applies to all Accessories that clone data.

0089 DATABridge Engine: Forcing syncpoint

This status message indicates that DBEngine is forcing a syncpoint to mark the boundary of the fixup phase. If there is a significant delay between this message and a subsequent message, most likely some other program is staying in transaction state too long and preventing the syncpoint from occurring. Correct the other program so that it exits transaction state sooner.

0090 DATABridge Engine: Invalid Property level in parameter file: filename

This message indicates that you have entered an invalid property level in the DBEngine parameter file. The property level must be six digits. See Audit and Property Levels.

0091 DATABridge Engine: Trouble formatting record at AA=address auditlocation

This message indicates a problem in a formatting routine. Specifically, it can occur when the accessory is using BINARYFORMAT and filtering null records (via the DBFilteredNullRecord API). If this message persists, notify Technical Support.

0092 DATABridge Engine: Expected ABSN=nnnn in AUDITnnn at segment nnnn but found ABSN=mmmm

This message indicates a possible audit trail discontinuity, which may result from an unsuccessful repositioning of the accessory after a rollback. See Manual Recovery from a Rollback.

0093 DATABridge Engine: Stopping at task taskname

This status message indicates that Span Accessory, Server Accessory, or DATABridge Twin is stopping at the indicated taskname, based on the task specified for the STOP option. For more information, see one of the following: STOP for the Span Accessory or STOP for the Server Accessory. For DATABridge Twin, see the STOP option in the DATABridge Twin Administrator’s Guide.

0094 DATABridge Engine: Exceeded audit timestamp limit: timestamp

This status message indicates that the Span Accessory, the Server Accessory, or DATABridge Twin is stopping at the indicated timestamp, based on the time specified for the STOP option. For a list of references, see the preceding error message.

0095 DATABridge Engine: Partitioned dataset datasetname is not supported

This release of DATABridge does not support partitioned data sets. If you are using the Snapshot Accessory, comment the data set name in the list of data sets. If you are using the Span Accessory, comment the data set replication status information. If you are using the Server Accessory, turn off cloning for the data set in the client control tables. For a list of DMSII structures supported by DATABridge, see DATABridge Support for DMSII Structure Types.

0096 DATABridge Engine: DBSupport needs to be recompiled

Basically you must recompile DBSupport anytime the DMSII database update level changes. Typically the database update level changes when you reorganize the database. When the Span Accessory and the Server Accessory detect an update level mismatch, they attempt to recompile the support library automatically. If the recompile fails, this message is displayed. You must then recompile the support library manually. To recompile the support library, follow the instructions in the DATABridge Programmer’s Reference.

If you use DATABridge Clients older than version 2.7, this error can occur even after DBSupport is recompiled. Either upgrade you DATABridge Client to the current version or reclone all of the data set tables.

0097 DATABridge Engine: location must be from nnnn to mmmm

location represents a component of an audit location, as follows:

AFN (audit file number)
ABSN (audit block serial number)
INX (index)
SEG (segment)

In this case, an accessory has passed an invalid audit location to DBEngine (during the DBSelect API). Check that the accessory parameter file or client control table contains a value that falls within the range specified by nnnn to mmmm.

0098 DATABridge Engine: subsetname is not a set of datasetname

This message applies to the DATABridge DMSII Client. It can occur if you use the FIND dataset USING subset1, subset 2 . . . option in the DMSII parameter file and one of the subsets listed is not a subset of the data set. Correct the FIND option and rerun the DMSII Client.

0099 DATABridge Engine: value_1 does not allow re-entry

This message can occur when you are using a user-written accessory. It indicates that a DBEngine entry point cannot be called recursively (directly or indirectly). For example, this message could occur if an accessory called the DBDATASETS entry point and passed it a callback routine that in turn called DBDATASETS. When this message occurs, rewrite your accessory so that it does not call entry points recursively.

0100 DATABridge Engine: Incorrect ABSN in block after AFN=auditfilenumber ABSN= auditblockserialnumber

This message indicates a problem in the DMSII audit trail. Each audit block should have an ABSN that is one greater than the previous block. When this message occurs, however, DBEngine has encountered an audit block where this is not true. The most common cause of this problem is failing to remove obsolete audit files after performing a database rollback.

0101 DATABridge Engine: Audit file nnnn corrupted

This message indicates that the file named AUDITnnnn is corrupted and therefore DATABridge cannot read it. To remedy this situation, you may need to rebuild to a previous, uncorrupted audit file.

0102 DATABridge Engine: Incorrect timestamp in audit file AUDITnnnn near ABSN auditblockserialnumber

This message indicates a problem in the DMSII audit trail. Each audit block should have its own timestamp and the timestamp of the previous audit block. When this message occurs, however, DBEngine has encountered an audit block where this is not true. The most common cause of this problem is failing to remove obsolete audit files after performing a database rollback.

0103 DATABridge Engine: Statistics are not available. Compile DATABridge Engine with $ SET STATS

This message indicates an accessory has called the DBStatistics entry point but the DBEngine was not compiled with the $ STATS option. Load the DBEngine code file that was compiled with the $ STATS option and then rerun the accessory.

0104 DATABridge Engine: Filter excluded record

This message indicates the filter rejected the record, that is, the record did not satisfy the filter. Normally, this message is not visible. It is used internally to communicate between the filter and the accessory.

0105 DATABridge Engine: Database update level changed from previousupdatelevel to updatelevel

This message indicates DBEngine or the Span Accessory detected a DMSII database update level that does not affect any DBSelected structures. If you use DATABridge Clients 2.6 or earlier, you must reclone all data tables or upgrade your Client to version 2.7 or later.

0106 DATABridge Engine: Invalid timestamp: hextimestamp

This message indicates that DBSPLITTIMESTAMP detects an invalid timestamp. Correct the specified invalid timestamp.

0107 DATABridge Engine: Invalid processing parameter type nnn

This message indicates that the accessory passed an invalid processing parameter type to the DBParameters entry point. Correct the accessory and run it again. See the list of valid parameter types in SYMBOL/DATABRIDGE/INTERFACE below the comment line "DBPARAMETERS processing parameter types."

0108 DATABridge Engine: Restart dataset is unsuitable for the A Series Client

This message indicates that the restart data set does not meet the criteria listed in the DATABridge Twin Administrator’s Guide. Either modify the layout of the restart data set or add the DBTWINCONTROL data set to your primary database DASDL source. Refer to the DATABridge Twin Administrator’s Guide for more information.

0109 DATABridge Engine: Audit switch wait exceeded maxdelay seconds

This message indicates that the DBAUDITSWITCH has failed and has exceeded the maximum delay retry rate. This problem could also be caused by some other application program remaining in transaction state too long.

0110 DATABridge Engine: Invalid audit medium value: nnnn

This message indicates that the AUDIT ON parameter in either the Span, Server, or Tanker Accessory parameter file is invalid. Enter a valid AUDIT ON parameter into the appropriate parameter file. See the list of valid audit mediums in SYMBOL/DATABRIDGE/INTERFACE below the comment line "DBAuditMedium parameters."

0111 DATABridge Engine: Invalid audit type value: nnnn

This message indicates that an accessory called the DBAuditMedium entry point in DBEngine with an invalid audit type. Correct the audit type value. See the list of valid audit types in SYMBOL/DATABRIDGE/INTERFACE below the comment line "DBAuditMedium parameters."

0112 DATABridge Engine: Port portnumber at server is unavailable reasoncode.

This message indicates that the specified port does not exist or is unavailable. Verify that the SOURCE entry is correct in the accessory's parameter file. The reasoncode is a number indicating the type of open error.

0113 DATABridge Engine: Can’t track datasetname without INDEPENDENTTRANS

This message indicates that the mode of the embedded data set datasetname is one (fixup) or two (normal) and the database does not have the INDEPENDENTTRANS option set. The embedded data set must have a mode of zero. See Chapter 3, “DATABridge Engine Library.”

0114 DATABridge Engine: Program fault

This message indicates that an internal error occurred. Contact Technical Support.

0115 DATABridge Engine: Interface version mismatch: DATABridge Engine = engineversion, accessory: accessoryversion

This message indicates that DBEngine and the interface of the specified accessory are incompatible. Recompile the accessory using the current DATABridge interface file and retry the task.

0116 DATABridge Engine: Unknown filter name: filtername

DBSupport returns this message if the accessory specifies an unknown filter name. Verify the filter names in the accessory’s parameter file.

0117 DATABridge Engine: Invalid AFN in DMSIIcontrolfilename: afn

This message indicates that the AFN in the DMSII CONTROL file is invalid. One possible reason for this error is that the database administrator did a DMCONTROL INITIALIZE on the DMSII CONTROL file and no update programs have been run since then.

0118 DATABridge Engine: Invalid task name: taskname

This message indicates that an accessory supplied an invalid program name to the DBLIMITTASKNAME entry point.

0119 DATABridge Engine: Recovery point not found

This message indicates that the Engine could not find the Rollback or Rebuild point in the audit trail. Consult the Rollback or Rebuild DMSII reports to determine the recovery point.

0120 DATABridge Engine: Database rolled back to AFN=afn ABSN=absn Seg=seg Inx=inx timestamp

This message indicates that DBEngine detected that an accessory supplied an invalid audit location. DBEngine will automatically look for a database rollback (or rebuild) and use it. The accessory should reload its client database as of that point before trying to reprocess. Use the timestamp displayed in this message for the timestamp to specify in the DBSelect call.

0121 DATABridge Engine: Missing transform transformname

DBSupport returns this message if the accessory specifies an unknown transform name. Verify the transform name in the accessory's parameter file.

0122 DATABridge Engine: Setname does not have key data

This message indicates that the specified set does not contain any key data. The DBEngine returns this result in response to a call to the DBKeyDataRemap entry point.

0123 DATABridge Engine: Unable to link to libraryname reason

DBEngine tried to link to the indicated library but was unable to do so because of reason. If this is unexpected and persists, contact Technical Support.

0124 DATABridge Engine: Missing format formatname

The specified format does not exist. Create the format or enter the name of a different format.

0125 DATABridge Engine: GetStatus error: reason

This message describes errors returned from calls to the system GetStatus function.

0126 DATABridge Engine: filename is not a file

This message indicates that the specified filename is actually a directory name.

0127 DATABridge Engine: Error reformatting itemname of datasetname with user value uservalue

This message indicates a problem with the specified reformatting routine. Check the reformatting routine for errors.

0128 DATABridge Engine: Reader-specified dataset datasetname failed VERIFY test for record recordloc in file filenumber

This message occurs when a flat file record returned by a FileXtract Reader library fails the VERIFY test associated with that structure. Correct the FileXtract Reader library or the VERIFY test in the DASDL and then rerun FileXtract. Refer to the DATABridge FileXtract Administrator’s Guide for more information.

0130 DATABridge Engine: Remote DBServer protocol level is ServerLevel but needs to be RequiredLevel

This message indicates that the remote Server Accessory’s protocol level is lower than what is required. The remote system needs to run a newer version of the Server Accessory.

0131 DATABridge Engine: SetStatus error: description command

This message reports an error message returned from the SETSTATUS system function and the attempted command.

0132 DATABridge Engine: virtualds is derived from basedataset, so they must be selected together

The accessory attempted to clone a virtual dataset virtualds without also cloning the dataset basedataset from which it is derived.

0133 DATABridge Engine: Invalid DBSupport title: ‘supporttitle’

The accessory specified an illegal title for the Support Library.

0134 DATABridge Engine: No license for platform product

The DBEngine parameter file does not contain a valid key for running the product on the platform.

0135 DATABridge Engine: License for platform product expired

The DBEngine parameter file contains a key for the product but the license expired on the indicated date.

0136 DATABridge Engine: License for platform product will expire timestamp

The DBEngine parameter file contains a key for the product but the license will expire soon on the indicated date. This is only a warning message.

0137 DATABridge Engine: Invalid audit file prefix: ‘prefix’

The accessory called the DBAuditPrefix entry point with an illegal audit file prefix.

0138 DATABridge Engine: can’t track embeddeddataset because parent records do not have a valid AA

The accessory selected an embedded dataset in fixup or normal mode but the parent dataset does not have record addresses usable for associating an embedded record with its parent record.

0139 DATABridge Engine: Invalid file title: ‘filetitle’

DBEngine encountered an illegal file title for the DMSII DESCRIPTION file.

0140 Invalid AFN: <afn>

The accessory supplied an illegal audit file number. For DMSII audit files, valid audit file numbers range from 1 to 9999.

0901 Invalid filter name: name

The FILTER name specified in the parameter file is not the name of a DBFILTER routine in the Support Library. Either correct the name in the parameter file or use the GenFormat program to define the filter to the Support Library and recompile it. Make sure that you entered the correct library name for the SUPPORT parameter.

0902 Invalid format name: name

The FORMAT name specified in the parameter file is not the name of a DBFORMAT routine in the Support Library. Either correct the name in the parameter file or use the GenFormat program to define the format to the Support Library and recompile it. Make sure that you entered the correct library name for the SUPPORT parameter.

0903 Support SETUP failed; Accessory version = version

The DBSETUP entry point in the Support Library returned an error. Typically, this means one of the following:

You entered an incorrect SUPPORT library title in the parameter file.
The Support Library needs to be recompiled. See Chapter 4, “Support Library.”

0904 Interface version mismatch

DBEngine and the accessory were compiled with different versions of the DATABridge API. Copy the correct version of the DATABridge software and rerun the accessory. If you are running a user-written accessory, recompile it with the correct DBInterface file (SYMBOL/DATABRIDGE/INTERFACE).

0905 Another file opened filename EXCLUSIVE

filename is the name of a parameter file. This message appears when an accessory attempts to access its parameter file and some other program has opened it EXCLUSIVE. Usually this indicates that another copy of the accessory is already running and using the same parameter file. Determine which program has the parameter file opened EXCLUSIVE and either wait for it to finish or manually terminate it. Then, rerun the accessory.

0906 Syntax error in parameter file

This message indicates that there is an error in the parameter file. It is preceded by a more descriptive message indicating the line number and column number of the syntax error.

0907 Missing entry point entrypoint in DBSupport

The accessory tried to use an entry point in DBSupport that was not in the Support Library. Recompile DBSupport or correct the user-written accessory and try again.

0908 Duplicate entry for STR# structurenumber

This message indicates that there is a duplicate structure number (and record type) in the accessory’s parameter file. This is usually the result of a mistake in editing the file. Correct the parameter file and rerun the accessory.

0909 Initialization failed

The accessory detected errors when it tried to initialize. See the accessory’s report file for the specific error message.

0910 Duplicate option (at line nnn): option

Check the following:

Does the parameter file contain a duplicate entry for a SOURCE (for example, two SUPPORT entries)? If so, remove the duplicate entry.
Does the parameter file contain a duplicate entry for a STOP command (for example, two STOP BEFORE commands)?

0911 Parameter file missing

The accessory was unable to find the parameter file. Copy the sample parameter file as the name of the missing file and rerun the accessory.

0912 Invalid time limit=hh:mm

The time you entered for the STOP option is invalid for any of the following reasons:

The value for hours (hh) is outside of the valid range of 0 to 23.
The value for minutes (mm) is outside of the valid range of 0 to 59.

Correct the time and run the accessory again.

0913 Invalid date limit=mm/dd/yyyy

The date you entered for the STOP option is invalid for any of the following reasons:

The day is invalid for the specified month (for example, February 30, September 31)
The month is 0 or greater than 12
The year is between 100 and 1970

Correct the date and run the accessory again.

0914 Invalid number of days = days

The number of days you entered for the STOP option is invalid because it caused the date to be before 1970. Correct the number and run the accessory again.

0915 Time should be 14 digits: time

A data set entry in the parameter file contains a date/time that is not 14 digits long. Enter it using the following syntax: YYYYMMDDhhmmss

0916 Error writing to filename

This message indicates a problem with a WRITE command on one of the accessory’s output files. This problem might be a hardware problem. If the hardware is functioning properly and the error message persists, contact Technical Support.

0917 n Errors in parameter file

The accessory detected n errors in the parameter file. Correct the errors and rerun the accessory.

0918 Line n Error

The parameter file contains an error on line n. Correct the error and rerun the accessory.

0919 Error reading filetitle

The accessory encountered an error while trying to read filetitle.

0921 EOF reading filetitle

The accessory encountered the end-of-file while trying to read filetitle.

0999 Fatal error

The program encountered an error condition that won’t allow it to continue processing. The program will terminate. Some of these conditions include the following:

Syntax error in the parameter file
Software version mismatch
An error during initialization

1001 DBServer: Unable to assume configuration usercode:usercode

The Server Accessory could not use the usercode specified in the Server parameter file. Check both of the following:

Make sure that the Server Accessory has the TASKING privilege. Otherwise, it cannot assume the usercode specified in the Server Accessory parameter file.
Make sure that the usercode specified in the Server parameter file has visibility to the DATA/ENGINE/CONTROL file.

For more information on how the usercode relates to the Server Accessory, see USERCODE.

1002 DBServer: Unable to link to SUPPORTlibrary (reason)

The Server Accessory could not attach to the Support library specified in the Server Accessory parameter file. Either the Support library name is misspelled in the Server Accessory parameter file, or the specified Support Library is missing.

1003-1005 N/A

These numbers are not currently used.

1006 DBServer: Invalid host password

This message indicates that the Server Accessory has a password specified in its parameter file (KEY=password) and that a DATABridge Client user has entered the wrong (or no) password.

1007 DBServer: No default source defined

This message applies to DATABridge 1.0 Clients. It indicates that no default data source is defined in the Server Accessory parameter file. To do this, add the keyword DEFAULT to the SOURCE entry in the Server Accessory parameter file. See SOURCE for information about the SOURCE entry in the Server Accessory parameter file.

1008 DBServer: Data source name required

This message indicates that the Server Accessory parameter file does not contain a data source name. Make an entry for SOURCE in the parameter file.

1009 DBServer: Data source sourcename not found

The data source that a DATABridge Client user specified with the dbutility command does not exist. Check the spelling of the data source name. The data source name must match the entry for SOURCE in the Server Accessory parameter file.

1010 DBServer: Structure structurename is not viewable

This message indicates that a DATABridge Client tried to select one or more data sets, but they are filtered out by the Support Library. Use the Client DEFINE or REDEFINE command to reload the database layout.

1011 DBServer: Interface version (DATABridge Engineversion) mismatch

Server Accessory and DBEngine were compiled with different versions of DBInterface. Copy the correct software from the release tape.

1012 N/A

This number is not currently used.

1013 DBServer: Invalid function requested: functioncode

This message indicates that the Client supplied an invalid function code in its request. If the error persists, contact Technical Support.

1014 DBServer: I/O error on port portnumber: description

Server Accessory encountered an I/O error trying to use the network transport, for example, TCP. The description indicates the type of error. This error is often the result of the DATABridge Client terminating abnormally or the operator terminating the network transport. After correcting the cause of the error, try rerunning the DATABridge Client.

1015 DBServer: Operator terminated Worker

An AX QUIT command was issued to a Worker that was receiving data from an audit file. The Worker will keep the connection open, but return this message and then stop at the end of the current transaction group.

1016 DBServer: Invalid Server option number: number

This message indicates that the client supplied an invalid Server option. Make sure you have the proper version of the host DATABridge software for the Client you are using.

1017 DBServer: Assertion failed @ linenumber

Server Accessory detected an unexpected data value. If this condition persists, report it (including the line number) to Technical Support.

1018 DBServer: Unoffered subport opened: subport

A program such as the DATABridge Client opened a subport of Server Accessory's network transport file that the Server Accessory had not offered for use. This unexpected situation could cause Server Accessory to run more Workers than specified in the parameter file.

1019 DBServer: Invalid FILESTATE at open of transport port [subport] ; description

A program such as the DATABridge Client opened a subport of Server Accessory's network transport file that had a file state other than CLOSED, as indicated by description. This may indicate a network transport problem.

1020 DBServer: Bad port number syntax

The port number configured in the Server Accessory parameter file is greater than 65535. Enter a correct port number and rerun Server Accessory.

1021 DBServer: Subport subport was already open

Server Accessory initiated a duplicate Worker for the subport. If this error persists, contact Technical Support.

1022 DBServer: Parameter file had nnn errors

The Server Accessory parameter file contains errors. Correct the errors and then rerun Server Accessory.

1023 DBServer: Invalid command: command

The AX command you entered is not a valid command. Enter a valid command.

1024 DBServer: Source not found (at line nnn): sourcename

The target source in the SOURCE...LIKE... command (at line number nnn in the Server Accessory parameter file) is invalid. Enter a valid target source. See SOURCE.

1025 DBServer: OPEN error on transport port [subport]: description

Server Accessory encountered an I/O error trying to open the subport of the network transport. The description indicates the type of error.

1026 DBServer: DATABASE must be specified for SOURCE sourcename

The Server Accessory parameter file does not have a valid database specified in the SOURCE option. See SOURCE.

1027 DBServer: PORT or ENDPOINT must be specified

The Server Accessory parameter file did not contain a PORT or ENDPOINT declaration indicating the type of network transport to use. Fix the parameter file and rerun Server Accessory.

1028 DBServer: At least one SOURCE must be specified

You must specify at least one SOURCE entry in the Server Accessory parameter file. See SOURCE.

1029 N/A

This number is not currently used.

1030 DBServer: Invalid file handle: number

Enterprise Server requested a file operation with an invalid handle number.

1031 DBServer: Expected number: text

The operator entered an AX command to Server Accessory that requires a number (for example 1234 AX BUFFER nnn), but instead entered text. Re-enter the AX command with the correct number.

1032 DBServer: Default source already specified (at record nnnnnn): DEFAULT

The Server Accessory parameter file contains more than one SOURCE entry containing the DEFAULT option. Remove the DEFAULT option from all SOURCE entries except one. See SOURCE and SOURCE LIKE.

1033 DBServer: Invalid client host host for source

This message indicates that a Client tried to connect to a SOURCE from a host that was not listed in the HOST declaration. See SOURCE.

1034 DBServer: row rownum of filetitle has I/O errors

The indicated file row (area) is locked out with an I/O error.

1035 DBServer: XDR error @ linenumber

Server Accessory detected invalid (or missing) data in the message to/from the DATABridge Client. Make sure you have compatible versions of the host and Client software. If this message persists, contact Technical Support and be sure to include the Server Accessory line number.

1036 DBServer: Unable to send response @ linenumber

When Server Accessory attempted to send a response message to the DATABridge Client, it received an error. This could be due to an abnormal termination of the Client or a network problem.

1037 DBServer: Read_Callback interrupted by client input

Server Accessory was in the middle of sending the updates in a transaction group when it received an input message from the Client. When this happens, Server Accessory discards the rest of the transaction group and tries to process the input message.

1038 DBServer: Workers can not exceed nn

The message indicates that the number of workers specified in the Server Accessory parameter files is set too high. The maximum number of workers you can set is 20. See WORKERS.

1039 DBServer: No NOTIFY listener at ipaddress port number

This message indicates that DBAuditWait is not listening for notification messages on the indicated port number at the host indicated by ipaddress. Either DBAuditWait is not running or the NOTIFY option in the Server Accessory parameter file is not configured correctly. Configure the NOTIFY option, see NOTIFY.

1040 DBServer: Error sending to NOTIFY listener at ipaddress port number: errortext

This message indicates a network problem sending a message to DBAuditWait using the specified port.

1041 DBServer: Error receiving from NOTIFY listener at ipaddress port number: errortext

This message indicates a network problem reading a message from DBAuditWait at the specified port.

1042 DBServer: NOTIFY listener at ipaddress port number reported: message

DBAuditWait sent on of the following status messages to Server Accessory:

Success
Read error
Incomplete message
Message too long
Source busy
Out of packets
Unknown error

1043 DBServer: File not found: filetitle

The client requested a file that was not found on the host system.

1201 DBSpan: Found task taskname in audit

This informational message indicates that the Span Accessory met the requirements set by the STOP option. It has found the task indicated in the STOP option and will terminate at the next quiet point. See STOP.

1202 DBSpan: Exceeded audit file limit: n

This is an informational message that informs you that the Span Accessory met the requirements set by the STOP option. Span Accessory has processed the number of audit files (n) indicated in the STOP option and will terminate at the next QPT. See STOP.

1203 DBSpan: Exceeded audit timestamp limit: time

This is an informational message that informs you that the Span Accessory met the requirements set by the STOP option. Span Accessory passed the timestamp indicated in the STOP option and will terminate at the next QPT. See STOP.

1204 DBSpan: Encountered record limit: n

This is an informational message that informs you that the Span Accessory met the requirement set by the STOP option. Span Accessory received the number of record updates indicated (n) in the STOP option and will terminate at the next QPT.

1205 DBSpan: Error repositioning filename

This message indicates a problem with a SEEK command on one of the Span Accessory output files. This problem might be a hardware problem. If the hardware is functioning properly and the error message persists, contact Technical Support.

1206 DBSpan: No dataset entries in parameter file

This message indicates that you did not select any data sets to be processed. See step 3 in Running the Span Accessory.

1207 DBSpan: Creating new parameter file filename

This message indicates that the Span Accessory is creating the specified parameter file.

1208 DBSpan: No header in existing file

The Span Accessory parameter file indicates that the output data files will contain a header record showing the starting and ending audit locations contained in the file (see HEADER). Span Accessory tried to read an existing output file’s header record but did not find it. It is likely that the HEADER option was changed to TRUE in the parameter file after the output file was created. If this is the case, transfer the output file to the target system and remove it from the source system so that the Span Accessory does not find it. Then rerun Span Accessory.

1209 DBSpan: Ending location too short in existing file

Although a corrupted output file could cause this problem, it is more likely that the HEADER option was changed to TRUE in the parameter file after the output file was created. If this is the case, transfer the output file to the target system and remove it from the source system so that the Span Accessory does not find it. Then rerun the Span Accessory.

1210 DBSpan: Output file audit location mismatch

This message can occur when the following conditions are true:

HEADER = TRUE in the Span Accessory parameter file
You are running the 2.0 or newer version of the Span Accessory
A Span Accessory UPDATES file is present

In this case, the Span Accessory tried to append data to an existing output data file with HEADER=TRUE but found that the existing file’s header doesn’t match the current audit location. Span Accessory renames the file .../BAD and opens a new data file.

To avoid this message, move any UPDATES files created by a previous version of the Span Accessory before you run the current version. If the current version of the Span Accessory created the existing UPDATES file, then either the Span Accessory parameter file was replaced with an older version, or the UPDATES file was replaced with an older version.

1211 DBSpan: Previous end location = auditlocation

This is an informational message that tells you the audit file location (AFN, ABSN, SEG, and INX) according to the header record in an existing output file from which the Span Accessory will start to gather updates. This message is displayed when there is a conflict between the audit location in the parameter file and the audit location in the header record of an output file.

1212 DBSpan: Current start location = auditlocation

This is an informational message that tells you the audit file location (AFN, ABSN, SEG, and INX) according to the header record in an existing output file. The header record corresponds to the first data record in the output file. This message is displayed when there is a conflict between the audit location in the parameter file and the audit location in the header record of an output file.

1213-1217 N/A

These numbers are not currently used.

1218 DBSpan: No starting location in existing file

The Span Accessory parameter file indicates that the output data files will contain a header record showing the starting and ending audit locations contained in the file (see HEADER). Span Accessory tried to read an existing output file’s header record but did not find the delimiter indicating the starting location. The output file is probably corrupted. Either remove it or replace it from a backup copy. Then rerun the Span Accessory.

1219 DBSpan: No ending location in existing file

The Span Accessory parameter file indicates that the output data files will contain a header record showing the starting and ending audit locations contained in the file (see HEADER). Span Accessory tried to read an existing output file’s header record but did not find the delimiter indicating the ending location. Most likely, the output file is corrupted. Either remove it or replace it from a backup copy.

1220 DBSpan: parameter must be greater than 0. Adjusting to nnn

The Span Accessory parameter file contained a negative value for parameter. Span Accessory automatically adjusts it to nnn.

1221 DBSpan: MAXRECSIZE not file-equated. Using default nnn bytes

This is a warning message. The Span Accessory parameter file says to write a consolidated output file to tape, but the WFL did not specify a MAXRECSIZE for OUTFILE. Tape files must have a fixed record size. Span Accessory will use a MAXRECSIZE of nnn bytes for OUTFILE. Records longer than that will be truncated.

1222 DBSpan: datasetname formatted record size nnn truncated to mmm bytes

This is a warning message. The output file record size specified for datasetname in the Span Accessory parameter file, mmm, is smaller than the size of a formatted record, nnn, for datasetname. The records will be truncated.

1223 DBSpan: datasetname attribute cannot exceed nnn. Adjusting to mmm

The output file record size, block size, or area size for datasetname (or DEFAULT) in the Span Accessory parameter file is larger than the mainframe size limit of nnn and will be changed to mmm.

1301-1303 N/A

These numbers are not currently used.

1304 Snapshot: Invalid number of days=days

The number of days you entered for the STOP option is invalid because it caused the date to be before 1970. Correct the number and run Snapshot again.

1401 DBSupport: Format level mismatch for Str# nnn (Support=supportlevel Audit record =formatlevel)

A DBFORMAT routine in the Support Library was compiled with a different DESCRIPTION file than the one corresponding to the current audit file. Snapshot Accessory, Span Accessory, Server Accessory, and DATABridge Twin will attempt to automatically recompile the support library when this error occurs. If that fails, recompile Support manually. See Support Library.

1402 DBSupport: Format cannot check for numm or invalid data

The accessory set one of the data validation options but the format does not support data validation.

1403 DBSupport: DBSupport has update timestamp supportupdatets but database is dbupdatets

The Support library was compiled against a different database update level and needs to be recompiled.

1404 DBSupport: DBSupport has LINKS option supporttruefalse but current DATABridge Engine parameter file has enginetruefalse

The Support Library was compiled with a different setting for the LINKS option than the current setting in the DBEngine parameter files. Either recompile Support or change the LINKS option in the DBEngine parameter files.

1405 DBSupport: DBSupport database supportdbname [supporttdbts] doesn’t match enginedbname [enginedbts]

The Support Library was compiled against a different database than the one that DBEngine has open. Recompile the Support Library.

1501 DBAuditTimer: CREATIONTIME not returned

AuditTimer tried to get the creation time for an audit file but encountered this error. Notify Technical Support if this error persists.

1502 DBAuditTimer: CREATIONDATE not returned

AuditTimer tried to get the creation date for an audit file but encountered this error. Notify Technical Support if this error persists.

1601-1602 N/A

These numbers are not currently used.

1603 DBGenFormat: Duplicate name: at line nnn

You have used the same name twice (for example, two filters have the same name or a format and a filter have the same name). All declared names in the GenFormat parameter file must be unique. Choose a new name for the duplicated name and rerun the GenFormat program.

1604 DBGenFormat: Translation not defined: translationname at line nnn

The translation table name you entered for a particular FORMAT declaration has not been defined. Check your spelling of the translation table name or create the translation table in the GenFormat parameter file. See Creating and Using Translation Tables.

1605 DBGenFormat: Duplicate definition: optionname at line nnn

This message indicates that you have entered the same option twice in a FORMAT declaration. optionname can be one of the following:

PREFIX
POSTFIX
POSITIVE
NEGATIVE
UNSIGNED
TEXT
BOOLEAN
SEPARATOR
DECIMALPT
PADDING
OVERFLOW
NULL
TRUE
FALSE
FLOAT

In a FORMAT declaration, you can specify each option only once. Remove the duplicate option and rerun the GenFormat program.

1606 DBGenFormat: Variable format type recordtype already specified at line nnn

The specified variable format type recordtype has already been specified. This can occur when you declare a SELECT statement for a variable format data set and specify the same variable-format part twice. Combine or remove the duplicate clauses for the specified recordtype and rerun the GenFormat program.

1607 DBGenFormat: Duplicate SELECT for datasetname at line nnn

Within a FILTER, you have declared multiple SELECT statements referring to the same data set. Each data set can have only one SELECT statement in a FILTER. Combine the duplicate SELECT statements into a single SELECT statement and rerun the GenFormat program.

1608 DBGenFormat: Data item dataitemname not found at line nnn

This message can occur anytime you reference a data item, as in the following examples:

When you declare an ALTER data set
When you declare PRIMARY keys
When you use a SELECT statement in a filter

In all cases, the data items you use in the parameter must have the same name they have in the DASDL or in a preceding ALTER or VIRTUAL data set. Correct the spelling of the data item and rerun the GenFormat program.

1609 DBGenFormat: count errors detected

This message indicates the number of errors the GenFormat program encountered in its parameter file.

1610 N/A

This number is not currently used.

1611 DBGenFormat: OCCURS nnn exceeds the maximum mmm at line rrr

The ALTER or VIRTUAL declaration contains a data item having OCCURS nnn but the limit is mmm. Change the OCCURS to a legal value.

1612 DBGenFormat: Version version compiled compiletime

version indicates the release of the GenFormat program and compiletime indicates when the GenFormat program was compiled. This is an informational message.

1613 DBGenFormat: Warning: Boolean strings truestring and falsestring are different lengths in formatname

The true and false strings must be the same length. This is a warning that the data items following a Boolean will be in different positions depending on whether the data item is true or false. For more information about Boolean values, see Creating a Format.

1614 DBGenFormat: Invalid for non-tailored. Restart compile with database name at line nnn

This message indicates that you referenced a data item in the parameter file. Any time you specify a data set or data item name in a FILTER, ALTER, PRIMARY KEY, etc., declaration, you must create a tailored support library. See Tailoring a Support Library.

1615 DBGenFormat: Name is too long: name at line nnn

The data set or data item name you have entered for an option exceeds the length allowed by DMSII. Currently, data set names are limited to 17 characters and data items names are limited to 30 characters. Correct the spelling of the name and rerun the GenFormat program.

Note: There is no limit on the size of user-declared names for FORMATs, FILTERs, TRANSFORMs, etc.

1616 DBGenFormat: Duplicate KEY for datasetname at line nnn

The parameter file contains two PRIMARY key declarations for the same data set. Each data set can have only one PRIMARY key declaration. Remove the duplicate PRIMARY key declaration and rerun the GenFormat program.

Note: A single PRIMARY key declaration can specify a compound key.

1617 DBGenFormat: Duplicate ALTER: datasetname at line nnn

You have already declared an ALTER statement for the specified data set name. You can use only one ALTER declaration per data set.

1618 DBGenFormat: Can’t ALTER item in occurring group: groupname at line nnn

You cannot convert a data item that is part of an occurring GROUP. Instead, you must convert the entire GROUP. Refer to the DATABridge Programmer’s Reference for ALTER restrictions.

1619 DBGenFormat: Dataset datasetname not found at line nnn

This message can occur anytime you reference a data set, as in the following examples:

When you declare an ALTER data set
When you declare PRIMARY keys
When you use a SELECT statement in a filter

Correct the spelling of the data set and rerun the GenFormat program.

1620 DBGenFormat: Record type recordtype not found at line nnn

The parameter file contains a SELECT statement that references a record type of a data set. The specified record type was not found in the DMSII DESCRIPTION file. Enter a valid record type.

Note: VIRTUAL data sets do not allow variable format records, and variable format records are not referenced in ALTER declarations.

1621 DBGenFormat: ALTERed data item dataitemname not allowed in WHERE clause at line nnn

You are attempting to use a converted data item in a WHERE clause of a SELECT statement in a filter declaration. Refer to the DATABridge Programmer’s Reference for ALTER restrictions.

1622 DBGenFormat: Duplicate structure number number at line nnn

You have used the same structure number for two VIRTUAL declarations. All virtual data sets must have a unique structure number. Also, the structure number for a virtual data set must not match the structure number of an existing, real data set or set. Choose a different structure number and then rerun the GenFormat program.

1623 DBGenFormat: Structure number must be > previous structure numbers: number at line nnn

This message indicates that you have tried to define a virtual data set with a structure number that was not greater than the structure numbers of existing, real data sets and sets and previously defined virtual data sets. Choose a larger structure number.

Guidelines for selecting structure numbers include the following:

Do not use actual DMSII structure numbers.
Once you declare a virtual data set, subsequent data set numbers must be greater than previously declared virtual data sets.
Each structure number must be unique.

Complete details on virtual data set structure numbers are listed in the DATABridge Programmer’s Reference.

1624 DBGenFormat: Duplicate REFORMAT declaration at line nnn

This message indicates that there are duplicate reformat declarations in the GenFormat parameter file. Refer to the DATABridge Programmer’s Reference for REFORMAT restrictions.

1625 DBGenFormat: dataitem original size: nnn but REDEFINE size: mmm at line nnn

This message indicates that the REDEFINE size differs from the original size. The REDEFINE size must be the same as the original size. Refer to the DATABridge Programmer’s Reference for REDEFINE restrictions.

1626 DBGenFormat: REDEFINE of dataitem requires byte-alignment at line nnn

This message indicates that the original data item was not on a byte boundary but the REDEFINE data type requires it to start on a byte boundary (as for GROUP items). Refer to the DATABridge Programmer’s Reference for REDEFINE restrictions.

1627 DBGenFormat: Dataitem in WHERE clause must not have an OCCURS clause: dataitem at line nnn

This message indicates that the specified data item in the WHERE clause has an OCCURS clause, which is not allowed. Refer to the DATABridge Programmer’s Reference for WHERE clause restrictions.

1628 DBGenFormat: subset is not a (sub)set of dataset at line nnn

The USING clause of a SELECT statement refers to a set or subset (subset) that is for another data set. The USING clause must specify a set or subset of data set dataset.

1629 DBGenFormat: non-tailored Support, DBInterface level n

DBGenFormat: Support update level mmm, DBInterface level n

These are informational messages. The first form indicates you are compiling the nontailored (generic) DBSupport. The second form indicates you are compiling a tailored DBSupport using database update level mmm. In both cases, n indicates the DATABridge Interface level number, that is, the value of DBV_VERSION of SYMBOL/DATABRIDGE/INTERFACE.

1630 - 1634 N/A

These numbers are not currently used.

1635 Merged data item dataname is in a different parent group

To merge data items, all of the data items must be in the same parent group.

1636 Merged data item dataname is not adjacent to previous item

The specified data item does not start where the previous data item ends. To merge data items, all of the data items must be adjacent.

1637 VIRTUAL dataset datasetname must have DERIVED FROM datasetlist

The DERIVED FROM clause is missing from the virtual data set declaration in the GenFormat parameter file. (In previous releases, the DERIVED FROM clause was optional.) Add the DERIVED FROM clause to the virtual data set declaration and then recompile the tailored support library.

1638 Filter filtername excludes datasetname, from which virtualdatasetname is derived

A filter includes a virtual dataset but excludes its DERIVED FROM dataset clause. The filter must specify the DERIVED FROM clause.

1800 DBTanker: Duplicate filter name filtername on line linenumber

This message indicates duplicate filter names. The second occurrence of the filter name is found on line linenumber of the parameter file. Remove or rename the duplicate filter. See FILTER.

1801 DBTanker: Couldn’t link to DBSupportname

This message indicates that the Tanker Accessory could not link to the specified tailored support library. See SUPPORT.

1802 DBTanker: No filters in parameter file

This message indicates that you did not specify a filter in the Tanker Accessory parameter file. Specify at least one filter. See FILTER.

1803 DBTanker: Mismatch in output file header of filename

The first record of each filtered audit file contains a header record indicating the size of the header and the size of the UpdateInfo records in the file. The Tanker Accessory has tried to extend an existing filtered audit file but the header record contains incompatible values. This can happen after installing a new release of DATABridge that uses a larger size for the header record or for the UpdateInfo records. Remove or rename the old filtered audit file and let the Tanker Accessory recreate it with the new header record.

1804 DBTanker: Parameter file FAMILY missing

This message indicates that the disk containing the Tanker Accessory parameter file is missing. Either make the disk available or change the location of the parameter file in the WFL.

1900 DBTwin: Please specify a SOURCE rather than CFPRIMARY

This message indicates that you are using an older version of the DBTwin parameter file. Use the current version of the DBTwin parameter file. Refer to the DATABridge Twin Administrator’s Guide.

1901 DBTwin: Option name ignored. Use SOURCE

This message indicates that you are using an older version of the DBTwin parameter file. Use the current version of the DBTwin parameter file. Refer to the DATABridge Twin Administrator’s Guide.

1902 DBTwin: Remote SOURCE cannot have ‘option’

DBTwin is using a Server Accessory source that has a source option DBTwin does not support. Remove the option from the Server Accessory SOURCE declaration.

1903 DBTwin: Remote SOURCE must have ‘option’

DBTwin is using a Server Accessory source that does not have an option that is required for DBTwin. Add the option to the Server Accessory SOURCE declaration.

4001 N/A

This number is not currently used.

4002 DMSIIClient: Unable to connect to port portnumber at hostname: errormessage

The DMSII Client was unable to connect to the specified port. The error message text will explain why the error occurred.

4003 DMSIIClient: Unable to read port portnumber at hostname: errormessage

The DMSII Client was unable to read the specified port. The error message text will explain why the error occurred.

4004 DMSIIClient: Unable to write port portnumber at hostname: errormessage

The DMSII Client was unable to write to the specified port. The error message text will explain why the error occurred.

4005 DMSIIClient: DASDL database compile failed

The DMSII Client was unable to compile the DASDL file because it contains a syntax error. Correct the syntax error in PATCH/DATABRIDGE/DMSIICLIENT/clientdbname/DASDL and then rerun the DMSII Client. Refer to the DATABridge DMSII Client Administrator’s Guide for information about configuring the DMSII Client DASDL settings.

4006 DMSIIClient: Set generation failed

The generation of a SET failed during the clone of the dataset.

4007 DMSIIClient: DBServer protocol level (x) must be at least y

The DMSII Client requires a certain level of RPC protocol indicated by y. However, Server Accessory supports RPC protocol levels up to x. Install a newer version of Server Accessory that supports RPC protocol y or above.

4008 DMSIIClient: ClientLib compile failed

There is an error in compiling the DMSII Client library file. Do not edit SYMBOL/DATABRIDGE/DMSIICLIENT/LIB. Reinstall the DMSII Client software. If the file was not edited and it still gets a syntax error, contact Technical Support.

4009 DMSIIClient: Unable to link to library_name: reason

The DMSII Client was unable to connect to the DMSII Client library. The error message text will explain why the error occurred.

4010 DMSIIClient: DMS Error: errormessage

A DMSII operation failed. Refer to your Unisys DMSII documentation to resolve this error.

4011 DMSIIClient: DMUtility dataset purge failed

DMUtility was unable to initialize the data set. Refer to your Unisys DMSII documentation to resolve this error. Verify that SYSTEM/DMUTILITY is available.

4012 DMSIIClient: Update errors: nnn

This is a summary message indicating nnn errors occurred while the DMSII Client was updating the client database. Check the previously displayed messages. Refer to your DMSII documentation to resolve the error.

4013-4015 N/A

These numbers are not currently used.

4016 DMSIIClient: SYSTEMSTATUS error errornumber

Contact Technical Support.

4017 DMSIIClient: DBServer closed port unexpectedly

Server Accessory closed the network communications port unexpectedly. This could be due to the operator DSing the Worker or a program fault.

4018 DMSIIClient: XDR error at line line#

The DMSII Client detected incorrect data or not enough data in the message it received from Server Accessory or in the message it is trying to send to Server Accessory. Contact Technical Support if this condition persists.

4019 DMSIIClient: Missing filename

The DMSII Client skeleton DASDL file is missing. Refer to the DATABridge DMSII Client Administrator’s Guide.

4020 DMSIIClient: Invalid AX command: invalid_command

There was a syntax error in the AX command you entered. Refer to the DATABridge DMSII Client Administrator’s Guide for valid AX commands.

4021 DMSIIClient: dataset_name not found for DISABLE

An unknown data set was specified in the DISABLE or DISABLE ALL command in the DMSII Client parameter file. Correct the data set name and then rerun the DMSII Client. Refer to the DATABridge DMSII Client Administrator’s Guide.

4022 DMSIIClient: dataset_name is disabled

This error occurs when you include one of the following commands as the second parameter of WFL/DATABRIDGE/DMSIICLIENT and the DMSII Client parameter file says to disable one or more of the data sets that are in [datasetlist]:

UPDATE [datasetlist]
CLONE [datasetlist]
STATUS [datasetlist]

For example, if DATA/DMSIICLIENT/CLIENTDB/CONTROL has: DISABLE BANK, BRANCH, TELLER and then you do: START WFL/DATABRIDGE/DMSIICLIENT ("CLIENTDB", "UPDATE HISTORY, BRANCH") you would get error 4022 because BRANCH is disabled.

4023 DMSIIClient: Expected keyword not token

There is a syntax error in the second parameter of the WFL. Start the DMSII Client WFL with the proper syntax. Refer to the DATABridge DMSII Client Administrator’s Guide.

4024 DMSIIClient: Unknown data set: dataset_name

A data set specified in the second parameter of the WFL does not exist in the client database. Start the DMSII Client with valid data sets in the second parameter of the WFL. Refer to the DATABridge DMSII Client Administrator’s Guide.

4025 DMSIIClient: Invalid port number: portnumber

The PORT command in the DMSII Client parameter file contains an invalid port number. Correct the syntax error and then rerun the DMSII Client. Refer to the DATABridge DMSII Client Administrator’s Guide.

4026 DMSIIClient: Unrecognized command: errormessage

There is a syntax error in the optional second parameter in the WFL command. Rerun the WFL using a valid second parameter. Refer to the DATABridge DMSII Client Administrator’s Guide.

4027 DMSIIClient: Missing insertion point (@) in dasdl_patch_file_name

The at sign (@) was removed from the DMSII Client DASDL file. Re-edit the DASDL file, and then rerun the DMSII Client. Refer to the DATABridge DMSII Client Administrator’s Guide.

4028 DMSIIClient: Duplicate insertion point (@) in dasdl_patch_file_name lines firstlinenbr and secondlinenbr

There is more than one at sign (@) in the DMSII Client DASDL file. Remove one of the at signs and then rerun the DMSII Client. Refer to the DATABridge DMSII Client Administrator’s Guide.

4029 DMSIIClient: Use WFL/DATABRIDGE/DMSIICLIENT/COMPILEDB to compile clientdbname

The DMSII Client has generated the new DASDL for the Client database but the parameter file has the COMPILE = MANUAL option. Start the indicated WFL using a usercode having access to the compilers used in the WFL.

4030 DMSIIClient: Use WFL/DATABRIDGE/DMSIICLIENT/REORGDB to reorganize clientdbname