Skip to content

Aging and Archiving Releases

Batch job ARCHIVE2 combines the package aging and archiving functions in base ZMF job

ARCHIVE1 with release archive functions. ERO customers run ARCHIVE2 rather than ARCHIVE1 to age and archive packages and component history, and to archive ERO releases and their associated Db2 table rows.

Note the commented out section at the start that provides sample code to notify users by email or TSOID, only relevant if you are running z/OS 2.3 or later, and JES2.

These are the processing steps in ARCHIVE2.

  1. Delete aged package records from the package master

  2. Delete aged component history records from the component master

  3. Merge deleted component history records into a cumulative component record archive file.

  4. Delete release records from the package master.

  5. Merge deleted package master records into a cumulative package master archive file.

  6. Extract Db2 table records for archived releases into PDS members.

  7. Combine extracted Db2 table records into a GDG.

  8. Delete Db2 table rows for archived releases.

Note

Release area libraries are scratched by ZMF online housekeeping (=A.G.H/1) after it scratches all aged staging libraries for packages attached to a release. The Aging - Staging Datasets days in application administration must be less than the Aging - Installed Packages days so that staging libraries and release area libraries are scratched before package and release records are deleted.

Notes On Archiving Db2 Table Rows

  • When you delete or archive a large release, you should execute a REORG on the ERO Db2 tables. (REORG should be included in periodic Db2 table housekeeping.)

  • You can execute sample ZMF job ARCDBERO in place of step DB2ICMD in job ARCHIVE2, which executes Db2 program DSNTEP2 to delete Db2 table rows for archived releases. ARCDBERO executes a REORG on each table to strip off archived rows, but it requires more experience to run and restart without risk.