Chapter Contents |
Previous |
Next |
SAS/C Cross-Platform Compiler and C++ Development System User's Guide, Release 6.50 |
The SAS/C CICS
Command Preprocessor can be invoked either directly or by the
sascc370
or
sasCC370
compiler driver.
Invoking ccp Directly |
The following syntax is used to invoke
ccp
directly:
ccp [options] in_file.ccp
The options that may be used are described in Option Descriptions .
The
in_file.ccp specifies the name of the input file. By default, the name of the output file will be the input filename with a
.c
suffix, unless the
-o
option is used.
Using sascc370 or sasCC370 to Invoke ccp Automatically |
If your source file suffix is
.ccp
, the compiler driver uses the
ccp
command to translate any CICS commands. The
ccp
command is invoked and the output is compiled, with either the C or C++ compiler. For example, the following command could be entered to compile the file named
myfile.ccp
:
sascc370 -Tcics370 -Krent myfile.ccp
In this case,
myfile.ccp
is preprocessed for CICS commands. The resulting file is compiled with the C compiler and linked with the CICS target libraries to produce
a.out
.
sasCC370 -Tcicsvse -Krent myfile.ccp
In this case,
myfile.ccp
is preprocessed for CICS commands. The resulting file is compiled with the C++ compiler and linked with the CICS VSE library to produce
a.out
.
To pass options to the CICS preprocessor during compilation with
sascc370
or
sasCC370
, specify the compilation phase prefix,
-WP
, followed by the CICS option. For example, this command compiles
myfile.cpp
and passes the CICS
-d
option to the CICS preprocessor:
sascc370 -Tcics370 -WP,-d myfile.ccp
The options that may be used are described in the section Option Descriptions .
Linking CICS Preprocessed Files |
You must use the
-Tcics370
or
-Tcicsvse
options on the compiler driver to cause
cool
to use the CICS or CICS VSE target libraries. However, if you are using the CICS external call interface (
-x
option), you should link with the standard resident library,
STDOBJ
, instead of the CICS libraries.
Note: When you use
cool
to link a CICS application, you will receive warnings about unresolved references to the following:
DFHEI1
,
DFHEAI
, and
DFHAI0
. These warning messages
are expected. The output object file from
cool
must subsequently be moved to the target mainframe and linked with the CICS Execution Interface stubs.
Note: For CICS, use of the
-Aclet
option is not necessary when you use
-Tcicsxxx
. However, use of one of the compiler options
-Krent
or
-Krentext
is necessary for CICS programs. See the section on compiling SAS/C programs for CICS under MVS/TSO in the SAS/C CICS User's Guide for more
information.
Chapter Contents |
Previous |
Next |
Top of Page |
Copyright © 1998 by SAS Institute Inc., Cary, NC, USA. All rights reserved.