Skip to content

Messages Associated with Client Exit Codes

Exit codes correspond to expected conditions (that is, they are not errors). These messages should be referred to instead of the host messages that often overlap them.

Exit code messages appears at the end of every client run and between restarted dbutility process commands as a result of scheduling or the built-in error recovery loop. This text (exit_code_text) appears in the form “Client exit code: dddd(nnn) - exit_code_text”.

For a list of Client Exit Codes, see Appendix E of the Databridge Client Administrator's Guide.

0000 - Successful
0001 - General error
0002 - Database reorganized
0094 - DBServer STOP TIME limit
0093 - DBServer STOP TASK encountered
1015 - Operator terminated the worker
1135 - Operator terminated DBEnterprise
2001 - Command line usage error
2002 - Client control table error
2003 - Client control table locked
2004 - Client control table load error
2005 - Data source not found error
2006 - Redefine command required
2007 - Could not connect to DBServer
2008 - Invalid data set name
2009 - Invalid ds_mode value
2010 - Create/cleanup error
2011 - Error dropping index
2012 - Bad structure index received from DBServer
2013 - Memory allocation error
2014 - No active structures
2015 - No remaining active structures
2016 - Load error
2017 - Load or index creation error
2018 - Index creation error
2019 - Fixup phase deferred
2020 - Client operations inhibited
2021 - Operator issued quit
2022 - SQL error
2023 - COMMIT TRANSACTION error
2024 - ROLLBACK TRANSACTION error
2025 - AFN limit reached
2026 - EBCDIC-ASCII Library error
2027 - Improperly linked virtual dataset
2028 - Not all virtual dataset sources specified
2029 - Records have been discarded, see log for details
2030 - Database signon error
2031 - Verification count discrepancy
2032 - Generate command required
2033 - Reorg command required
2034 - DMSII reorg caused some AA values to become invalid, add the -y option to the process command to force a reclone
2035 - Aborted clone
2036 - Operator issued abort
2037 - Relational database deadlock
2038 - End of fixup phase for cloned DataSets
2039 - Global working directory not found
2040 - Lock file open error
2041 - Install directory not found
2042 - Redefine command required
2043 - IO error writing script files
2044 - DMSII link improperly setup in control tables
2045 - Reorg script error
2046 - Refresh of stored procedures failed
2047 - Bulk Loader failure
2048 - Missing binary configuration file
2049 - Bad checksum in configuration file
2050 - IO Error reading configuration file
2051 - Configuration file processing error
2053 - Error in writing discard file
2054 - Discard threshold exceeded
2055 - 2056 (Not currently used)
2057 - Wrong value for parameter bcp_decimal_char
2058 - SQL operation cancelled
2059 - Server connection timed out
2060 - Commit CHECKPOINT FREQUENCY parameters are all 0
2061 - Error in loading DLL or finding entry points
2062 - Error in updating control table
2063 - Error creating control table
2064 - Error dropping control table
2065 - Malformed unload file
2066 - Error dropping user table
2067 - Control tables are incompatible with DBConfig, you need to run dbscriptfixup
2068 - Unable to create directory
2069 - Unable to allocate STMT; try reducing the value of aux_stmts
2070 - Error creating file
2071 - User script in error
2072 - Bad DMSII database timestamp
2073 - History table error
2074 - Data source already defined
2075 - Index for user table has too many columns
2076 - Mismatched AFNs in control tables
2077 - Protocol error
2078 - File does not exist
2079 - IO error reading filter file
2080 - Malformed binary filter file
2081 - Bad checksum in binary filter file
2082 - Syntax error in filter source file
2083 - Filter generation failed
2084 - Unsupported table encountered in filter source file
2085 - Data source already exists in relational database
2086 - 2090 (Not currently used
2089 - Database connection lost
2091 - Databridge service failed
2092 - Connection to Server closed by peer
2093 - Connection to Server reset by peer
2094 - Transport error for connection to server
2095 - RPC timeout
2096 - Initialization error
2097 - Error processing RPC data
2098 - Communications or protocol error
2099 - Premature termination of RPC
nnnn - Abnormal termination - see log for details. This message addresses situations other than a host error or any of the preceding exit codes.