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

Working With SAFECOM
Safeguard User’s Guide — 422089-020
7 - 13
Executing a Command File During an Interactive
Session
You can embed comments within a command by including double hyphens at the
beginning and end of the comment:
ALTER DISKFILE report1, ACCESS 2,78 -- give ted jones -- READ
When SAFECOM encounters a double hyphen (--), it ignores all following characters
until it reaches either the end of the line or the next double hyphen.
Do not put a semicolon within a comment because it terminates the line and causes
the remainder of the comment to be treated as a SAFECOM command.
Executing a Command File During an Interactive Session
You can execute a command file during an interactive session by entering an OBEY
command. OBEY directs SAFECOM to execute the commands stored in a specific file.
For example, this command is equivalent to the first batch mode example in this
subsection:
=OBEY / OUT $s.#lp1 / saleinfo
After executing the commands in the file saleinfo, SAFECOM returns control to your
terminal in the interactive mode of SAFECOM. However, the SAFECOM OBEY
command does not support the NOWAIT option, so executing an OBEY command
might result in a delay in getting back control at your terminal.
Using Command Files to Set Up Default Access Control Lists
Command files are useful for establishing default access control lists for disk files or
other objects. For example, suppose the following commands are placed in an EDIT
file called $system.mgr.tight:
ASSUME DISKFILE -- Build default ACL for DISKFILE
RESET -- Clear all current settings
SET ACCESS 255,254 (r,w) -- 255,254 is security admin
SET ACCESS 3,255 r -- Company auditor can read
SET ACCESS 255,8 (r,w,e,p) -- I can do anything
SET AUDIT-ACCESS-FAIL ALL -- Audit failed access attempts
SHOW -- Display current defaults
Using this command file, you can easily apply tight security constraints to any number
of disk files. The following SAFECOM screen display shows an interactive session in