Configuration

Update Skeletons

The SAMP members WZU@DB2, WZU@DB2B, and WZU@BLD would have been customized in the SITE Application.

M.ER

Define M.ER Variables DB2PKG, DB2PKVDK, and DB2PKVIK. Refresh the server.

M.AD(L)

Once the interface is turned on, specification of the pre-compile version format must be done in M.AD(L) as shown in the following figure.

Specifying Pre-compile Version Format in M.AD(L)

The following table lists valid values for the Package Management fields and their meanings.

Package Management Values and Descriptions

Housekeeping Job

The SAMP member WZU@PKGH contains JCL to call the routine WZU@DB2F to free the Db2 Packages. This needs to be customized and made available for use. A copy of this JOB can be made which calls WZU@DB2V instead of WZU@DB2F. This copy will be useful in testing whether the interface is set up and working correctly.

Pre-compile Process

A new ISPW program is used instead of the standard Db2-supplied program for the pre-compile process (in skel WZU@DB2). This new program provides a variable containing an ISPW Generated Version that is suitable for the Db2 Pre-compile step. The format of the version ID is dependent upon what was specified in M.AD(L). This generated version ID is stored against the ISPW Task so that it can be used to determine if any subsequent Db2 Packages can be freed. The pre-compile skeleton requires changes to support the passing of the ISPW-generated version ID. Because of JCL and input parameter constraints, a new ISPW program wraps around the Db2 Pre-compiler.

Bind Process

An enhancement to ISPW’s Bind process calls new ISPW messages to record and retrieve information about the Bind being performed. As a result of this, ISPW has all the information it needs to know what Binds have been performed against which Tasks in any Db2 subsystem.

BINDHIST ADD

If Package Version Management is enabled, a call is made in the Bind processing logic after a successful Bind to register the Package Version.

BINDHIST STATUPD

In a Fallback (FB) Operation, it is necessary to update the Status of the Package in the Repository Table to indicate that it is active again (and update the previous one to Inactive). If Package Version Management is enabled, this is done with a call in the normal Package Bind process. The code will check to see if a corresponding Package exists and, if so, will call the function to update its status.

Housekeeping Process

A batch Housekeeping process, as shown in the following figure, is supplied that issues Db2 FREE PACKAGE for any Package Versions that are identified as not being in use and able to be freed. This housekeeping job needs to be defined for each individual Db2 subsystem and scheduled to run periodically.

Housekeeping Process

Housekeeping Job Input Parms  

The Input Parms for the Housekeeping job are listed in the following table.

Housekeeping Job Input Parms

The value specified for PARM2 needs to be carefully considered in the context of the organization’s requirement for fallback. It should be complementary with the period of time that Superseded Backup tasks are kept in the warehouse and can be fallen back to. Check the relevant Warehouse Policy for this Application Level to confirm. If a Package Version is Freed and its Inactive Task is still backed up in the Warehouse, a subsequent Fallback operation will need to perform a Bind, rather than reinstate that Package Version, because it is no longer in the Db2 catalog.

The value specified for PARM3 can be set to a relatively small number of days, because the corresponding load and dbrm does not exist in ISPW after the associated Task has been deleted.