Creating the Audit Tape

The OSC Technical Applications staff member responsible for creating the audit tape must review and edit the RUN-JCL. After the RUN-JCL has been reviewed and edited, the run statement C-GL-AUDIT-TAPE-RUN then can be edited and submitted. The following narratives are presented to provide a summary of this process.

STEP 1

The first step in creating the audit tape is to review and edit the RUN-JCL. The RUN-JCL must reference the 300 byte data definition, C300BYTE. The C-300BYT dataframe allows a 300 byte data record to be created.

The RUN-JCL must also name the data set created.. The 'DSN = OSC.FAA.GL.AUDxx.MOpp.FYyy' (where 'xx' is the two character NCAS agency id, 'pp' is the period, and 'yy' is the last two positions of the fiscal year ending date).

STEP 2

The Run Statement in the OSC production library must be edited with relevant selection information provided by the requester on the Production Modification Request. On the next page is an example of the run statement parameters used to create an audit tape for an agency on the cash basis of accounting.

The run statement identifies the range of companies to included on the audit tape. In this example, all companies between '1600' and '1699' are be included on the tape. The '16' is the NCAS agency id which becomes part of the dataset name.

The run statement next identifies the source module id when a specific module is to be selected. This statement should be excluded from the run statement by commenting it out if all source modules are to be included on the tape.

The run statement next identifies the starting and ending effective dates for the detail transactions. For state agencies, the cash basis fiscal year begins on 07/01/YY and ends on 06/29/YY. The accrual basis fiscal year begins on 07/01/YY and ends on 06/30/YY.

The dataset name created in this example would be OSC.FAA.GL.AUD16.MO04.FY98