Transcription
Errors and Messages GuideDatabridgeversion 6.5
Legal NoticesCopyright 2017 Attachmate Corporation, a Micro Focus company. All Rights Reserved.No part of the documentation materials accompanying this Micro Focus software product may be reproduced, transmitted,transcribed, or translated into any language, in any form by any means, without the written permission of Micro Focus.PatentsThis Micro Focus software is protected by the following U.S. patents: 6983315,7571180, 7836493, 8332489, and 8214884TrademarksMicro Focus, the Micro Focus logo, and Reflection among others, are trademarks or registered trademarks of Micro Focus orits subsidiaries or affiliated companies in the United Kingdom, United States and other countries. RSA Secured and the RSASecured logo are registered trademark of RSA Security Inc. All other trademarks, trade names, or company names referencedherein are used for identification only and are the property of their respective owners.Third-Party NoticesThird-party notices, including copyrights and software license texts, can be found in a 'thirdpartynotices' file located in the rootdirectory of the software.
ContentsAbout This Guide51 Databridge Host and Enterprise Server Messages70000-0899 (DBEngine) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 70900-0999 (Accessories) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 221000-1099 (DBServer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 241100-1199 (DBEnterprise) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 271200-1299 (DBSpan) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 341300-1399 (DBSnapshot) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 361400-1499 (DBSupport) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371500-1599 (DBAuditTimer) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371600-1699 (DBGenFormat) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 371900-1999 (DBTwin) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 414000-4099 (DBDMSIIClient) . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 41Status Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 44Windows Event DBDirector Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 46Databridge Plus Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 482 Databridge Client Messages49Command Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 49Common Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 50Configure Command Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 53Define Command Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 54Redefine Command Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 56Generate Command Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Reorg Command Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 61Process and Clone Commands Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 63Drop and Dropall Commands Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 77Switchaudit Command Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 78Display Command Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Runscript Command Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Unload Command Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 79Reload Command Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 80Refresh Command Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Export Command Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Import Command Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 81Rowcounts Command Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82CreateScripts Command Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 82Tcptest Command Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Databridge Client Console Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 83Client Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 88Usage Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Host Messages That Appear on the Client. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 134Sockets Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 139ODBC Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 140OCI Errors . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 141Client Warnings . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 142Messages Associated with Client Exit Codes . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 166Contents3
3 Databridge Client Manager Service/Daemon Messages169Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 169Error Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 174Windows Application Log Messages . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 181Client Console and Configurator Messages. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1834Databridge Errors and Messages Guide
About This GuideThis guide provides detailed descriptions of the error, status, and log messages that may occur whenusing Databridge.To quickly locate a message in this PDF document, use the Find function (Ctrl F) to search bynumbers or unique keywords in the message.For troubleshooting assistance, see the Administrator's Guide for the product in question.About This Guide5
6Databridge Errors and Messages Guide
1Databridge Host and Enterprise ServerMessages1This section lists error messages generated by the Databridge Host components and DatabridgeEnterprise Server in error number order.Messages may appear on the station running a component linked to DBEngine and in thecomponent's report file. On the MCP server, messages are displayed by the default error handler inDBSupport. Custom error handling routines can help you manage error-prone situations byperforming an action when a particular error is encountered. For example, if Databridge Serverencounters an error while trying to notify a client system, an error handling routine may causeDatabridge Server to retry the notification. For information about creating custom error handlingroutines, see the Databridge Programmer’s Reference.In this Chapter “0000-0899 (DBEngine)” on page 7 “0900-0999 (Accessories)” on page 22 “1000-1099 (DBServer)” on page 24 “1100-1199 (DBEnterprise)” on page 27 “1200-1299 (DBSpan)” on page 34 “1300-1399 (DBSnapshot)” on page 36 “1400-1499 (DBSupport)” on page 37 “1500-1599 (DBAuditTimer)” on page 37 “1600-1699 (DBGenFormat)” on page 37 “1900-1999 (DBTwin)” on page 41 “4000-4099 (DBDMSIIClient)” on page 41 “Status Messages” on page 44 “Windows Event DBDirector Messages” on page 46 “Databridge Plus Messages” on page 480000-0899 (DBEngine)0000 OKThis is a notification that the last call to a DBEngine entry point was completed without error.0001Commit transaction groupThis is a notification that DBEngine encountered the end of a transaction group. The accessoryshould now commit all updates it has received for this group.0002Abort transaction groupDatabridge Host and Enterprise Server Messages7
DBEngine has encountered an indication that the current transaction group was aborted. Theaccessory should discard all updates it has received in this transaction group.0003Caller canceledAn accessory’s callback procedure returned a FALSE, which indicates that it does not want to receiveany more callbacks.0004Invalid database name: nameAn accessory passed an invalid database name to an entry point. Check the input to the accessoryand try again.0005Invalid dataset name: nameAn accessory passed an invalid data set name to an entry point. Check the input to the accessoryand try again.0006Invalid data item name: nameAn accessory passed an invalid data item name to an entry point. Check the input to the accessoryand try again.0007messagewhere message is one of the following messages:"Active (usercode)database audit file afn is unavailable"The audit file is still in use by the Accessroutines. This is normal and indicates that the accessoryshould stop."Active (usercode)database audit file afn 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 afn is an incorrect audit file number"DBEngine was given an AFN less than one or greater than 9999. Check the values that theaccessory passes to DBEngine to make sure they’re not invalid."Another program opened (usercode)database audit file afn EXCLUSIVE"A different program has opened the audit file with the EXCLUSIVE attribute set to TRUE. Rerun theaccessory when that program has finished."(usercode)database Audit file afn was not found"An operator entered a mixnumber NF command to indicate that the audit file is not available. Reloadthe audit file and run the accessory again."(usercode) database Audit file afn missing section"Reload the missing sections of the audit file and run the accessory again."(usercode)database Audit file afn is offline"The audit file is archived offline. Retrieve the audit file, load it, and run the accessory again."(usercode)database Audit file afn is unavailable (no family packname)"The pack that contains the audit file is unavailable. Make the pack ready and rerun the accessory.8Databridge Errors and Messages Guide
"(usercode)database Audit file afn does not exist because the database wasnever updated."The database has never been updated by an application program and no audit files exist. Run anapplication program that updates the database and then rerun the accessory.0008Missing DESCRIPTION file for Audit file update level updatelevelDBEngine cannot find a DMSII DESCRIPTION file that is compatible with the audit file. updatelevelgives the DMSII update level for the audit file. Copy the DESCRIPTION file that has the compatibleupdate level from one of the following backups and rerun the televel/DESCRIPTION/databasenameThis message can also appear when creating the secondary database if the primary database wasdumped before an update program was run following the DASDL update to add theDBTWINCONTROL data set. If so, complete the procedure "Cloning Procedure on the PrimarySystem," in the Databridge Twin Administrator's Guide, starting at step 2.Additionally, make sure that you copied the primary database DESCRIPTION file to the secondaryside before compiling the (modified) secondary database DASDL. If you didn't, copy theDESCRIPTION file and complete "Installing Databridge Twin to the Secondary System," starting atstep 6.0009Audit file afn: Unexpected end-of-fileDBEngine encountered an unexpected end-of-file error while reading the audit file given by afn. Mostlikely the audit file is corrupted. Use COPYAUDIT to reload the audit file from a backup and thenrerun the accessory.0010Data set structurenumber not selectedAn accessory requested information for a data set that it had not previously selected via theDBSELECT entry point. structurenumber is the structure number of the data set that was notpreviously selected. This typically indicates a problem in a user-written accessory. Check the userwritten source code and try again.0011Invalid audit location for datasetname; value 2 must be from value 3 to value 4An accessory tried to select a data set but gave an invalid audit location:datasetnameindicates the data setvalue 2is the name of the audit location component that is invalidvalue 3 and value 4 give the legal range for that componentCheck the input to the accessory. If the accessory is Span, check the Span parameter file to makesure that all of the audit locations have legal values. Correct any illegal values and try again.0012Invalid dataset structure number: structurenumberAn accessory passed an invalid data set structure number to an entry point. structurenumber in thiscase 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 thestructure number.—or—If the accessory specified a logical database, it could be a data set that exists in the physicaldatabase but not in the logical database. In this case, select a different logical or physical database.0013Out of room in array arraynameDatabridge Host and Enterprise Server Messages9
DBEngine was unable to allocate more memory for one of its internal arrays. If this error occursconsistently, report this error to Technical Support.0014Invalid attribute number attrnumThe accessory requested file attribute information but gave an invalid file attribute number.0019No datasets or remaps selectedAn accessory requested updates from DBEngine, but it did not previously select any data sets orremaps.0020 Table reorganization required for datasetname; DMS dataset level updatelevel, Tablelevel clienttablelevelThe DMSII update (format) level for datasetname does not match the update level for thecorresponding 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. Thismessage applies to any accessory that calls the DBREAD entry point in DBEngine.0021Table purge required for clienttablenameThe 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.0022Database timestamp mismatch: Audit file has timestamp, DESCRIPTION file has timestampThe database timestamp in the audit file does not match the database timestamp in theDESCRIPTION file. Find the correct DESCRIPTION file and make it available to Databridge.0023Array is too short: arraynameAn accessory passed an array as a parameter to one of the DBEngine entry points, but the array wasshorter than DBEngine expected. Typically, this error occurs when an accessory is not recompiledwith the current version of the Databridge Interface. Recompile the accessory with the currentDatabridge interface and try again.0024filetitle is not availableDBEngine could not locate the database CONTROL file. Locate the DMSII database CONTROL fileand make it available to Databridge. Make sure you check security access restrictions.0025databasename is not an audited databaseThe requested database is not an audited database. Databridge can use only audited databases.0026modevalue is an invalid mode for datasetnameAn accessory tried to select a data set with an invalid mode value. (The mode value indicateswhether the data set should be cloned, processed normally, etc.) In this case, set the mode to thecorrect value, as follows:Mode 0The data set needs to be cloned.Mode 1The data set is in the fix up phaseMode 2The data set is in the update phaseMode 3The data set was reorganized.Mode 4The data set was purgedThis 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’sGuide, look for ds mode in the client control tables.10Databridge Errors and Messages Guide
0027datasetname does not have a set with a unique keyAn accessory tried to initiate cloning for the data set (indicated by datasetname) which does not havea NO DUPLICATES set. Cloning of certain types of data sets requires a NO DUPLICATES set. Oneoption is to define a primary key for the data set.0028Databridge not initializedThe accessory called an entry point in DBEngine that requires a previous (successful) call ofDBINITIALIZE, which determines the database being replicated. Check your user-written accessoryto make sure you initialize DBEngine before you call any other entry points.0029DMS Error: subtypesubtype contains the text of a DMS error message. Consult your Unisys DMSII manuals for moreinformation on this message.0030Invalid set structure number: numberAn accessory passed an invalid set structure number to an entry point. number in this case is not aset 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 thestructure number.—or—If the accessory specified a logical database, it could be a set that exists in the physical database butnot in the logical database. In this case, select a different logical or physical database.0031Invalid data item number: itemnumber not found in datasetThe accessory passed an invalid data item number to an entry point. The data set does not have adata item with that number. Most likely, the accessory passed the wrong data set and/or item numberto the DBNULL entry point. Correct the user-written accessory. Note that the DBLAYOUT entry pointreturns information about individual data items, including their item numbers.0032Invalid variable format record type number for dataset #structurenumberThe accessory passed an invalid record type number for a variable format data set. Check your userwritten accessory for the variable format record type number. The DBDATASETS andDBDATASETINFO entry points return information about valid record types.0033tablename: Audit location mismatch, subtype value is wrong. Check for DMS rollback.tablename is
This guide provides detailed descriptions of the er ror, status, and log mess ages that may occur when using Databridge. To quickly locate a message in this PDF document, use the Find function (Ctrl F) to search by numbers or unique keywords in the message. For troubleshooting assistance, s
