Extended-auditing data sets (EQQDBARC, EQQDBnn)

If you have set AUDIT AMOUNT(EXTENDED), extended-auditing data sets are a log of records that show the values that were set before and after the database was changed. They comprise:
  • Extended-auditing logs (EQQDBnn)
  • Extended-auditing archive (EQQDBARC)
You can control the level of information to be logged by editing the SYSIN card in the EQQAUDIB sample, as follows:
  1. Set the input file to use:
    DBX
    For EQQDBnn
    DBR
    For EQQDROUT
  2. Specify the level of information to log in the report (this applies only to the delete or add action):
    K
    Only the key is reported.
    S
    Summary information is reported (default).
    F
    Complete information is reported.
  3. Set the database to audit. If you do not specify any value, all the databases are audited.
    AD
    Application Description
    CAL
    Calendar
    JV
    Job Variable Table
    OI
    Operator Instructions
    PER
    Period
    RD
    Special Resource
    RUN
    Run cycle group
    WS
    Workstation
  4. Specify the database key to audit. If you did not set a database, this vale is ignored.
    ad_name
    For the AD database.
    calendar_name
    For the CAL database.
    jv_table_name
    For the Job Variable Table database.
    oi_ad_name oi_op_num
    For the Operator Instructions database.
    period_name
    For the Period database
    special_resource_name
    Special Resource
    run_cycle_group_name
    Run cycle group
    ws_name
    For the WS database
For example, a SYSIN card to audit the EQQDBnn database by logging the complete information about the workstation named CPU1 in the WS database, looks like the following: 
//SYSIN    DD *
DBXFWS  CPU1
/*

You must allocate EQQDBARC and at least two extended-auditing logs (EQQDB01 and EQQDB02) for a controller. The actual number of DB logs that you should allocate is determined by the value that you specify on the JTLOGS keyword of the JTOPTS initialization statement. If you decide to allocate three extended-auditing logs, specify the DD names EQQDB01, EQQDB02, and EQQDB03. If you specified EQQDB01, EQQDB02, and EQQDB04, an error occurs and HCL Workload Automation for Z terminates. HCL Workload Automation for Z uses the extended-auditing logs in turn. When a current plan backup is performed, the active log is appended to EQQDBARC data set.

The size of the DB and DBARC data sets can become large, but with appropriate tuning of the size and of the DP frequency, they will not allocate additional extents. If necessary, use the allocation of additional extents (not additional volumes, because only extent allocation is supported in the shipped DB allocation samples).

The extended-auditing-archive data set accumulates all extended-auditing data between successive creations of a new current plan (NCP). Therefore, allocate EQQDBARC with enough space for all extended-auditing records that are created between daily planning jobs; that is, extend or replan of the current plan. In other words, ensure that you allocate for EQQDBARC an equal or greater amount of space than the total of the space you allocate for the DB files, or you will get a system error. When the daily planning batch job is run, the active extended-auditing log is appended to EQQDBARC, and the DB log is switched. The archive log, EQQDBARC, is then copied to the extended-auditing log data set referenced by the EQQDBOUT DD name during the daily planning process. When HCL Workload Automation for Z takes over the NCP, the EQQDBARC data set is emptied.

HCL Workload Automation for Z recovery procedures that use the extended-auditing data sets are described in Customization and Tuning.