When running TSSUTIL with CLASS(O) to report on control option changes, the following lines for RPW in the Top Secret parameter file are shown in the report at IPL time (when Top Secret is started). For example:
From the TSSUTIL report (with the LONG option):
DATE TIME SYSID ACCESSOR JOBNAME FACILITY PROGRAM SRC/DRC
-------- ------- -------- ---------------- -------------- ------------- ---------------- -------------
12/04/22 00:45:32 sss *UNDEF* tssjob STC TSSMNGR4 OK
RESOURCE TYPE & NAME CNTL OPT RPW(ADD,psw1,psw2,...) * comment from parameter file
12/04/22 00:45:32 sss *UNDEF* tssjob STC TSSMNGR4 OK
RESOURCE TYPE & NAME CNTL OPT RPW(ADD,psw5,psw6,...) * comment from parameter file
12/04/22 00:45:32 sss *UNDEF* tssjob STC TSSMNGR4 OK
RESOURCE TYPE & NAME CNTL OPT RPW(ADD,pswnn,pswxx) * comment from parameter file
Release : 16.0
At IPL time, when processing the Top Secret parameter file, the Top Secret log TCB is not currently active so most control options will not be logged. However, there are three control options: RPW, MSG and DB2FAC, that are set to be delayed until the log TCB is active, so if any of these are set in the Top Secret parameter file, they will be logged at IPL time and show up in the TSSUTIL CLASS(O) report.
Note in the above TSSUTIL output, the ACCESSOR is *UNDEF* and the JOBNAME is the Top Secret job name. If an administrator had changed RPW, MSG, or DB2FAC with a TSS MODIFY command, the ACCESSOR and JOBNAME columns in the TSSUTIL output would show the administrator's ACID and the job name (or TSO session) where the TSS MODIFY command was issued.