Step 1A. Define Scheme for Generating Plan Names and Rebind DBRMs

In a non-COPE IMS system, the plan name used, when an application program is scheduled, is either the same name as the PSB or an alternate name supplied by a RTT table.

Since COPE uses a single PSB to support multiple Logical System (environments) a different mechanism must be used.

COPE uses an Assembler exit named COPESXUX to generate a plan name on the first SQL call from an application program. The exit has access to the real (unmodified by COPE) PSB name and the Logical System name that the application program is executing in. With these tokens it can generate a unique plan name for the application. The simplest approach is to generate a plan that is the same name as the Logical System. All DBRMs for all applications in the Logical System may be bound to one or more collections that are referenced in the PLAN.

If the COPESXUX exit is not used, COPE substitutes a C-number COPE name that is different for each Logical System. This C-number name can be found in Option 4;D;5.

In addition, the COPESXUX exit may associate different DB2 sub-systems with different Logical Systems. This is a supported facility for IMS but application programs must be link edited with different DB2 interface modules containing unique SSID tokens that relate to a specific DB2 subsystem. If the COPESXUX module is used, all versions of application programs may contain the default language interface module and the exit will substitute different SSIDs automatically.

Once the PLAN name protocol is defined, appropriate DB2 collections must be populated, and the defined plans created.