The following steps are required to install application programs to run
under CICS®. For detailed information about using the CICS-supplied procedures
to install application programs, see Using the CICS-supplied procedures to install application programs.
To use your own JCL to install application programs, see Using your own job streams.
- Compile your program source if you are using a compiler with an integrated
translator.
- If your compiler does not translate CICS commands, you will need to translate
the program source code, turning CICS commands into calls that are understood
by the compiler, then compile or assemble the translator output to produce
object code.
Notes:
- If your program does not use CICS commands and is only invoked by a running
transaction (and never directly by CICS task initiation), no translator step
is needed.
- CICS command-level programs that access DL/I services through either the
DL/I CALL or EXEC DLI interfaces must also be translated. Applications that access DB2® services using the EXEC SQL interface need an additional
precompilation step. For information about this step, see the CICS DB2 Guide.
- Link-edit the object module to produce a load module, which you store
in an application load library that is concatenated to the DFHRPL DD statement
of the CICS startup job stream. Additional INCLUDE statements are required
for applications that access DB2 services using the EXEC SQL interface. For
information about these extra statements, see the CICS DB2 Guide.
- Create resource definition entries, in the CSD, for any transaction that
calls the program, and install them.
- Do one of the following:
- If you are using program autoinstall, ensure that the autoinstall user-replaceable
module can correctly install a resource definition for the program.
- If you are not using program autoinstall, create a resource definition
entry in the CSD for the program, and install it.
References to the CSA or to the TCA are not allowed. You can specify YES
for the system initialization parameter DISMACP to cause CICS to disable any
transaction whose program invokes an obsolete CICS macro or references the
CSA or the TCA.
CICS provides a utility
program, DFHMSCAN, to identify the macro-level programs used by your CICS
applications. For information about using the DFHMSCAN utility to identify
macro-level programs, see theCICS Operations and Utilities Guide.
Consider these points when installing application programs.
[[ Contents Previous Page | Next Page Index ]]