User interface to provide correlation between Db2 packages and load module

Pain Point:

Housekeeping of Db2 packages (deletion of old, no longer needed application packages) is done subsequently to the houskeeping of the corresponding load modules on the loadmod.

Today we use the contoken to correlate the load module with the Db2 package.

This correlation and therefore the housekeeping process for Db2 packages cannot be done in some cases;

There are situations, where Db2 coprocessor is not providing a contoken for the loadmod (i.e. the SQL-call is contained in an obsolete section and the COBOL-compiler uses compile options SQL and OPT(2) )  the contoken in the load module is ommitted whereas it is still contained in the DBRM).

We have documented such a situation in Case TS002667221.

Furthermore the contoken is presented in the load module in different ways depending on the language used. Finding a contoken in a C module can be very difficult or even impossible.

Using the column LASTUSED from SYSIBM. SYSIBM.SYSPACKAGE is non-reliable to detect obsolete packages. A package have to be there as long as the corresponding load module is present in the load library.

Problem Statement:

DB2 uses the contoken to match package and load module, but this is not an official user interface and it may be subject to changes.

Statement IBM in case TS002667221: "The consistency token is considered by Db2--...--not to be a user interface."

Proposed solution: 

In order to delete obsolete DB2 packages, we would like to ask for a user interface which allows us to assign a DB2 package to the appropriate load module.

The user interface should give us the possibility to decide, if a load module belongs to a given DB2 package. Inserting the contoken in a unique and reliable way into the load module preceded by an eyecatcher could be a solution.