1

Obtain the names of master files that are supposed to be read‑only. Use the F line command to freeze the files. Prepare a work paper that documents information about the frozen master files.

2

Refreeze the master files that were frozen during previous reviews using the Select Batch Functions display (0.4.2). Note any changes detected.

3

If you found modifications to the master files in Step 1, search SMF for additional information using the File History Search display (6.5). Verify the purpose and authorization of any changes.

4

Freeze SYS1.PROCLIB and any other procedure libraries by entering the F line command on the JES Proclib Display (4.2). If you detect any changes, determine that they agree with change procedures and authorization records.

5

Check the JES parameters.

Determine if you have JES2 using the System Overview display (1.1). If so, split your screen and use ISPF/PDF Browse to review the JES2 member of SYS1.PROCLIB.

A HASPPARM DD statement should exist, unless the operator starts JES with a HASPPARM= parameter.

Check the console operator’s log (SYSLOG). The data set that the JES ddname refers to contains the parameters. Enter the F line command next to it to freeze that data set.

6

Freeze the z/OS Master Scheduler JCL using the F line command.

Find and freeze all members that begin with MSTJCL in SYS1.LINKLIB using the Program Statistics Display (5.2).

Repeat this step for all members that begin with MSTJCL that reside in the actual SYS1.PARMLIB data set (not the logical Parmlib).

If you encounter identically named members in both SYS1.LINKLIB and SYS1.PARMLIB, remember that z/OS will first search SYS1.PARMLIB, followed by SYS1.LINKLIB.

7

Freeze the Subsystem Name Table. Subsystem names (SSN) are defined to z/OS through a number of methods as follows:

• The IEFSSNxx logical Parmlib member or members that are processed at IPL.
• After IPL through the MVS SETSSI command.
• Program products such as CA SYSVIEW. Other program products such as CA ACF2 dynamically create SSN definitions as needed.

List all such SSN names defined on your system using the Subsystem Display (3.1). You can also use it to display the active additional SSN names dynamically added since IPL.

Identify the IEASYSxx system parameter list used at IPL and then all of the IEFSSNxx members it references using the Parmlib MAP function (2.2.1).

Freeze all such members to identify future changes.

To ensure that all SSN names defined are proper and that dynamic changes (if any) were logged, you can also identify and reconcile those SSN names active on your system that were not defined through the IEFSSNxx logical Parmlib members.

8

Obtain a list of active subsystems on the system using the Subsystem Display (3.1). If you have an archived copy of the source code, use the B line command to browse the program and compare the two versions. Note any changes that you or the peer reviewer detects. Verify that any changes you find agree with change procedures and authorization records.

9

If an archived copy of any file that you checked is available, use the File Comparison option (6.4) to determine what was changed. Verify that these changes agree with change procedures and authorization records.