|
|
|
The control statements used in JSINET1 are described below. Complete descriptions of all CA JARS Wizard control statements can be found in your CA JARS Wizard Reference Guide.
PARAMETER
The PARAMETER control statement specifies options for a CA JARS Wizard run.
creates a cross-reference of the data fields used in the run and the statements they are found in. This cross-reference listing is printed in addition to the control statements and the report for the run.
suppresses the CA JARS Wizard error handling routine.
INPUT
INPUT statements are used to identify the CA JARS Wizard glossary and/or the input files for the run. In JSINET1 two INPUT statements are given:
defines the matching key field for the secondary file. Here, the first eight positions for each record are the matching key.
designates the terminal ID field of the primary input file as its matching key field.
indicates that the secondary input file is a table file to be read completely at the start of the run. Therefore, the entire file is available for searching during the run. The field in positions 10 through 25 of the secondary file contains the account information.
The notation 2CC10-25 serves two purposes:
SELECT
The SELECT statement identifies the record type of the Network Accounting Billing Records.
DEFINE
Eleven DEFINE statements are given in JSINET1. Each defines a field for the run. All of the defined fields are initialized each time a new record is processed. The first nine DEFINE statements define fields for the debit record. There are:
One-byte filler field, initialized as a blank.
Eight-byte field, initialized as DEBIT. This field identifies the CA JARS record as a DEBIT record.
One-byte field, initialized as a blank, and used to identify the CPU.
Eight-byte field, initialized as blanks, and used for terminal identification.
Six-byte field, initialized as blanks, and used for the date (YYMMDD).
Eight-byte field, initialized as blanks, and used for the job name.
Six-byte field, initialized as blanks, and used for the time (HHMMSS).
20-byte field, initialized as blanks, and identifying the programmer.
Six-byte field, initialized to zero, and used for the debit amount.
Six-byte field, used to hold the sum of the network messages transmitted.
Six-byte field, used to hold the sum of the network characters transmitted.
COMPUTE
Four COMPUTE statements are executed in JSINET1.
The first COMPUTE statement evaluates the file matching between the primary input file and the secondary file. It also defines a new field OACCT(16 bytes) and assigns a value to it based on the results of file matching. If a match occurs on the terminal/ID of a primary input file record and a secondary input file record, OACCT is assigned the value of the account information in positions 10 to 25 of the secondary file. Otherwise, OACCT is assigned a value of the terminal/ID.
Notice the (P) suffix code appended to the first COMPUTE statement. This code indicates that the COMPUTE should take place before the primary input file records are sorted. This is necessary because the SORT occurs on the OACCT field.
The remaining three COMPUTE statements simply assign values to fields: NETMESSAGES, NETCHARACTERS, and OTERMINALID. OTERMINALID is assigned the value of TERMINAL/ID in the primary input record. NETMESSAGES and NETCHARACTERS are calculated from other fields in the primary input record.
SORT
The SORT statement identifies the sequence in which the input records should be sorted prior to processing. Here the SORT is performed on OACCT (the account information). Note that the OACCT field is created and assigned a value in the COMPUTE(P) statement before the SORT.
BREAK
BREAK statements define logical groups of records. Here data is split into groups by OACCT. Records with the same account information are grouped together.
A SORT statement must be included in a CA JARS Wizard run when a BREAK statement is used. The fields specified in the BREAK statement must be included in the SORT statement and must be specified in the same order as the SORT statement.
HEADING
HEADING specifies a title for the report. Here the title for the report (created in addition to the output file) is TOTAL NETWORK CHARGES BY ACCOUNT.
LIST(SUM)
A summary listing is requested along with the output file. Each line of the summary listing list debit information for a different account. The LIST(SUM) statement identifies the data fields to be summarized and printed. This data includes the:
OUTPUT
One debit record is produced for each unique account. All records are written to the file identified by ddname CAIJWOP. The OUTPUT statement lists the fields to be included in each debit record.
| Copyright © 2012 CA. All rights reserved. |
|