Complete DB2 for z/OS Package Management

PackMan (DB/IQ PM) helps DBAs and developers analyze complete applications and their associated packages. This is accomplished by checking the consistency of executable load modules and / or DBRMs and bound packages within the DB2 Catalog.

This form of package management allows for regular checks across all required load libraries, DBRMs and the Catalog. Using the z/OS – CSI, "Catalog Search Interface", PackMan will easily locate all load libraries and DBRMs required. Cross checks may be performed from all angles of comparison. In other words; PackMan may be driven from the information found in resolved load library modules and check relevant package versions and/or DBRMs or vice-versa.

Together with a vast selection of reports, PackMan will cross-reference all load library modules and packages and DBRM modules. This informs the user which modules access which packages or which packages are "orphans".

Options are available to build FREE PACKAGE jobs and even clean-up PLAN_TABLEs and other explain-type tables where inconsistencies have been found or where “old“ entries can be removed. DBRMs can be re-generated from the Catalog for one or more Packages.

PackMan (DB/IQ PM) facilities offer the means to enhance package management consistently and impartially by focusing on all resources involved for all applications.

PackMan (DB/IQ PM) Functions and Facilities :

• analyze and perform inconsistency checks on all CONTOKEN's - irrelevant of whether it originates from the DB2 Catalog, a DBRM or within a LOADLIB module.

• assist the user to locate all relevant LOADLIBs and DBRMs, building the base resources to check. resolve all specified LOADLIBs into module and related CSECT names, together with all link timestamp information.

• resolve all DBRM modules and keeps all header options for comparison reasons - identifying empty and invalid contents along the way.

• build cross reference data sets - where Package names or plan-DBRM names match counter-parting LOADLIB and DBRM names.

• finally check "inconsistencies", and optionally build reports, FREE PACKAGE job input and sets condition codes as required.

• include "other" maintenance utilities to "keep" a certain number of package versions (n most recent) and FREE others or free packages marked by DB2 as "invalid".

• A final "clean-up" utility builds a job to remove inconsistent or non-required entries in all PLAN_TABLEs and other explain-type tables.

• generate DBRM member(s) from the Catalog (Packages)

This e-mail address is being protected from spambots. You need JavaScript enabled to view it