z/OS V1R9.0 UNIX System Services Command ... - Christian Grothoff

The parameters of the compiler invocation command can be names of input files,
compiler options, and linkage-editor options. Compiler options perform a wide
variety of functions such as setting compiler characteristics, describing object code
and compiler output to be produced, and performing some preprocessor functions.
To compile without binding, use the -c compiler option. The -c option stops the
compiler after compilation is completed and produces as output, an object file
file_name.o for each file_name.c input source file, unless the -o option was used
to specify a different object filename. The binder is not invoked. You can bind the
object files later using the invocation command, specifying the object files without
the -c option.
Notes:
xlc and xlC
1. Any object files produced from an earlier compilation with the same name as
expected object files in this compilation are deleted as part of the compilation
process, even if new object files are not produced.
2. By default, the invocation command calls both the compiler and the binder. It
passes binder options to the binder. Consequently, the invocation commands
also accept all binder options.
Invoking the binder
All invocation commands invoke the binder using the c89 utility, so all binder
options must follow the syntax supported by the c89 utility. Standard libraries
required to bind your program are controlled by the sysobj, syslib, and exportlist
attributes in the configuration file.
The specified object files are processed by the binder to create one executable file.
Invoking the compiler with one of the invocation commands, automatically calls the
binder unless you specify one of the following compiler options: -E, -c, -P,
-qsyntaxonly, -qpponly, or -#.
All input and output files supported by the c89 utility are valid for all invocation
commands.
Supported options
In addition to -W syntax for specifying keyword options, the xlc utility supports AIX
-q options syntax and several new flag options.
–q options syntax
The following principles apply to the use of z/OS option names with -q syntax:
v Any valid abbreviation of a z/OS option name that matches (in full or in part) the
spelling of the corresponding option on AIX, can be specified using -q syntax. For
example, ATTRIBUTE can be specified as -qatt, -qattr, -qattri, -qattrib,
-qattribu, -qattribut, and -qattribute. This is true even if the AIX option name is
longer, as in the case of -qbitfields, which can be specified as -qbitf, -qbitfi,
-qbitfie, -qbitfiel, -qbitfield, and -qbitfields. This is the common case that
applies to most z/OS options.
v Any z/OS-specific option name and its valid abbreviation can also be specified
using -q syntax; for example, DBRMLIB.
v Any z/OS option name that has a different spelling from the corresponding AIX
option name can not be specified using -q syntax. For example, CHECKOUT,
EXH, ILP32, LP64, SSCOMM, and TEST can not be specified using -q syntax.
Instead use, -qinfo, -qeh, -q32, -q64, -qcpluscmt, and -qdebug=format=isd.
For historical reasons, OBJECTMODEL and PHASEID are exceptions to this
Chapter 2. Shell command descriptions 807