Print Audit Trail screen

The following figure is displayed when you select option 5 from the Print Selection Menu. This screen enables you to print the contents of an audit trail dataset that you created with Edit (option 2) or Search/Update (option 3.6) and chose not to print the Audit Report at that time. Refer to Audit Trail Feature and Disposition of Audit Trail.

DBCS data is not supported for an unformatted audit print.

Print Audit Trail screen

Field Descriptions

Specify Audit Trail Information:

Audit trail disposition

Enter one of the following:

PK

Print and keep the audit trail dataset.

PD

Print and delete the audit trail dataset.

Audit trail dataset

This field contains the name of the audit trail dataset to be printed. File-AID automatically completes this field with the name of the most recent audit trail file created in Edit or Search/Update. Type over the existing dataset name to specify a different data set.

Specify Batch JCL Information:

Sysout class

Enter the sysout class for the Audit Trail Report. See Audit Trail Report for more information on the report.

Specify JOB Statement Information:

Enter the JOB statement for the batch print job.

After you complete the information on the screen, press Enter to submit the batch print job. Use the JCL command to display a PDF Edit screen and edit the generated JCL before you submit it. See Generated-JCL.

Use the END command (PF3) to exit the Print Audit Trail screen without submitting the print job.

The Print Audit Trail function can be executed also as a separate step in a batch job by coding the appropriate JCL. This process is described in Executing Print Audit Trail Independently in Batch .

Printing Audit Trail with Unicode Data

Use the CCSID parameter when printing Unicode data to specify the code page to be used. Manually add the parameter to the print JCL to override the default CCSID, for example:

$$DD01 APRINT CCSID=0500

Printing Multiple Audit Trail Datasets

When you want to concatenate multiple audit trail datasets together and produce a separate Audit Trail Report for each data set with one batch job execution, edit the generated JCL before submitting the batch job.

If you specified an S or X in the Edit screen Record layout usage field for the Edit session, File-AID produces a formatted audit report. File-AID produces an unformatted report if you specified an N in the Record layout usage field or if the formatted report generation fails. If the unformatted report program receives control, it processes all concatenated audit files. Subsequent concatenated formatted audit files that would have produced a formatted report are printed unformatted.

Concatenating mixed (formatted and unformatted) audit trail files may produce a report with unexpected results. Special attention is required when concatenating audit trail datasets. The same considerations apply when printing files that have been produced with and without layout concatenations. We recommend that you not concatenate audit trail files produced with record layout concatenation lists.

To prevent concatenation of formatted and unformatted files, we recommend concatenating the formatted audit trail files in a separate execution from the unformatted audit trail files. Audit File Sort Example provides a method for accomplishing this task.

Audit File Sort Example

The JCL shown in the following figure sorts a list of audit files into a list of formatted audit files and a list of unformatted audit files creating two new files. USERID9.FMTAUD, shown in Formatted Record File Created by Sort Audit Files JCL contains the list of formatted record files. USERID9.UNFMTAUD, shown in Unformatted Record File Created by Sort Audit Files JCL, contains the list of unformatted record files.

After the audit files are sorted, you can copy in the list of formatted file names into the JCL shown in Audit Print JCL, and submit the job to concatenate and print the formatted audit record files. Then copy in the list of unformatted files and submit the JCL again to concatenate and print the unformatted audit record files.

JCL to Sort Audit Files for Printing

Formatted Record File Created by Sort Audit Files JCL

Unformatted Record File Created by Sort Audit Files JCL

Audit Print JCL

Audit Trail Report

The Audit Trail Report is printed by the batch job submitted from the Print Audit Trail screen. The report displays the audit trail contents and is printed in a formatted, character, or hexadecimal format. The report also contains summary information.

The contents of the report depends on the value specified in the Record layout usage field on the Edit. See Formatted Report Contents for a description of the report contents. You can override a formatted report with a character or hexadecimal report by changing the SYSIN control card generated for the batch job submission as follows:

Samples of the formatted, character, and hexadecimal formats of the Audit Trail Report are shown in Audit Trail Report — Formatted through Audit Trail Report — Hexadecimal.

Each page of the Audit Trail Report begins with page headings that consist of the edited dataset name, the date and time the report was produced, the File-AID release number, and the page number.

Following the page headings is the date and time when the data file was opened for updating, and the TSO user ID that was used to perform the updates. If the data file organization was VSAM-KSDS or keyed BDAM, File-AID includes the starting position and length of the defined key.

Preceding the image of each data file update on the report are audit trail record headings. The first line contains a sequential number assigned to each data file update, the update action (explained more fully below), and the date and time the update occurred.

For VSAM-RRDS data files, File-AID includes the relative record number of the updated record.

The ACTION field on the first record heading line contains the word INSERT when a data file record was added to the file. When a data file record was deleted via a DELETE primary command or a D (Delete) line command, the ACTION field shows DELETE. CHANGE is shown in the ACTION field when a data file is changed via any primary command or a direct data typeover.

Formatted Report Contents

The format used to print the before and after record images in the Audit Trail Report depends on what was specified for record layout usage during the edit session. If a single record layout or a record layout XREF was used, File-AID prints the audit trail contents in a formatted display.

If record layouts were not used during the edit session, then File-AID prints the audit trail contents in an unformatted, hexadecimal display. The HEX print format is described in HEX Print Report Contents .

When printing the audit trail contents in formatted display, File-AID uses the same record layout or XREF dataset that was specified during the edit session in which the audit trail was created to format the inserted, deleted, and changed records’ images. The first two columns on the report contain the level number/data-name and format of each field in the record layout that is similar to Edit Formatted mode. See Formatted Mode.

