|
|
|
To detect inefficiencies in change control procedures and to prevent unwanted manipulation of sensitive data, it is important to monitor changes to production programs. The CA AuditorProgram Freezer functions lets you take “snapshots” of programs and monitor them for later comparison and detection of any changes, including source programs in CAI.CAILIB, CA Panvalet, Endevor, or CA Librarian .libraries.
You can compare the snapshot later to another snapshot of the program to determine if any changes were made. You can use Program Freezer options to monitor:
Libraries can be frozen with the File Freezer option. The library freeze of a PDS directory detects and reports changes at the member level. It is usually faster to freeze the PDS directory using option 6.6 than to freeze each member individually. You can then freeze members that were changed using the Program Freezer to investigate the changes in detail. The File Freezer option can also detect changes to sequential files that are not libraries or VSAM KSDS or ESDS.
Most programs are frozen using the Program Freezer Add and Refreeze Program panels, or the F (Freeze) line command on a row of an CA Auditor table display. Programs in storage, exits, SVCs, and LPA modules, however, are added to the CA Auditor freezer database or refrozen only with the F line command. You can use the Program Freezer Query and Program Freezer Delete panels for these programs.
When CA Auditor freezes a program, it creates a “digital signature” for the program and saves it with other information about the program in the CA Auditor freezer database. CA Auditor compares this same signature to the signature it creates the next time you freeze the program. If CA Auditor finds differences, the entry is flagged on the display. You can freeze any number of programs, depending on the size of your DBASE1, the CA Auditor database.
CA Auditor displays the results of its freezes to a program in two formats: a change history and a change log. The change history shows the results of up to 10 freezes to a program. It displays these results in terms of time periods and compares the most recent freeze to each previous freeze. Using a program’s change history display, you can discover programs that were changed and then changed back again. You can also monitor whether your staff is freezing a program regularly.
The change log stores the results of up to 10 changes to the program. It displays only those intervals during which a change occurred and discards the intervals between changes. Therefore, the change log shows you the “end points” of relevant time intervals. Using the change log, you can determine how often a program is changed, indicating how thorough your data center’s testing program is.
When you ask CA Auditor to freeze a program, it saves this information in a work group in the freezer database. Work groups are pools or “folders” that store freezer processing. By default, CA Auditor provides you with a personal work group to process your freezer requests. No other user can access your personal work group through CA Auditor. However, if you want to share the results of freezer processing with other users, you can select a different work group or create a new one. You can create a new work group by selecting option 1.4 from the Change User Profile Information menu. See the Select Work Group section in the “User Profile Information” chapter for a description of how to select and create a work group. If you want CA Auditor to ask you to select a work group every time you want to freeze a program, you must enable prompt mode. By default, CA Auditor does not prompt you for a work group. For an explanation of how to enable or disable prompt mode, see the section Freezer Prompt Mode in “User Profile Information.”.
| Copyright © 2009 CA. All rights reserved. | Tell Technical Publications how we can improve this information |