Safeguard User's Guide (G06.29+, H06.08+, J06.03+)

Working With SAFECOM
Safeguard User’s Guide — 422089-020
7 - 12
Placing Comments in a Command File
execute the commands in the EDIT file, run SAFECOM and, using the IN option, name
the EDIT file as the input file.
For example, suppose this sequence of commands is in an EDIT file called
$system.secmgt.saleinfo:
INFO VOLUME $data , DETAIL
INFO SUBVOLUME $data.sales1 , DETAIL
INFO DISKFILE $data.sales1.* , DETAIL
INFO SUBVOLUME $data.sales2 , DETAIL
INFO DISKFILE $data.sales2.* , DETAIL
INFO SUBVOLUME $data.sales3 , DETAIL
INFO DISKFILE $data.sales3.* , DETAIL
These commands produce detailed INFO reports on the $data volume; on the $data
subvolumes sales1, sales2, and sales3; and on all the disk files residing on those
subvolumes.
The following example uses the INFO command to produce a report:
22> VOLUME $system.secmgt
23> SAFECOM /IN saleinfo, OUT $s.#lp1, NOWAIT/
24>
Specifying $system.secmgt.saleinfo as the input file directs SAFECOM to open the
saleinfo file, execute the commands in the file, and stop after executing the last
command. SAFECOM lists the INFO reports on the printer $S.#LP1. Because this
example does not use your terminal for input or output, you can use the NOWAIT
option to instruct TACL to start SAFECOM and then return to your terminal.
You can include several options in one command. To do so, enclose the option string in
slashes and separate each option from the next with a comma.
Placing Comments in a Command File
To place a comment in a command file, use a double hyphen (--) to delimit the
comment. The following comments begin lines in a command file:
-- Establish the default subvolume for file-name expansion
--
VOLUME $system.secmgt
--
-- Assume DISKFILE as the default object type for the
-- next set of commands
--
ASSUME DISKFILE
You can also place comments at the end of a command line:
VOLUME $system.secmgt -- LISTUSER is on this subvol
OBEY listuser -- reports on all system users