Exit Codes

Many Texis programs have standardized exit codes. The following are typical exit codes and what they mean:

  • 0 Success.

  • 1 Generic failure.

  • 2 Generic failure.

  • 3 - User interrupt or signal The user interrupted the program, e.g. via Ctrl-C or Ctrl-Break.

  • 4 - Cannot open monitor log The Texis monitor.log file could not be opened, perhaps due to file permissions. This file typically resides in the texis subdir of the install dir.

  • 5 - ABEND The program ended abnormally due to a severe error that could not be recovered from, and possible database corruption may have resulted. Contact tech support for details.

  • 6 - Cannot exec monitor sub-process The Texis monitor program could not be started. The Texis monitor must be running whenever most major Texis programs are run.

  • 7 - Cannot re-open DDIC The database could not be re-opened by the monitor.

  • 8 - Unknown program An unknown program name was given to the monitor -c option.

  • 9 - Texis Monitor already running The Texis monitor was explicitly started, but is already running.

  • 10 - Invalid license file The Texis license file (license.key) is invalid.

  • 11 - Schedule server init failed The Texis monitor's Vortex <schedule> server could not be started.

  • 12 - Named pipe failed A named pipe could not be opened for statistics collection.

  • 13 - Database open failed The database could not be opened.

  • 14 - User/pass failed The specified user and password were incorrect.

  • 15 - Web server init failed The Texis monitor web server could not be started.

  • 16 - No such index The specified index could not be found, e.g. by chkind.

  • 17 - Table open failed The database table could not be opened.

  • 18 - Index open failed The specified index could not be opened.

  • 19 - Lock open failed The database locking mechanism could not be opened. May indicate the system is low on semaphores, or a permission issue.

  • 20 - Invalid install dir specified An invalid Texis install dir was given.

  • 21 - Registry set value failed Windows: the registry could not be updated.

  • 22 - Register service failed Windows: the Texis service could not be registered with the operating system.

  • 23 - Incorrect usage Command-line syntax or other usage was incorrect.

  • 24 - Cannot open input file An input file could not be opened.

  • 25 - Cannot read input file An input file could not be read.

  • 26 - Non-KDBF input file The input file given to kdbfchk was not KDBF.

  • 27 - Internal error An internal error occurred.

  • 28 - Unknown error An unknown error occurred.

  • 29 - Corrupt input file An input file was corrupt (e.g. kdbfchk found problems).

  • 30 - Timeout The Vortex script timed out, i.e. exceeded its <timeout>.

  • 31 - Core dump requested A core dump was specifically requested, usually for debugging/tracing.

  • 32 - cpdb server init failed The cpdb server could not be started.

  • 33 - Out of memory Memory could not be allocated.

  • 34 - Computed checksum differs from file checksum A computed checksum was different than expected. E.g. the file integrity checksum computed by tfchksum was different from that present in the file, indicating the file was modified.

  • 35 - Checksum not found in file No file integrity checksum was found in the file.

  • 36 - Cannot exec sub-process A sub-process or program could not be started.

  • 37 - License violation or error The Texis license has been violated (limit exceeded), or has an error.

  • 38 - Secondary error during exit Another error or signal occurred while exiting from a previous signal.

  • 39 - Permission denied The requested action could not be performed due to permissions.

  • 40 - Cannot connect to remote server A remote server cannot be contacted, e.g. cpdb cannot contact the remote cpdb server.

  • 41 - Cannot connect to local server A local server cannot be contacted, e.g. copydb cannot contact the local texisd server.

  • 42 - Cannot write to table A database table cannot be written to.

  • 43 - Cannot open output file An output file cannot be opened, perhaps due to permissions.

  • 44 - Cannot open error log An error log file (e.g. vortex.log) cannot be opened.

  • 45 - Cannot write to file A file cannot be written to.

  • 46 - Genserver init failed The genserver server could not be started or failed.

  • 47 - Terminated by signal or event A signal or event terminated the program, e.g. SIGTERM on Unix.

  • 48 - Floating-point exception A floating-point exception occurred, i.e. there was a mathematical error.

  • 49 - SQL statement failed A SQL statement could not be executed, e.g. to update the Vortex library.

  • 50 - Vortex script compile failed A Vortex script could not be compiled, perhaps due to a syntax error.

  • 51 - Vortex module library action failed The requested Vortex module library action could not be completed.

  • 52 - Cannot rename file A file cannot be renamed, perhaps due to permissions.

  • 53 - Cannot schedule Vortex script A Vortex script could not be <schedule>d, perhaps because the (local) Texis monitor schedule server cannot be contacted.

  • 54 - Cannot get config settings The Texis configuration settings could not be obtained, perhaps due to permissions or a shared-memory-segment error.

  • 55 - Incorrect environment setup The environment is not set up as expected, i.e. some CGI variables are not set as expected.

  • 56 - Cannot execute Vortex script A Vortex script could not be executed.

  • 57 - No current license No Texis license was detected running.

  • 58 - A newer version of Texis is installed An already-installed newer version of Texis was detected.

  • 59 - Effective user is root The program is running with root (Unix administrator) privileges, which may be unintended or cause problems.

  • 60 - cpdb action failed The requested cpdb action failed.

  • 61 - Cannot write to standard output The program could not print its output, i.e. to the screen or via pipe to another program. This may occur when a parent program has terminated it.

  • 62 - Nothing found in file to patch The string or expression was not found in the file, so no patch could be made.

Copyright © Thunderstone Software     Last updated: Dec 10 2018
Copyright © 2019 Thunderstone Software LLC. All rights reserved.