The next two columns on the report are BEFORE FIELD VALUE and AFTER FIELD VALUE. The way these columns are formatted depends on the update action, as follows:

• When the update action is INSERT, the AFTER FIELD VALUE column contains the value of each field in the data record that was created. The BEFORE FIELD VALUE column is always empty.
• When the update action is DELETE, the BEFORE FIELD VALUE column contains the value of each field in the data record that was deleted. The AFTER FIELD VALUE column is always empty.
• When the update action is CHANGE, the BEFORE FIELD VALUE column contains the value of each field in the data record as it was before the change. The AFTER FIELD VALUE column shows the new field value only for the fields that were changed. The AFTER FIELD VALUE column is blank for unchanged fields.

Field values are shown in the BEFORE FIELD VALUE and AFTER FIELD VALUE columns similar to Edit formatted mode. See Formatted Mode.

The rightmost column on the formatted Audit Trail Report displays informational messages. A message displays in this column to describe the following situations:

• When an alphanumeric field was changed from a non-blank value to blanks (HEX 40’s), the message AFTER BLANK is printed. This message enables you to distinguish between fields that were not changed and those that were blanked out.

If a single record layout was used during the edit session that created the audit trail, the same record layout is used to print the audit trail contents. If a Record Layout XREF was used, the same Record Layout XREF is used to determine the appropriate record layout for each audit trail record. If File-AID is unable to print a particular audit trail record in a formatted format, processing is terminated and it passes control for the generation of the report to the unformatted report program. Following are some of the reasons that File-AID switches from formatted to hexadecimal printing:

• The record layout member name for the before and/or after record image specified in the record layout XREF was not found in the record layout library.
• The record layout for the before and/or after record image has syntax errors.
• If your record layout(s) are stored in ISPF "packed" format File-AID does not use the layouts and prints the audit trail report in the default "hex" format.

Audit Trail Report — Formatted

HEX Print Report Contents

The Audit Trail Report contents can print in the HEX print format for the following reasons:

• Record layouts were not used during the edit session that created the audit trail (a value of N was specified in the Record layout usage field). As a result, the entire Audit Trail Report is printed in HEX format.
• A single record layout (a value of S was specified in the Record layout usage field) or a record layout XREF (a value of X was specified in the Record layout usage field) was used during the edit session that created the audit trail, but File-AID was unable to print an audit trail record in the formatted manner. File-AID attempts to perform a formatted print of each audit trail record first before switching to hexadecimal printing. Refer to Formatted Report Contents for a description of what happens when File-AID switches print formats.

When printing the audit trail contents in HEX, File-AID displays each record in a three-line format similar to the hexadecimal mode of the Edit unformatted mode. The top line contains the character representation of the record, the middle line contains the upper half-byte of each character in HEX, and the third line contains the lower half-byte of each character in hexadecimal.

Up to l00 positions of the record are printed in each set of three lines. The POSITION column immediately to the left of the record contents indicates the starting position in the record represented by each set of three lines.

When the update action shown is INSERT, the DATA DISPLAYED column to the left of the inserted record’s image contains AFTER. When the update action shown is DELETE, the DATA DISPLAYED column contains BEFORE for the deleted record’s image. When the update action shown is CHANGE, the before image is printed, followed immediately by the after image, if a change has occurred on that line.

When the before and after images of a changed record are displayed, the Audit Trail Report also indicates the record positions that were changed with an asterisk (*) under each changed position. For each three-line set of print lines that contains changed record positions, CHANGE ===> is printed to the left and between the print lines, on the same line as the asterisks.

Audit Trail Report — Hexadecimal

Character Report Contents

The character audit trail report is similar to the HEX report except that the two hexadecimal lines are not printed. Unprintable characters are printed as blanks.

Audit Trail Report — Character

Summary Information

Summary information is printed on the last page of the Audit Trail Report. See Audit Trail Report — Summary. It contains the following information:

• Name of the audit trail dataset that was printed.
• Description of the audit trail entered on the Audit Trail Disposition screen (see Disposition of Audit Trail Screen).
• Number of data file records that were changed, inserted, or deleted.
• The number of members updated if the edit data set was a PDS.
• Name of the updated data file that created the audit trail.
• Names of the record layout dataset and member specified during the edit session (if a value of S or X was specified in the Record layout usage field) and the record layout dataset type (SEQ for sequential, PDS for partitioned, PAN for CA Panvalet, LIB for CA Librarian). All data sets within the record layout concatenation are included.
• Names of the record layout XREF dataset and member specified during the edit session (if an X was specified in the Record layout usage field).
• Names of the selection criteria dataset and member, if existing selection criteria was used during the edit session. If temporary selection criteria was used during the edit session, the literal ** TEMPORARY ** is printed.
• Date and time the edited data file was closed.
• The system ID on which the data file was updated.

Audit Trail Report — Summary

Executing Print Audit Trail Independently in Batch

You can execute the Print Audit Trail function as a separate step in a batch job by coding the JCL shown in the following figure. This process can be useful when you want to print multiple audit trail datasets in one batch print job.

Batch Print Audit Trail JCL

Audit Trail Print Execution Return Codes

The audit trail print execution return codes are the same as the data file print execution return codes. Refer to Print Execution Return Codes for a summary of the return codes. Additional audit trail print return codes are documented in the File-AID Batch Reference guide. See the "Return Codes" heading in the "Message Codes" section.