|
|
|
There are several interfaces to this product available on the distribution tape. They are:
The CICS interface (CA JARS for CICS), IDMS interface (CA JARS CA IDMS Option), and the Disk Space Accounting interface (CA JARS DSA Option) are available on separate tapes. Each interface has its own documentation.
All of the interfaces produce output that can be used as input to CA JARS or into the Wizard Report Writer. In addition, some of the interfaces can also generate EXTDATA records that can be used by CA Earl and CA Easytrieve. To determine if an interface produces EXTDATA, see the documentation for that interface. For record layouts for interface EXTDATA records, see CA Earl and CA Easytrieve SMF Data Dictionary in the chapter "EXTDATA Reporting."
Because CA JARS is primarily designed to read SMF data, these interfaces have been created to permit data collected by other program products to be read into the report writer as well, with a few exceptions. What follows is a brief explanation of the interfaces to this product.
The ADABAS Interface
The ADABAS Interface allows users of Software AG's ADABAS Database Management package to use this product to report and charge on ADABAS data. The ADABAS command log file is reformatted into CA JARS history record format with this interface. The Report Writer may then be used to generate invoices, activity reports or whatever reports are desired.
The DB2 Interface
The DB2 Interface extracts CPU elements from SMF type 101 records and enables you to chargeback for this activity. This interface is similar to that of DSA in that, DB2 calculates charges for DB2 activity, generates reports, then creates DEBIT control statements to be input to the Report Writer. Those DEBITs will then be included in the TOTAL CHARGE for the appropriate cost center or account code. No history file is generated in the interface, and all charges for the DB2 activity are calculated by the interface, not the Report Writer (CA JARS).
The IMS Interface
The input to this interface is the IMS log file, which contains the information about IMS application resource usage. The log records are reformatted into history record format and account codes or cost center identification may be added during the reformatting process. Full reporting and charging capabilities of CA JARS may then be applied to IMS data.
Optionally, EXTDATA records may also be produced by this interface.
The Network Accounting Interface
The Network Accounting Interface provides a mechanism for:
The data used to assess and charge network cost is obtained from either CA Mazdamon or IBM NETVIEW. This guide describes how to manipulate NETVIEW and CA Mazdamon data through CA JARS and CA JARS Wizard.
The Roscoe Interface
The Roscoe Interface reformats the Roscoe account file into CA JARS history records, thus making the Report Writer available to users of ADR's Roscoe product.
The Tape Volume Accounting Interface
The CA JARS Tape Volume Accounting Interface provides a mechanism for users of CA tape management software packages (CA 1 and CA DYNAM/TLMS) to:
The VM Interface
The VM Interface converts the VM account file data to CA JARS history format so reports may be generated to reflect the activity of each VM machine and each CMS user. Billing reports and invoices may also be created based on the accounting information provided through this interface.
The Disk Space Accounting Interface (CA JARS DSA Option)
The DSA Interface lets you account for disk space usage and charge for it as well. This interface is different from the others, in that, DSA calculates charges for disk space usage, generates reports, then creates DEBIT control statements to be input to CA JARS. Those DEBITs will then be included in the TOTAL CHARGE for the appropriate cost center or account code. No history file is generated in the interface, and all charges for the space used are calculated by the interface, not CA JARS.
The IDMS Interface (CA JARS CA IDMS Option)
The IDMS Interface is a tool for effectively analyzing IDMS activity. This interface compiles information about IDMS resource usage into a format that can be used for producing reports with CA JARS. To accomplish this, the interface reformats your IDMS Archived Log File records, producing a history file. All data required for you to monitor and allocate resource utilization is retained.
The CICS Interface (CA JARS for CICS)
The CICS Interface, once installed, becomes an integral part of CICS. Without altering IBM code, CA JARS for CICS collects data on transaction activity within CICS. Log files containing that data are maintained by the interface and through batch processing are reformatted into history records to be input to the report writer. The reformatting process (the Translate Utility) permits the user to generate utilization graphs on transaction, program, or file statistics and assign an account code or cost center identification to each record.
CA JARS for CICS GOLD is the feature of this interface that permits the user access to the collected data, online, before any batch processing is performed on the log files. Graphic reports can be generated on the terminal, and CICS can be closely monitored to assist in pinpointing problems during peak utilization periods.
DMS, UFO and MANTIS information can be included in the CICS data if desired.
The CA Datacom/DB Interface
The CA Datacom/DB Interface is a tool for effectively analyzing CA Datacom/DB activity. This interface compiles information about CA Datacom/DB resource usage into a format that can be used for producing reports with CA JARS. To accomplish this, the interface reformats your CA Datacom/DB accounting records, producing a CA JARS summary file. All data required for you to monitor and allocate resource utilization is retained on the CA JARS summary file.
The Online System Interface (JOS)
JOS is an ISPF interface designed to increase user productivity by providing an interactive, menu-driven environment for creating reports. You simply specify the options you want to perform using the menu-driven system. This eliminates the task of creating control statements.
Summary
When running reports on several interfaces and batch data, See the Account Record Matrix in this chapter to compare the record layout across all interfaces. Keep in mind that some fields are vastly different, depending on which interface data is input. For example, CICS executes transactions much more rapidly than batch jobs can run in the operating system. Therefore, time fields in the CICS data are in a different format than in batch data. (CICS times are relative to minutes, seconds, and fractions of seconds, and batch times are relative to hours, minutes, and seconds.) Similar differences exist in other data elements as well.
When generating a summary line on a report including data from multiple interfaces and SMF, be sure to display only fields that are true across all the data types, or totals can lose meaning. For example, you cannot add number of lines printed to number of file I/Os and expect the total to always be useful.
Each interface, except DB2 and DSA, comes with its own data element title table. An explanation of the Title Tables can be found in the CA JARS Systems Programmer Guide.
A good example of a report for multiple types of data, or interfaces, is an invoice. The report program is an excellent method of generating such an invoice. Different algorithms may be applied to each type of data. It may be necessary to perform grouping on processing id and/or a specific literal in the record to have the correct charge calculated for each data type.
Running the sample reports provided with each interface will prove helpful in familiarizing you with the different data elements definitions.
| Copyright © 2012 CA. All rights reserved. |
|