Many Texis programs have standardized exit codes. The following are typical exit codes and what they mean:
User interrupt or signalThe user interrupted the program, e.g. via Ctrl-C or Ctrl-Break.
Cannot open monitor logThe Texis
monitor.logfile could not be opened, perhaps due to file permissions. This file typically resides in the
texissubdir of the install dir.
ABENDThe 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.
Cannot exec monitor sub-processThe Texis monitor program could not be started. The Texis monitor must be running whenever most major Texis programs are run.
Cannot re-open DDICThe database could not be re-opened by the monitor.
Unknown programAn unknown program name was given to the monitor -c option.
Texis Monitor already runningThe Texis monitor was explicitly started, but is already running.
Invalid license fileThe Texis license file (
license.key) is invalid.
Schedule server init failedThe Texis monitor's Vortex
<schedule>server could not be started.
Named pipe failedA named pipe could not be opened for statistics collection.
Database open failedThe database could not be opened.
User/pass failedThe specified user and password were incorrect.
Web server init failedThe Texis monitor web server could not be started.
No such indexThe specified index could not be found, e.g. by
Table open failedThe database table could not be opened.
Index open failedThe specified index could not be opened.
Lock open failedThe database locking mechanism could not be opened. May indicate the system is low on semaphores, or a permission issue.
Invalid install dir specifiedAn invalid Texis install dir was given.
Registry set value failedWindows: the registry could not be updated.
Register service failedWindows: the Texis service could not be registered with the operating system.
Incorrect usageCommand-line syntax or other usage was incorrect.
Cannot open input fileAn input file could not be opened.
Cannot read input fileAn input file could not be read.
Non-KDBF input fileThe input file given to
kdbfchkwas not KDBF.
Internal errorAn internal error occurred.
Unknown errorAn unknown error occurred.
Corrupt input fileAn input file was corrupt (e.g.
TimeoutThe Vortex script timed out, i.e. exceeded its
Core dump requestedA core dump was specifically requested, usually for debugging/tracing.
cpdb server init failedThe
cpdbserver could not be started.
Out of memoryMemory could not be allocated.
Computed checksum differs from file checksumA computed checksum was different than expected. E.g. the file integrity checksum computed by
tfchksumwas different from that present in the file, indicating the file was modified.
Checksum not found in fileNo file integrity checksum was found in the file.
Cannot exec sub-processA sub-process or program could not be started.
License violation or errorThe Texis license has been violated (limit exceeded), or has an error.
Secondary error during exitAnother error or signal occurred while exiting from a previous signal.
Permission deniedThe requested action could not be performed due to permissions.
Cannot connect to remote serverA remote server cannot be contacted, e.g.
cpdbcannot contact the remote
Cannot connect to local serverA local server cannot be contacted, e.g.
copydbcannot contact the local
Cannot write to tableA database table cannot be written to.
Cannot open output fileAn output file cannot be opened, perhaps due to permissions.
Cannot open error logAn error log file (e.g.
vortex.log) cannot be opened.
Cannot write to fileA file cannot be written to.
Genserver init failedThe
genserverserver could not be started or failed.
Terminated by signal or eventA signal or event terminated the program, e.g.
Floating-point exceptionA floating-point exception occurred, i.e. there was a mathematical error.
SQL statement failedA SQL statement could not be executed, e.g. to update the Vortex library.
Vortex script compile failedA Vortex script could not be compiled, perhaps due to a syntax error.
Vortex module library action failedThe requested Vortex module library action could not be completed.
Cannot rename fileA file cannot be renamed, perhaps due to permissions.
Cannot schedule Vortex scriptA Vortex script could not be
<schedule>d, perhaps because the (local) Texis monitor schedule server cannot be contacted.
Cannot get config settingsThe Texis configuration settings could not be obtained, perhaps due to permissions or a shared-memory-segment error.
Incorrect environment setupThe environment is not set up as expected, i.e. some CGI variables are not set as expected.
Cannot execute Vortex scriptA Vortex script could not be executed.
No current licenseNo Texis license was detected running.
A newer version of Texis is installedAn already-installed newer version of Texis was detected.
Effective user is rootThe program is running with
root(Unix administrator) privileges, which may be unintended or cause problems.
cpdb action failedThe requested
Cannot write to standard outputThe 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.
Nothing found in file to patchThe string or expression was not found in the file, so no patch could be made.
Cannot load shared libraryA shared library could not be loaded at run time. Added in version 7.06.1535387860 20180827.
Unknown hostA hostname could not be resolved (via DNS or otherwise). Added in version 8.00.1642183000 20220114.
Other fetch errorA fetch error occurred, other than specific ones mapped above such as timeout, cannot connect, cannot read/write file, out of memory, incorrect usage, unknown/internal error, cannot load shared library, or unknown host. Added in version 8.00.1642183000 20220114.