4000-4099 (DBDMSIIClient)

The DMSII Client can generate the following errors.

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, DATABridge Server supports RPC protocol levels up to x. Install a newer version of DATABridge Server 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

DATABridge Server 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 DATABridge Server or in the message it is trying to send to DATABridge Server. 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

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.