Previous Topic: Differences between System Use Reports and EXTDATA System Use Reports

Next Topic: History Files


User-Defined Reports

CA JARS allows you to design customized reports. These reports are called user-defined reports. Using control statements, reports are generated to meet your needs. This guide is designed to assist you in coding the control statements required for report generation.

Up to 15 user-defined reports can be generated in a single run of this product, in addition to any selected System Use Reports.

A set of sample report control statements is provided on the distribution tape. You can find them in CAJROPTN (WSETJARS). These precoded control statements produce a wide variety of reports on your SMF data and provide an example of how to use the control statements. Some minor modification is required to define installation dependent elements such as department names, shift hours, rates to be charged, and so forth. Sample reports for the interfaces also exist on the distribution tape.

User-Defined Reports on performance statistics can be generated to complement the System Use Reports. Performance and utilization statistics can be shown in more detail than System Use Reports. Samples of System Use Reports are provided in the sample working reports as well.

Billing, or chargeback, is a common use of CA JARS. Several charge-related reports are provided in the sample reports. There are detailed explanations of chargeback, rate calculations, and cost distribution in the sections that follow. Also, you should read the section on Accounting Standards/Conventions in the CA JARS Systems Programmer Guide. Once you are familiar with the CA JARS method of chargeback, data from any of the interfaces including CA JARS DSA Option (Disk Space Accounting) in combination with the SMF Extensions (SMF/E) can be implemented to provide a complete chargeback solution.

More advanced chargeback capabilities are available through the use of the JARS/OLF component. For further information see the JARS/OLF Component in the "System Description" chapter of the Systems Programmer Guide.