Performance Considerations › Retaining the Intermediate Account File

Retaining the Intermediate Account File

CA JARS automatically creates an intermediate working data file called the account file. This file is a concise and manageable collection of computer utilization statistics at the job and step levels and can be defined as a temporary sequential file.

You can elect to keep this file for future processing by defining a permanent data set for ddname CAIJSACT in the JCL.

Suggested reasons for keeping this intermediate file are listed below, along with a discussion of some appropriate SELECT flags.

1. The No Input Indicator

   If you intend to produce more than 15 user-defined reports with the same data, the account file may be retained using the no input indicator, (position 16 on the SELECT statement). A second step in the execution job stream can produce up to 15 more reports. No new input is allowed in the second step. Performance for this step is enhanced over that of the first step, in that the account file is not reconstructed. Processing begins in Phase 4. Refer to the chapter titled "System Description" in this guide.

2. Account Input Indicator

   The retained account file can be introduced to CA JARS in a later job stream using the account input indicator. Refer to the SELECT statement. Any user-defined report normally produced using the raw SMF or DOS job accounting data, can be generated using the account file as input at a considerable savings in processing time.

   It should be noted here that the account file record layout is subject to change from one release to another of this product. Therefore, this file should not be used for historical backup or year-to-date reporting purposes. Use history output for those purposes. The sole function of the account file is to relieve the user of the need to repeatedly enter the raw SMF or DOS job accounting data to generate multiple reports against a given amount of data. Saving the account file should not serve as an alternative to creating a history file. Reprocessing a history file is the preferred method of processing except in the case where more than 15 user-defined reports are to be generated against the same account file.

   Note: In this case, the account file contains records corresponding to all available input. If you were to input historical data through the ddname CAIJSHST, the output account file would also contain these history records in addition to account records. When such summary records are present, the account file should not be retained and reused.

3. EXTDATA Records

   If EXTDATA records are to be the primary output of JSIMAIN, then for efficiency, it makes sense to make the Account file permanent, and not to produce a history/summary file.