Managing the size of Package Dataset


Article ID: 50816


Updated On:


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 PanAudit Plus CA Easytrieve Report Generator CA PAN/SQL CA Endevor Software Change Manager (SCM) CA Endevor Software Change Manager - Natural Integration (SCM) CA Endevor Software Change Manager - ECLIPSE Plugin (SCM) CA Endevor Software Change Manager - Enterprise Workbench (SCM) CA 2E



Ideas for housekeeping of the Package Dataset.


  1. Knowing the contents of your PKG file.
    With a simple CSV - List package - job you can determine how many packages have been defined and what their status is.
    The CSV data is most useful when imported into Excel. It can be used to produce management reports, determine a list of packages that should be deleted or archived or to take a view of your package file contents prior to any decision.

  2. Delete unnecessary data from the file:

    • Make sure your packages are really used. Delete all unnecessary packages.

    • Define an expiration period for executed and non-executed Packages.
      Commit, Archive and Delete expired Executed and Committed packages,
      Delete expired unexecuted packages.
      See also topic -6-, notes on the Archiving of Packages.

  3. Package size optimization:

    Avoid using the ENCOPTBL option SCL_IN_CAST_REPORT=ON. When used, packages will require more space than in most cases is needed.

  4. Physical housekeeping using BC1JRPKG:

    The BC1JRPKG job will rebuild the VSAM Package Dataset using the IBM IDCAMS utility. It reclaims the space of the deleted package records and also improves the performance of future read and write operations to the package file.

    Job BC1JRPKG can, if needed, also be used to change the size of the package file by increasing the CYLINDERS parameters in the DEFINE CLUSTER statements of this job.

    You should run this job even if you have not deleted any packages, as every change to a KSDS record creates a new physical record as well as reclaimable space.

    You should run this job as a minimum once every week but depending on your package activity, you might want to run it every night.


    Run BC1PPKGC (part of BC1JRPKG) every 3 months.

    Package Analysis Program:

    This program VALIDATES that the records in the PACKAGE file still have a PACKAGE HEADER records to which they relate.
    During the 1ST run of this program, you may find that some Package Records are obsolete and get dropped. If during subsequent executions the number of dropped records is not close to zero then an error may have occurred during PKG processing leading to orphaned records. If this happens frequently and if your analysis of the job and console logs show no errors, you should contact support for assistance.

  6. Notes on the Archiving of packages.

    The Archive Package action allows you to offload packages to an external dataset with or without the specification of a "Where Older than" clause.

    Ideally, packages are archived to a GDG or to an existing file using DISP=MOD.

    The Package Archive file(s) can be used to run Endevor reports on archived packages. You cannot restore archived packages!

    Refer to "The Archive Package Action" in the r14 SCL Reference Guide, also to Chapter 9: Archived Package Reports in the r14 Reports Guide.


Component: C21E