xbackup and xrestore check for the following errors:
· The tool was called with invalid syntax.
· DBROOT is neither given as an -r or -R parameter nor set in the environment, or it does not point to a valid ADABAS installation directory.
· SERVERDB (or DBNAME) are neither given as a -d parameter nor set in the environment, or they do not identify a valid ADABAS instance.
· ADABAS instance "serverdb" is not running.
· ADABAS instance "serverdb" is not running in cold mode for xrestore.
· The utility task of the ADABAS instance "serverdb" is busy and cannot accept a new session.
· The tool is called by a user who does not have both read and write permission on the files needed by CONTROL.
· The action parameter is not valid.
· The action requires a medium, and none is given (and no default possible).
· The medium given is not defined to CONTROL.
· The file name given as -f parameter does not agree with the CONTROL medium definition.
· The medium is a special medium (e.g., of kind EXTERN, ADSM, FNET, NSR or OMNI), and the action is not allowed for it.
· The medium is of kind "extern", and there is no -f parameter.
· The medium is of kind "extern", and the file name does not identify a named pipe.
· The medium addresses a specific archiver tool (e.g., ADSM, FNET, NSR or OMNI) (see Section External Backup Tools), but the tool (or its client for ADABAS) is not installed on the machine.
· The medium addresses a specific archiver tool (see Section External Backup Tools), and (one of) the pipe(s) is already in use or could not be created.
· The medium addresses a specific archiver tool (see Section External Backup Tools) for a restore operation, but the medium definition has a number of members different from that at backup time, or (one of) the pipe name(s) is different from that at backup time.
· The medium addresses a specific archiver tool (see Section External Backup Tools) for a restore operation, but the tool has no save available, or not all parts of a save are available.
If an error is detected, an explanatory message is written to standard output. These errors are considered fatal, the execution is aborted, and the exit code is non-zero.