INTRO(CP) XENIX System V INTRO(CP)
Name
intro - Introduces XENIX Development System commands.
Description
This section describes use of the individual commands
available in the XENIX Development System. Each individual
command is labeled with the letters CP to distinguish it
from commands available in the XENIX Operating and Text
Processing Systems. These letters are used for easy
reference from other documentation. For example, the
reference cc(CP) indicates a reference to a discussion of
the cc command in this section, where the letter ``C''
stands for ``Command'' and the letter ``P'' stands for
``Programming''.
Syntax
Unless otherwise noted, commands described in this section
accept options and other arguments according to the
following syntax:
name [options] [cmdarg]
where:
name The filename or pathname of an executable file
option A single letter representing a command option.
By convention, most options are preceded with a
dash. Option letters can sometimes be grouped
together as in -abcd or alternatively they are
specified individually as in -a -b -c -d . The
method of specifying options depends on the
syntax of the individual command. In the
latter method of specifying options, arguments
can be given to the options. For example, the
-f option for many commands often takes a
following filename argument.
cmdarg A pathname or other command argument not
beginning with a dash. It may also be a dash
alone by itself indicating the standard input.
See Also
getopt(C), getopt(S)
Diagnostics
Upon termination, each command returns 2 bytes of status,
one supplied by the system and giving the cause for
termination, and (in the case of ``normal'' termination) one
supplied by the program (see wait(S) and exit(S)). The
former byte is 0 for normal termination; the latter is
customarily 0 for successful execution and nonzero to
Page 1 (printed 8/7/87)
INTRO(CP) XENIX System V INTRO(CP)
indicate troubles such as erroneous parameters, or bad or
inaccessible data. It is called variously ``exit code'',
``exit status'', or ``return code'', and is described only
where special conventions are involved.
Notes
Not all commands adhere to the above syntax.
Page 2 (printed 8/7/87)