Safeguard Audit Service Manual (G06.24+, H06.03+)

Producing SAFEART Reports
Safeguard Audit Service Manual—520480-014
6-14
Using SAFEART Command Files
This example illustrates how to use the Before prefix in a search. This command
selects events in which an attempt was made to change the Safeguard configuration
attribute PASSWORD ENCRYPT from ON to OFF (from True to False):
<=SET WHERE BeforeConfigPasswordEncrypt=True AND &
<=&ConfigPasswordEncrypt=False
Using SAFEART Command Files
SAFEART command files simplify your work. For example, if you want to use the same
selection criteria more than once, as in daily or weekly audit reports, you can store the
necessary commands in a command file.
To create a command file, put a preferred sequence of commands in an EDIT file. You
can execute a command file in one of two ways:
•
As an IN file when starting a SAFEART session
•
With the OBEY command during a SAFEART session
Executing an IN File When Starting SAFEART
If used as an IN file when starting SAFEART, the command file must contain all the
commands necessary to produce a report, including the START command. This
example shows the syntax for starting SAFEART with an IN file:
>SAFEART /IN $data.security.report2, NOWAIT/
After you issue this command, control of the terminal returns to your command
interpreter. If you omit the NOWAIT option, all the commands in the command file are
executed before control of the terminal returns to your command interpreter.
Executing a Command File During a SAFEART Session
If you run a command file during a SAFEART session, the file does not have to be
complete because you can issue additional commands during the session. This
approach can be helpful because you might not know some parameters, such as the
time period or the name of the audit file, until you are ready to run the command file.
These guidelines apply to command files that are used during a SAFEART session:
•
Include the AUDIT FILE command (with no file specified) in command files to clear
any audit file selections that occurred previously in the session.
•
Use RESET commands in command files to clear any previously defined
parameters for the session.
•
Because the current audit file changes periodically, specify audit files during the
session rather than in the command file.
•
Because the time period for your report changes, specify it during the session.