What to bind after a program change

For an overview of the bind process, see The bind process. For an overview of plans and packages, see Plans, packages and dynamic plan exits.

The example in Figure 34 shows a CICS® transaction consisting of four program modules. It is not unusual that the number of modules is high in a real transaction. This section describes what you must do if one module is changed.

Figure 34. Application consisting of four program modules
 Module A is the main module. Module A calls Module B. Module A also calls Module C, and Module C calls Module D.

Assuming that at least one SQL statement changed in program C, you must perform the following steps to prepare the program and to make the transaction executable again:

  1. Precompile the program on DB2®.
  2. Translate the program using the CICS translator.
  3. Compile the host language source statements.
  4. Link-edit.
  5. If the DBRM for program C was bound into a package, bind that package using the new DBRM, and all the application plans that use program C will automatically locate the new package.
  6. If the DBRM for program C was bound directly into any application plans, locate all the application plans that include the DBRM for program C. Bind all the application plans again, using the DBRMs for all the programs directly bound into them, to get new application plans. For the programs that were not changed, use their old DBRMs. Note that you cannot use the REBIND subcommand, because input to REBIND is the plan and not the DBRMs.

If you have not used packages before, note that using packages simplifies the rebinding process. You can bind each separate DBRM as a package and include them in a package list. The package list can be included in a PLAN. You can then use the BIND PACKAGE command to bind the DBRMs for any changed programs, instead of using the BIND PLAN command to bind the whole application plan. This provides increased transaction availability and better performance. See section Using packages for more information on using packages.

Related concepts
Preparing CICS DB2 programs for execution and production
The CICS DB2 test environment
CICS DB2 program preparation steps
Bind options and considerations for programs
CICS DB2 program testing and debugging
Going into production: checklist for CICS DB2 applications
Tuning a CICS application that accesses DB2
[[ Contents Previous Page | Next Page Index ]]