What timestamp does the CONTOKEN on a Package List report represent?

book

Article ID: 19580

calendar_today

Updated On:

Products

CA RC/Migrator CA Endevor SCM Interface DB2 Administration CA RC Compare for DB2 for z/OS CA RC Extract for DB2 for z/OS CA RC/Query CA RC Secure for DB2 for z/OS CA RC Update for DB2 for z/OS CA Bind Analyzer for DB2 for z/OS CA Detector CA SQL-Ease for DB2 for z/OS CA Sysview Performance Management Option for DB2 for z/OS CA Database Detector for DB2 for z/OS CA Plan Analyzer for DB2 for z/OS CA Subsystem Analyzer for DB2 for z/OS CA Database Analyzer for DB2 for z/OS CA Fast Unload for DB2 for z/OS CA Fast Check for DB2 for z/OS CA Fast Index for DB2 for z/OS CA Fast Load for DB2 for z/OS CA Rapid Reorg for DB2 for z/OS

Issue/Introduction

Background:

When a program is compiled and bound a CONTOKEN is stamped on the package as well as embedded in the load module. During program execution the load module passes the CONTOKEN to DB2 to find the correct version of the package. If the contokens match, the program works. If they do not match a -805 occurs and the correct version of the package needs to be found. Using the CONTOKEN or a TIMESTAMP users can check if a match is found in the load module.

 

Question:

What timestamp does the CONTOKEN on a Package List (PK L) report represent?

Answer:

The CONTOKEN shown on the Package Detail Report in RC/Query is from SYSIBM.SYSPACKAGES. This represents the timestamp when the package program was precompiled. The RC/Query detailed screen also contains the precompiled date. Either the CONTOKEN or precompile date can be searched for in the load module to ensure there is a match.

Environment

Release:
Component: GEN