The Network Accounting Interface › Operating Instructions

Operating Instructions

Two reports are generated by the interface:

JSINET1:

shows how debit records can be created. These debit records are read in a product run that reports on charges by account. Network usage charges are added to the other charges that are calculated on an account basis.

JSINET2:

shows network usage by terminal ID.

JSINET3

provides sample control statements for processing of IBM NETVIEW data into CA JARS.

Each report and the CA JARS Wizard glossary for the interface are described on the following pages.

The source code for both of these CA JARS Wizard programs is distributed in the AAJ1OPTN distribution library and is copied to CAJROPTN at APPLY time by SMP. You are encouraged to use these as samples and develop your own CA JARS Wizard applications against either CA Mazdamon or IBM NETVIEW data. However, you should avoid modifying the distributed source other than via official maintenance.

JSINET1: Debit Record Creation

In JSINET1, CA JARS Wizard is used to:

• Get accounting information for each network user using their terminal ID and a CA JARS Wizard facility called file matching. This involves CA JARS Wizard searching a second file to find the accounting information associated with each terminal ID. Complete information on file matching can be found in the Wizard Reference Guide.
• Calculate the charge for the user. In this sample the charge is based on number of characters and number of messages transmitted to and from the terminal. Because CA JARS Wizard has a flexible language for computing new fields, the charge can be based on anything in the record. for instance, a surplus could be charged for network usage during peak hours.
• Sum the charges for the accounts and print a report that shows the charge by account.
• Write a debit record for each account. This debit record contains the account information and the calculated charge. All debit records are read in a product run that reports on charges by account. The charge for using the network is added to the other charges that is calculated on an account basis.

JSINET1 executes on the assumption that you have a secondary file containing one record for each unique terminal ID at your site. Each record in this secondary file also contains the necessary debit record accounting information. Report JSINET1 assumes that the Terminal ID is in positions 1 to 8 and the accounting information is in positions 10 to 25, as follows:

         1         2    2
1........0.........0....5
terminal accounting info.
ID

If you do not have such a file, you must set one up or alter the JSINET1 control statements accordingly.

A sample of this file is located in CAJROPTN member JSINET1.

To execute JSINET1, set up the necessary JCL for the run. Be sure to include DD statements for the following ddnames:

• CAIJWI (your session file)
• CAIJWI2 (the secondary file containing account information)
• CAIJWOP (the output file for the debit records)

The sample report produced with the debit record output file when JSINET1 is shown on the next page.