Appendix E: Client Exit Codes

If the DATABridge Client terminates with an error, an exit code appears in the last_run_status column of the DATASOURCES Client control table. The value 9999 indicates that the last run status is no longer available (typically when dbutility is running). These status messages apply only to the process and clone commands.

The Client exit codes are as follows:

Note: On UNIX, exit statuses are restricted to 8 bits (a range of 0 to 255). The Client uses the exit status specified in the 8-bit Exit code column instead of the actual code, which is longer than 8 bits. This only affects shell scripts that test the exit status.

Exit Code	8-bit Exit Code	Description
2001	150	Indicates an error in the command line when invoking the Client.
2002	151	The control table check failed. This means one of two things—either the Client control tables do not exist, or they are not the right version. In the latter case, the Client issues a control table version mismatch error and suggests that you run the dbfixup program.
2003	152	The data source is locked, indicating that a Client is currently running. If you try to run a process or clone command, while there is a DBClient process command running, the run will return this exit code. The -u option will not work in this situation; you must wait for the run to finish. If the run hangs, you can release the data source lock by terminating the run.
2004	153	An error occurred while loading the control tables.
2005	154	The data source specified on the command line does not exist in the DATASOURCES table.
2006	155	The process or clone command failed because the DS_Needs_Redefining(8) bit in the status_bits column was set for an active data set. This status indicates that normal operations can only be resumed after a redefine command is executed.
2007	156	The Client could not connect to the DATABridge Server or to DATABridge Enterprise Server either during initialization or data transmission.
2008	157	The clone command failed because one of the data set names specified on the command line is invalid.
2009	158	A data set has an invalid value in the ds_mode column of DATASETS. Any other value causes the Client to abend with this exit code.
2010	159	An error occurred while creating or cleaning up a data table at the start of the data extraction phase of a process or clone command.
2011	160	An error occurred while dropping the index of a data table at the start of the data extraction phase of a process or clone command.
2012	161	A bad structure index was received.
2013	162	A system error occurred while attempting to allocate memory.
2014	163	No active structures were found at the start of a process or clone command.
2015	164	No active structures remain after a structure was deselected during a process or clone command.
2016	165	The Client is stopping at the start of the fixup phase because errors occurred during data extraction.
2017	166	The Client is stopping at the start of the fixup phase because errors occurred during data extraction and index creation.
2018	167	The Client is stopping at the start of the fixup phase because errors occurred during index creation.
2019	168	The Client is stopping at the start of the fixup phase because of the defer_fixup_phase parameter setting (or -c option).
2020	169	Client operations are being inhibited by the stop_time settings. You can override this situation by specifying the -o option on the command line. The applies only to the command line client (dbutility).
2021	170	The console operator issued a QUIT command, which stops the Client at the next quiet point. If you stop the Client using a DBServer AX QUIT command for the worker or an Enterprise Server Quit command, a different exit code results (1015 for DBServer) and (1135 for Enterprise Server).
2022	171	The Client encountered a SQL error while updating the control tables. Note: Some SQL errors generate an exit code of 2099.
2023	172	An error occurred while executing a COMMIT TRANSACTION for the relational database.
2024	173	An error occurred while executing a ROLLBACK TRANSACTION for the relational database.
2025	174	The Client is stopping because it finished processing the audit file specified in the stop_afn column of the DATASOURCES tables. You can do one of the following: Specify the stop AFN using the "-F <afn>" command line option. Use the Stop After AFN command from the command line or the Client Console.
2026	175	An error occurred in the EBCDIC to ASCII translation.
2027	176	The command terminated because the Client encountered improperly linked virtual data sets while loading the control tables. This status applies only when the configuration file parameter automate_virtuals is set to True.
2028	177	The clone command terminated because the operator tried to reclone a data set that is the primary source for the virtual data set without recloning the data set that is the secondary source for the virtual data set. This status only applies when the configuration file parameter automate_virtuals is set to True. For example, if the data sets SV-HISTORY (primary source) and SAVINGS (secondary source) provide input to the virtual data set SV-HISTORY-REMAP, you must reclone SAVINGS when you reclone SV-HISTORY.
2029	178	The Client discarded records during audit processing. Any other fatal error or reorganization indication overrides this exit code.
2030	179	The Client was unable to sign on to the relational database. To find the cause, locate the corresponding OCI Error in the log file or the log output.
2031	180	The process or clone command failed because some records were not loaded during the data extraction phase. When the verify_bulk_load parameter is set to 2, the client compares the number of records loaded to the actual count of records in the table. If these do not match, the program fails with this exit code. If the verify_bulk_load parameter is set to 1, the program doesn't fail and errors are reflected in the final exit code, unless a more serious error occurs and overrides this exit code.
2032	181	The process or clone command failed because the DS_Needs_Generating(4) bit in the status_bits column was set for an active data set. This status indicates that normal operations can only be resumed after a generate command is executed. You can also get this exit code from a redefine command when a generate command is required to create scripts for tables in the relational database that were affected by a DMSII reorganization.
2033	182	You need to run a reorg command before resuming normal processing. You will get this exit code from a redefine command when a reorg command is needed to alter tables in the relational database affected by a DMSII reorganization. Note that a reorg command implicitly does a generate command.
2034	183	The Client stopped because a DMSII garbage collection reorganization that affects one or more datasets was encountered during audit file processing and the configuration parameter stop_after_gc_reorg was set to True.
2035	184	A clone was aborted by Enterprise Server and the operation was never restarted. This is a special case of a failed clone.
2036	185	The operator issued a dbutility QUIT NOW command or an abort command from the Client Console, which stopped the Client by closing the TCP connection to the server.
2037	186	A relational database deadlock was detected. This error causes the client to exit. When using dbutility, the program tries to restart the process command 3 times before exiting. When using DBClient, the service automatically retries the process command, as specified by the Error Recovery parameters set for the data source in the service configuration file.
2038	187	The Client is stopping at the end of the fixup phase because of the stop_after_fixup parameter setting. You can resume processing by issuing another process command when you are ready.
2039	188	The Client is unable to continue because the global working directory specified in the Windows registry or in the UNIX file /etc/Attachmate/DATABridge/globalprofile.ini cannot be found. Even if you do not use the service, before you can run the Client, the working directory (which includes the locks subdirectory) must be created .
2040	189	The Client encountered an error when trying to open the lock file for the data source. Look at the log file or the log output to determine the nature of the error, which might be security related. You must always run the Client using the same user. Failure to do so can result in this error, particularly on Windows Server 2008 and UNIX.
2041	190	The DATABridge Client for Microsoft SQL Server is unable to continue because the install directory specified in the Windows registry cannot be found. Reinstall the Client using the installer so that the Client can access this directory (and the bcp_auditor program) without having to use the full path. Copying the files from the DVD will result in this exit code.
2042	191	The Client command failed because the DS_Needs_Mapping(1) or the DS_Needs_Remapping(4) bit in the status_bits column was set for an active data set. This exit code indicates that normal operations can only be resumed after a redefine command is executed. You would typically get this status if you try to run a process or generate command after an error occurs when using the Client Configurator. You need to rerun the Client Configurator to fix the problem.
2043	192	A file IO error caused the Client to terminate.
2044	193	A DMSII link is improperly set up in the control tables.
2045	194	Reorg command script in error.
2046	195	Attempt to refresh stored procedure failed.
2047	196	The Client abended because of one or more bulk loader errors.
2048	197	The client did not find a binary configuration file. The DBClient and DBClntCfgServer programs get this exit status when the configuration file is not binary.
2049	198	This indicates that an I/O error occurred while reading the configuration file. For details, see error messages in the log.
2050	199	The computed checksum does not match the value in the binary configuration file. This error occurs if you try to patch the file using a hex editor. Use the export command, edit the exported configuration file, and then import it.
2051	200	This exit status indicates that errors were found while processing a text configuration file. See the log file for details.
2092	242	The connection to the DATABridge Server was closed by the host or Enterprise Server system. The client is forced to exit. This indicates that the server closed the connection because of an operator command. This exit code indicates that the connection was closed in an orderly manner.
2093	243	The connection to the DATABridge Server was reset by the host or Enterprise Server system. The Client is forced to exit. This exit code indicates that the server was forcibly terminated or that it crashed.
2099	248	This code indicates an internal error. This code is used for all errors that cause the DBREAD and DBWAIT callback routine to terminate prematurely.

Note: For more detailed information on how exit codes are used in custom programs to automate control of DATABridge operations, see dbutility Exit Status Values.