Installing application programs
An application program generally means any user program that uses the CICS® command-level application programming interface (API). To install an application program to run under CICS you must translate and compile your source statements, link-edit the resulting object modules into CICS libraries, and define the program to CICS as a resource.
Procedure
- If your compiler does not translate CICS commands, you
must translate the program source code to turn CICS commands into
calls that are understood by the compiler.
- If your program does not use CICS commands and is invoked only by a running transaction (and never directly by CICS task initiation), you do not need a translator step.
- You must also translate CICS command-level programs that access DL/I services through either the DL/I CALL or EXEC DLI interfaces. Applications that access DB2® services using the EXEC SQL interface need an additional precompilation step.
- Compile your program source to produce object code.
- Link-edit the object module to produce a load module, which you store in an application load library in the DFHRPL or dynamic LIBRARY concatenation. You need additional INCLUDE statements for applications that access DB2 services using the EXEC SQL interface.
- Create resource definitions for any transaction that calls the program, and install them.
- Define the program to CICS as a resource, using one of
the following methods:
- Create a resource definition in the CSD for a single CICS region. See An overview of resource definition.
- Use program autoinstall, so that CICS dynamically generates a resource definition in a single CICS region when the program is loaded. See Autoinstalling programs, map sets, and partition sets.
- Create a resource definition using CICSPlex® SM Business Application Services (BAS). The resource definition can be installed in multiple CICS regions. See Administering BAS.
- Create a resource definition in a standalone CICS bundle using the IBM® CICS Explorer® or IBM Developer for z System z® . The CICS bundle can be installed in multiple CICS regions. See Defining CICS bundles.
- Create a resource definition in a CICS bundle, and package and install the CICS bundle as part of an application deployed on a platform. The application can be installed in multiple CICS regions, and you can install multiple versions of the application at the same time. See Deploying applications to a platform.
- Program installation steps
There are a number of steps that need to be performed to install an application program to run under CICS. - Using dynamic program LIBRARY resources
For an application to run, the load module has to reside in a data set in a CICS load LIBRARY concatenation. - Defining MVS residence and addressing modes
The effect of the MVS™ residence and addressing modes on application programs, how you can change the modes, and how you can make application programs permanently resident, are described. - Running applications in the link pack area
Programs can reside in the link pack area (LPA) provided that they follow certain requirements. - Running application programs in the read-only DSAs
Programs that are eligible to reside above 16 MB, and are read-only, can reside in the CICS extended read-only DSA (ERDSA). Programs that are not eligible to reside above 16 MB, and are read-only, can reside in the CICS read-only DSA (RDSA) below 16 MB. - Using BMS map sets in application programs
The procedure to use BMS map sets in application programs is summarized. - Using the CICS-supplied procedures to install application programs
CICS supplies job control statements (JCL) for translate (if required), compile, and link-edit steps, in separate cataloged procedures for each supported programming language. - Including the CICS-supplied interface modules
If you want to use CPI Communications or SAA® Resource Recovery in your application program then you must make the appropriate interface modules available to your program. - Translating, assembling, and link-editing assembler language application programs
You can use the DFHEITAL or DFHEXTAL procedure to translate, assemble, and link-edit AMODE(24) and AMODE(31) application programs written in assembler language. You can use the DFHEGTAL procedure to translate, assemble, and link-edit AMODE(64) application programs written in assembler language. - Installing COBOL application programs
This diagram shows you the flow of control in the cataloged procedures for COBOL and PL/I programs that require a separate translator step. If you use an integrated translator, there is no separate translator step. The high-level language source and CICS .SDFHLOAD both input to the compiler, and a combined translator and compiler listing is produced. - Installing PL/I application programs
You can use the DFHYxTPL procedures to process PL/I applications with a separate translator. The value of “x” depends on whether it is a CICS application program or an EXCI batch program. Alternatively the DFHZxTPL procedures can be used to invoke the integrated translator. - Installing C application programs
This diagram shows you the flow of control in the DFHYxTzL cataloged procedures for C command-level programs that require a separate translator step. If you use an integrated translator, there is no separate translator step. The high-level language source and CICS .SDFHLOAD both input to the compiler, and a combined translator and compiler listing is produced. - Using your own job streams
You can use the supplied cataloged procedures as a model to write your own JCL to translate, assemble (or compile), and link-edit your application programs.
Related concepts:
Related information:
dfhp3_installprog_intro.html |
Last updated: Monday, 5 June 2017