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.
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:
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.