The use of protection files with this Model can be constrained or impacted by design differences between CA‑PanAPT, CA‑Panexec, and GDG (Generation Data set Group) processing requirements. It is important that you understand these limitations because errors could result. The error you experience in these situations is a JCL error that indicates that the disposition of the data set is inconsistent with its use.
CA‑PanAPT is designed to allow the deletion of members in the QA Library level at two separate times, during the removal of an obsolete member to make room for the new member, and during the scratch of a copy of a member after it has been moved. Because these deletions occur in different points of the procedure, the deleted members are in separate steps, requiring separate CA‑Panexec executions.
Generally, most CA‑Panexec customers match‑merge the %REMOVEd members with the previous protection file creating a new protection file. This is accomplished through the use of a GDG (Generation Data set Group). The problem that might occur is caused by the fact that the relative version of the new generation of the GDG is not recalculated after each step. Instead, it is recalculated only after the entire job has completed.
|
Copyright © 2004 CA.
All rights reserved.
|
|