Intro -- Introduces Development System commands


This section describes use of the standalone commands available in the native SCO OpenServer Development System. Each command is labeled with the letters CP to distinguish it from commands available in the Operating System and other commands within the SCO OpenServer Development System. This convention points users to the documentation set that contains information on a particular command. For example, the reference cc(CP) indicates a reference to a discussion of the cc command in this section; the letter ``C'' stands for ``Command'' and the letter ``P'' stands for ``Programming''.

Other reference sections related to the SCO OpenServer Development System include the CDMT (Custom Distribution Mastering Toolkit) section, the FP (programming file formats) section, the S (system services) section, the ADM (administration) section, and the M (miscellaneous) section. The ADM and M sections contain miscellaneous information, including a great deal of system maintenance information, which may be useful to programming in a UNIX environment.


Unless otherwise noted, commands described in the ``Syntax'' section of a manual page accept options and other arguments according to the following syntax and should be interpreted as explained below. This syntax and the rules which describe it are not followed by all commands, but they indicate what is generally true.

name [-option... ] [cmdarg... ]

[ ]
Surround a syntactic element that is not required.

Indicates multiple occurrences

The command name

letter [arg[,... ]]
An option is always preceded by a ``-''.

Any single letter

A character string that follows a letter in an option.

A path name, filename, any other argument not beginning with a dash (-), or a dash by itself.

Command syntax standard rules


Upon termination, each command returns two status bytes, 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 first byte is 0 for normal termination; the second is customarily 0 for successful execution and non-zero to indicate problems such as erroneous parameters, bad or inaccessible data. The second byte is called variously ``exit code'', ``exit status'', or ``return code'', and is described only where special conventions are involved.


Not all commands adhere to the syntax described here.

See also

getopts(C), exit(S), getopt(S), getopt(C), wait(S)
© 2003 Commands for Programming (CP)
SCO OpenServer Release 5.0.7 -- 11 February 2003