Print audit trail

The following figure is displayed when you select option U.2 from the Primary Option Menu or option 2 from the Utilities Selection Menu. This screen enables you to print the contents of an audit trail dataset that you created with the Update process and chose not to print the Audit Report at that time.

Print Audit Trail Screen

Field descriptions

Specify Audit Trail Information:

Audit trail disposition

Enter one of the following:

Audit trail dataset

File-AID/Data Solutions allocates the audit trail dataset at the beginning of your edit session. If your tso-prefix matches your tso-id, the audit trail dataset name is:

TSO-ID.DATASOL.AUDT.Dyymmdd.Thhmmss.Msss

tso-id

Your TSO user ID, up to seven characters, or up to eight characters if eight character user ID has been implemented with z/OS 2.3 or later.

Dyymmdd

Gregorian date when the audit trail is created.

Thhmmss

Hour, minute, and second the audit trail is created.

Msss

Millisecond the audit trail is created.

tso-prefix

Your TSO user prefix, up to seven characters, or up to eight characters if eight character user ID has been implemented with z/OS 2.3 or later.

If your TSO-prefix does not match your user ID and the audit data set name does not exceed 44 characters, the audit trail data  set name is:

tso-prefix.tso-id.DATASOL.AUDT.Dyymmdd.Thhmmss.Msss

When the tso-prefix is included and the construction of the audit data set name exceeds 44 characters, then millisecond will be omitted. For example, if you had a 4 character tso-prefix and a 5 character tso-id, millisecond would be included. If you had a 4 character tso-prefix and a 7 character tso-id, millisecond would be omitted:

tso-prefix.tso-id.DATASOL.AUDT.Dyymmdd.Thhmmss

If you specified an audit trail prefix (Audit trail prefix), the audit trail dataset name is:

audittrailprefix.Dyymmdd.Thhmmss.Msss

Specify Batch JCL Information:

Sysout class

Enter the sysout class for the Audit Trail Report. For more information on the report, see Audit Trail 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 ISPF/PDF Edit screen and edit the generated JCL before you submit it.

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 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.

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 and Audit Trail Report — Hexadecimal.

Each topic of the Audit Trail Report begins with topic headings that consist of the edited data set name, the date and time the report was produced, the product’s release number, report title, and the topic number.

Following the topic 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/Data Solutions 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/Data Solutions includes the relative record number of the updated record.

Formatted Report Contents

File-AID/Data Solutions prints the audit trail contents in a formatted display. When printing the audit trail contents in formatted display, File-AID/Data Solutions uses the same record layout or XREF dataset that was specified for the update in which the audit trail was created to format the 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 File-AID/MVS Edit Formatted mode.

The next two columns on the report are BEFORE FIELD VALUE and AFTER FIELD VALUE. 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 File-AID/MVS Edit formatted mode.

The right most 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 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/Data Solutions 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 an unformatted report program. Following are some of the reasons that File-AID/Data Solutions 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 because 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 for the update that created the audit trail, but File-AID/Data Solutions was unable to print an audit trail record in the formatted manner. File-AID/Data Solutions 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/Data Solutions switches print formats. You may also switch the audit report format to HEX by editing the Audit print JCL.

When printing the audit trail contents in HEX, File-AID/Data Solutions displays each record in a three-line format similar to the hexadecimal mode of File-AID/MVS 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. For the updated records, 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. You may switch the audit report format to CHARACTER by editing the Audit print JCL.

Audit Trail Report — Character

Summary Information

Summary information is printed on the last topic 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.
• Number of data file records that were changed.
• 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 for the update and the record layout dataset type (SEQ for sequential, PDS for partitioned, PAN for CA Panvalet, LIB for CA Librarian).
• Names of the record layout XREF dataset and member specified for the update (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 for the update. If temporary selection criteria was used during for the update, the literal ** TEMPORARY ** is printed.
• Date and time the 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.

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. See Print Execution Return Codes for a summary of the return codes.