Skip to content


The install processes specific to Native SQL SPs are similar to those for promotion. The differences being in the (usual) way that install jobs are distributed and scheduled.

Install usually implements a 'promotion cleanup' for executable components. This is based on the concatenated execution environment approach, i.e. once the component has been installed into production then you don't need separate copies it in all the test environments. This is, generally, not appropriate for SPs and we need to leave the promotion/test Db2 alone. Note that ChangeMan ZMF allows for this to be controlled via promotion admin definitions (see details below).

Install skeleton changes

The install mechanism for Stored Procedures (and other Db2 objects such as UDFs and Triggers) has been divorced from CMN20 and implemented as part of CMN21.

Some advantages of this are:

1) Job routing:

Job cards specific to the target Db2 subsystem can be defined for Db2 Bind processing. These are different to the job cards for rest of Promote/Install jobs. Note that LPAR on which the target Db2 runs may be different from the one where the rest of the installation runs.

Refer to panel CMNGD2S1, reached via =A.G.O.2 then 1 - Identify Db2 Physical Subsystems, then select the row desired to update or create the Jobcards.

CMNGD2S1             Db2 Physical Subsystems - Part 2 of 2 
Command ===>  _________________________________________________________________   

Db2 subsystem:  DSN
Site:           U810DP
Load Library:   DSNB10.SDSNLOAD

Job statement information for Db2 binds: 
  //         REGION=0M,TIME=(10)

See also skeleton CMN$$D2J

2) Db2 skeleton variables:

The full range of Db2 variables which may be used in skeletons are only generated if there is a need to generate a CMN21 job (i.e. if there are binds to be done). For a package containing just DDL related components none of these variables are available.