1

Use the Exits display (3.3) to prepare a work paper that shows all known z/OS exits. Determine if adequate documentation and approval from Technical Support exists that defines the purpose, function, use, and operation of each exit.

2

Select each exit from the display to obtain the System Exit Review screen. Note the CSECT, load module, and library names from the display. Enter PENDING in the Review Status field.

3

To detect changes made to exits after this review, use the F line command to freeze each exit load module.

4

Obtain the source code for each exit. Be sure to get the actual assembly listing that shows the link edit step.

Use the Program Statistics Display (5.2) and compare the assembly and link edit dates, module size, CSECT names, and so on, to ensure that the listing you have is the correct one.

5

If you read assembler language, ensure that the function of the exit is the same as the function recorded in its documentation. Otherwise, have someone in Technical Support perform a “peer review” of the code.

Return to the System Review Update Screen and enter the exit’s description and DONE in the Review Status field.

6

Once an exit is frozen, you can test for changes at any time by refreezing the module. If changes are detected, use the File History Search display (6.5) to search SMF for update activity to the module’s library during the time interval between freezes.

7

Split your screen and use ISPF/PDF Copy (option 3.3) to create an archival copy of the exit load module for later review.

8

If archival copies of the exit module are available from system backups or previous reviews and the Program Freezer detected changes, use the File Comparison display (6.4) to determine exactly what changed.

Verify that any changes agree with change procedures and authorizations.