Customers sometime question why a request to scratch a like-SRC component fails to also remove the ‘associated’ or ‘ILOD’ components, e.g. LOD, DBR, etc., from the relevant baseline library.

Generally this can occur for one of two reasons:

1. Global Admin option ‘Auto scratch load member with source’ is disabled.

This option was introduced in the ZMF 8.1 release. When enabled, it will automatically delete all components associated with the SRC component whenever that is possible (see point 2 below). This option is documented in the ZMF Administrator’s Guide, the 8.2 Patch 7 version of which can be found here. 

2. The SRC component was last built on a release prior to ZMF 8.1 and the last package to baseline the SRC component has been removed from the package master file, e.g. via ZMF housekeeping/ package aging.

Prior to ZMF 8.1, associated component information was held in package records rather than component records. If the package records disappeared for any reason, such as reaching their aging criteria, so did the details of any other components related to the SRC. Scratching the SRC component in the ISPF UI will typically issue a CMN149 message in this situation (NO RELATED SCRATCHES/PROG1.SRC scratch saved. Prior baseline package not found. Scratch requests for related components (e.g. LOD) must be added manually).