Preparing DB2 Application Plans › Generating Application Plans

Generating Application Plans

The application plan definition generates the plan and prepares applications for execution. If you recompile a program that is included directly in the plan, not in a package, and want it to run in static mode, you must regenerate the plan. If the program is included in a package, you must regenerate the package, but it is not necessary to regenerate the plan.

If you regenerate a plan while CICS is active, use the REFRESH PLAN command to make a new copy of the CA Ideal Static I/O modules available to CICS.

For information about the syntax of these commands, see the Command Reference Guide.

Issue the GENERATE PLAN command in batch. The JCL needed for plan generation is in the procedure IDPLAN, which you can use to generate both plans and packages. You must specify the library containing any
non-Ideal DBRMs in the JCL. Following is a sample jobstream:

//name EXEC IDPLAN
//SYSIN DD *
GENERATE PLAN AP3
/*
//

The IDPLAN procedure performs the following steps:

1. Generates CA Ideal Static I/O modules.

2. Precompiles DB2 SQL.

3. Assembles.

4. Link-edits.

5. DB2 BINDs.

If the plan contains any packages, the header information for the package static I/O modules is placed in the first static I/O module generated for the plan. You can bind the plan, even if packages included in the plan were not bound.

If a plan contains only packages, one static I/O module is created for the plan, but it contains only header information for the package static I/O modules, and the global COMMIT, ROLLBACK and SET CURRENT USER statements. The BIND command is generated based on the resources of the plan.

You can transport DB2 applications, package definitions, and plan definitions from the development site to the production site using the CA Ideal transport utilities (see the Working in the Environment Guide). You can transport DBRMs using IBM utilities.

The following diagram illustrates the plan preparation process.

Note: If dynamic SQL is allowed on the plan parameters fill-in, an application or program that would normally run in static mode runs in dynamic mode in the following circumstances:

• When an application with static SQL is executed, it runs in dynamic mode if its plan was not generated using the GENERATE command or the CA Ideal Static I/O modules cannot be loaded.
• If a program from an application with a generated plan is recompiled without re‑executing the GENERATE command, that program runs in dynamic mode while the rest of the application runs in static mode.