Using one plan for the application

Using one plan for the application gives the greatest flexibility in defining the DB2ENTRYs and DB2TRANs for the application, because the transactions involved can be grouped to better utilize protected threads and optimize thread reuse.

About this task

The steps in converting to this environment are:
  1. Bind all DBRMs for the transactions in the application into packages using a single collection such as COLLAPP1.
  2. Bind a new plan, PLANAPP1, with a package list consisting of a single entry, COLLAPP1.*.
    BIND PLAN (PLANAPP1) ..... PKLIST (COLLAPP1.*) ..
  3. In the DB2ENTRY, replace the dynamic plan exit program name with the name of this new plan. For example, replace:
    PLANEXITNAME=DSNCUEXT
    with
    PLAN=PLANAPP1


dfhtkc0059.html | Timestamp icon Last updated: Monday, 5 June 2017