Example 2: Auditing ongoing changes and creating an audit file
An auditor for a large insurance company requests a daily report that shows all transactions made to policy information. He wants the report sorted by authorization ID so that each person making changes to policy information can verify their daily changes before the report is delivered to him. Additionally, the auditor has asked you to save these changes in a separate file for archival purposes.
To respond to these requests, use the product’s ability to specify a work ID as an ongoing process. When Log Master runs an ongoing work ID for the first time, it uses the start point of the time frame that you define. But the next time you run the ongoing work ID, Log Master automatically adjusts the start point so that your log scan will select any transactions that were open at the end of the previous run. For more information about using ongoing processing, see Ongoing processing.
By combining the ongoing processing feature with the Log Master ability to define relative dates and time, you can create a single work ID that you can run daily to meet the auditor’s needs without changing or redefining the work ID.
You can specify a Log Master log scan step to create a filter to search all tables of the policy information application for updates, inserts, deletes, and exchanges. Select the changes made only by those authorized to use the application online. Exclude personnel who perform only batch transactions.
Log Master produces an Audit report by default. You can change the report ordering so that the information is grouped by authorization ID. Additionally, you can request a logical log to save the selected transactions for possible further use. It is inefficient and costly to search the entire log each time that you perform an audit. Use Log Master to create audit files in logical log format with just changes of interest for a particular purpose. Save these files for archival purposes and for further ad hoc filtering later.
The following figure shows an example of the ongoing auditing process.
For this example, you will set up a process that creates a daily report of all beneficiary changes made to policy information, and save that information to a file.
The overall process for this task is as follows:
- Define a filter.
- Set the time frame.
- Change the default ordering of the Audit report.
Run the ongoing auditing job.
Because you have defined this work ID as an ongoing process, the first time that you run the job, it starts at the start point that you designated when you defined the time frame. The next time that you run the work ID, it starts where the first run ended. The third run starts where the second run ended, and so on. This process gives you audit information in an ongoing manner.
To define an ongoing audit of data changes
Complete the following series of panels:
On this panel | Take this action | Notes |
|---|---|---|
Main Menu | Select Create Audit Report and press Enter. | None |
Create Audit Report | Select Specify Log Filter Criteria and press Enter. | This step creates the filter to define search criteria.
|
Selectable Fields | Use the Structured or Free Form filter interface to define search criteria. Define a filter that selects changed records for the BENEFICIARY column in the POLICYINFO table, and changes made only by users authorized to use the online application. Press F3 until you return to the Create Audit Report panel. | |
Create Audit Report | Select Specify Time Frame and/or Input Source and press Enter. | This step specifies the time frame for the log scan, and designates the job as an ongoing process. When the job is an ongoing process, Log Master automatically adjusts the range of the time frame to start where the last run ended. The first time that you run the job, it starts at the start point you designate when you define the time frame. For instructions, see Defining-a-time-frame. For time frame values, see the following figure(Example time frame definition). |
Time Frame Specification | In the Ongoing Process field, type Y. Type a date and time to define the start point, and accept the default end point value of CURRENT. Press F3 until you return to the Create Audit Report panel. | |
Create Audit Report | Select Define Report and File Outputs and press Enter. | Log Master displays an Audit report request by default. This step changes the report to sort by Authorization ID, Table Name, and Unit of Recovery. This ordering groups all transactions made by one person. With the transactions grouped, it is easier for each person to verify their section of the report. |
Report and File Outputs | In the ACT column, type E. | |
Report Output | In the Order By fields, type 3, 9, and 1 and press F3. | |
Report and File Outputs | In the ACT column, type I and press Enter. | This step inserts another output request that saves the logical log as an audit file. For more information, see Logical-log-output-files. After you complete this step, the Report and File Outputs panel will look similar to the example in the following figure(Example report and file outputs for ongoing migration). |
Output Options | Select Logical Log File Outputs and press Enter. | |
Logical Log Output | Beside the logical log or logical log control file, type E to change the data set name as appropriate for your environment. Press F3 until you return to the Create Audit Report panel. | |
Create Audit Report | Select Work ID Options, JCL Generation and press Enter. | This step saves the work ID and generates the JCL. For an example, see Creating-a-batch-job-from-a-work-ID. |
Work ID File Menu | Select Save As. Select Generate JCL for batch submittal. |
Filter selecting data by changes to a specific column
Command ===> ________________________________________________ Scroll ===> HALF
SSID: DB2R
Work ID . . : ABC.AUDITCHANGES
Description : POLICY INFO CHANGES - USERS ENTERING TRANSACTIONS ONLINE
Updated Version:V11.01.00
Type one or more action codes. Then press Enter.
C=Catalog Search I=Insert D=Delete E=Edit O=Logical OR
ACT SELECTABLE FIELD OPERATOR VALUE
_ CONNECTION ID = ONLINE
_ AND BENEFICIARY CHANGED
********************************* End Of List *********************************
Example time frame definition
Start of Log Scan . . . : 2013-01-18 00.00.00.000000
End of Log Scan . . . . : CURRENT
Log File Source . . . . : Subsystem BSDS
Select an Option. Then press Enter.
Options . . . _ 1. Define Start Point
2. Modify End Point
3. Reset Time Frame using Log File Selections
Ongoing Process . . . . . . . Y (Y=Yes, N=No)
Rerun/Reprocess Options:
Rerun Run Number . . . . . __________ (Run Sequence Number or LASTRUN)
OR
From End of Run Number . . __________ (Run Sequence Number or LASTRUN)
Example report and file outputs for ongoing migration
Command ===> ________________________________________________ Scroll ===> HALF
SSID: DB2R
Work ID . . : ABC.AUDITCHANGES
Description : POLICY INFO CHANGES - USERS ENTERING TRANSACTIONS ONLINE
Enter an action code. Then press Enter.
I=Insert, D=Delete, E=Edit
ACT TYPE DESCRIPTION
_ Report AUDIT
Sysout: Class(*)
_ Logical Log Data: ABC.D&DATE..T&TIME..LLOG.DATA
Cntl: ABC.D&DATE..T&TIME..LLOG.CNTL
******************************** End Of List ********************************
Related topic