In addition to logging updates to the current plan and recording auditing information for the requested files, you can also choose to log updates to the databases and record information for the requested files. You activate this extended-auditing function by setting AMOUNT(EXTENDED) in the AUDIT initialization statement.
The extended-auditing data is written to the EQQDBnn data sets, which are created by the EQQPCS14 sample. The extended-auditing records show the values that were set before and after the database was changed. Extended-auditing information can be requested only for the following files: AD, CAL, JV, OI, PER, RD, RG, and WS.
Logging much more information than currently.
Logging database objects before and after the changes.
Using new logs, to prevent overhead in JT that are also used in recovery process.
A new set of JT-like sequential data sets to log database activities, named EQQDB* A new set of REPORTs to show the database objects before and after the change
How it Works
In case of object ADDED or DELETED, the record is logged in the EQQDB* data sets.
In case of MODIFY, both the old and new records (BEFORE and AFTER) are logged in the EQQDB* data sets.
Run EQQJOBS to create the sample JCLs and set Extended Auditing to Y to activate the feature. Run the sample JCL EQQPCS14 to allocate the new EQQDB* data sets.
Address the new DD EQQDB* in Controller STC and DP Batch.
In the AUDIT statement, set the AMOUNT keyword to EXTENDED
What the Reports Show
Who (the user for which the request was run).
How (Dialog, PIF, DWC), When (timestamp).
What (the list of fields modified with old and new value, or the record deleted or created) was
In the SYSIN, you can specify new PARMS to the EQQAUDIT program to filter log data:
Header and Common Section
Conditions and Condition Dependencies Sections
Special Resource, Extended Info, User Fields, Var. Duration/Deadline Sections
Run Cycle Section
Annarita is currently technical leader for Performance Testing for IBM + HCL Workload Scheduler for z/OS. She has extensive experience in the IWS suite after several years covering various roles in development and test teams.