|
|
|
The data component of a PDS consists of one or more data blocks separated by end‑of‑file markers. The structure of the PDS data component can also depend on the product that uses it. The linkage editor creates a PDS data component that includes a number of differently formatted records. For audit purposes, we review IDR data records because they contain information about changes to a program.
When SMP/E invokes the superzap utility to apply a fix, superzap applies the fix and places control information in one of the program’s IDR data records. This information includes the date of the fix and it’s SYSMOD ID. SMP/E also places the SYSMOD ID in the UMID subentry of the MOD entry in the CSI that corresponds to this program.
CA Auditor compares the IDR data information to the corresponding MOD entries (the UMID subentries) in the CSI. In this way, CA Auditor determines if a particular fix was applied using SMP/E.
CA Auditor relies on the underlying integrity of the PDS and PDSE structure for it to process correctly. The structure of a PDS and/or PDSE can be corrupted if the system goes down during a PDS compress operation or because of a software error in managing PDSs. These can cause an alias relationship to be inaccurate or change the collating sequence in the directory. You can use the Library Integrity Analysis Function (6.1.2) to ensure that all members of a load library can be loaded. You can use the Program Statistics Display (5.2) to investigate modules with load errors.
| Copyright © 2009 CA. All rights reserved. | Tell Technical Publications how we can improve this information |