There are three ways
to start the HCL Workload Automation for Z auditing
functions:
Invoking it interactively (option 10.1 from the main menu)
Submitting from the dialog a batch job (option 10.2 from the main
menu)
Submitting a batch job outside the dialog
The sample library member EQQAUDIB contains a job that is customized
at installation time and that you can submit outside the dialog to
start the auditing function in those cases when either of the two
simpler methods cannot be used. The first two methods are useful when
there is an urgency to create reports from all the auditing data sets
(job-tracking, track-log, or extended-auditing). This facilitates
searching for answers to critical questions without having to spend
too much time to examine the input records with the aid of the mappings
listed in the Diagnosis Guide and Reference. The third way
is useful in case of a planned utilization: many installations have
a need to create and store auditing trails for a set period of time.
In this case, an HCL Workload Automation for Z auditing
job (copied from the EQQAUDIB CUSTOMIZED) can be defined to run automatically
after every daily plan EXTEND or REPLAN, using the data set referenced
by EQQTROUT or EQQDBOUT as input.
Even if you are not required to create an auditing
trail regularly, the report generated can provide quick answers in
determining who in your organization requested a function that caused
some business application to fail, or to trace the processing of a
job that failed and was rerun many times. If your AUDIT initialization
statement specifies all data for JS update requests, you can use the
auditing report to compare against the master JCL to determine exactly
which JCL statements were changed.
The auditing program reads the JTARC or DBARC data set and the
currently open EQQJTnn or EQQDBnn in their entirety.
Thus the report produced contains almost always some amount of obsolete
data generated by the old records still visible in the open data set
and not yet overwritten by new data. Any information appearing in
the auditing report after this header is old or residual, and you
must very carefully review timestamps when using it. Note that this
old information is also included in the statistical information at
the end of of the EQQAUDIT report. If accurate statistics are required,
they can be obtained by generating the report using the EQQTROUT dataset
(INPUT TRL).