Many Texis programs have standardized exit codes. The following are typical exit codes and what they mean:
User interrupt or signal
The user interrupted the program, e.g. via Ctrl-C or Ctrl-Break.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.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.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.Cannot re-open DDIC
The database could not be re-opened by the monitor.Unknown program
An unknown program name was given to the monitor -c option.Texis Monitor already running
The Texis monitor was explicitly started, but is already running.Invalid license file
The Texis license file (license.key
) is invalid.Schedule server init failed
The Texis monitor's Vortex <schedule>
server could not be started.Named pipe failed
A named pipe could not be opened for statistics collection.Database open failed
The database could not be opened.User/pass failed
The specified user and password were incorrect.Web server init failed
The Texis monitor web server could not be started.No such index
The specified index could not be found, e.g. by chkind
.Table open failed
The database table could not be opened.Index open failed
The specified index could not be opened.Lock open failed
The database locking mechanism could not be opened. May indicate
the system is low on semaphores, or a permission issue.Invalid install dir specified
An invalid Texis install dir was given.Registry set value failed
Windows: the registry could not be updated.Register service failed
Windows: the Texis service could not be registered with the operating
system.Incorrect usage
Command-line syntax or other usage was incorrect.Cannot open input file
An input file could not be opened.Cannot read input file
An input file could not be read.Non-KDBF input file
The input file given to kdbfchk
was not KDBF.Internal error
An internal error occurred.Unknown error
An unknown error occurred.Corrupt input file
An input file was corrupt (e.g. kdbfchk
found problems).Timeout
The Vortex script timed out, i.e. exceeded its <timeout>
.Core dump requested
A core dump was specifically requested, usually for debugging/tracing.cpdb server init failed
The cpdb
server could not be started.Out of memory
Memory could not be allocated.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.Checksum not found in file
No file integrity checksum was found in the file.Cannot exec sub-process
A sub-process or program could not be started.License violation or error
The Texis license has been violated (limit exceeded), or has an error.Secondary error during exit
Another error or signal occurred while exiting from a previous signal.Permission denied
The requested action could not be performed due to permissions.Cannot connect to remote server
A remote server cannot be contacted, e.g. cpdb
cannot contact
the remote cpdb
server.Cannot connect to local server
A local server cannot be contacted, e.g. copydb
cannot contact
the local texisd
server.Cannot write to table
A database table cannot be written to.Cannot open output file
An output file cannot be opened, perhaps due to permissions.Cannot open error log
An error log file (e.g. vortex.log
) cannot be opened.Cannot write to file
A file cannot be written to.Genserver init failed
The genserver
server could not be started or failed.Terminated by signal or event
A signal or event terminated the program, e.g. SIGTERM
on Unix.Floating-point exception
A floating-point exception occurred, i.e. there was a mathematical error.SQL statement failed
A SQL statement could not be executed, e.g. to update the Vortex library.Vortex script compile failed
A Vortex script could not be compiled, perhaps due to a syntax error.Vortex module library action failed
The requested Vortex module library action could not be completed.Cannot rename file
A file cannot be renamed, perhaps due to permissions.Cannot schedule Vortex script
A Vortex script could not be <schedule>
d, perhaps because
the (local) Texis monitor schedule server cannot be contacted.Cannot get config settings
The Texis configuration settings could not be obtained, perhaps
due to permissions or a shared-memory-segment error.Incorrect environment setup
The environment is not set up as expected, i.e. some CGI variables
are not set as expected.Cannot execute Vortex script
A Vortex script could not be executed.No current license
No Texis license was detected running.A newer version of Texis is installed
An already-installed newer version of Texis was detected.Effective user is root
The program is running with root
(Unix administrator) privileges,
which may be unintended or cause problems.cpdb action failed
The requested cpdb
action failed.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.Nothing found in file to patch
The string or expression was not found in the file, so no patch could
be made.Cannot load shared library
A shared library could not be loaded at run time.
Added in version 7.06.1535387860 20180827.Unknown host
A hostname could not be resolved (via DNS or otherwise).
Added in version 8.00.1642183000 20220114.Other fetch error
A 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.