|
|
|
The INPUT statement identifies the glossary to be used with the primary input file.
The second INPUT statement, as discussed in JARSWZ10, is used to define a secondary file for file matching. This is done in conjunction with the COMPUTE IF MATCHED statement. In this example, the secondary file records are formatted to contain a user information code in position 1 and corresponding department name (USER/FIELD) in positions 2 to 17.
The COMPUTE IF MATCHED statement uses the information in positions 2 to 17 to replace the information in the USER/FIELD of the primary input record when a match occurs between a primary input file record and a secondary file record.
Note that department names are only assigned to primary input file for records meeting the selection criteria specified in the SELECT statement; the SELECT statement restricts the COMPUTE IF MATCHED statement processing. If COMPUTE(S) IF MATCHED had been used, however, all primary input file records with a match in the secondary file would be assigned a department name. The (S) suffix code ensures that the COMPUTE is performed before any records are selected.
The new statement used in this example is:
This statement specifies that CA JARS Wizard create an output file in the same format as the input file and write out all the records from the input file. Hence, all the input file records, whether selected or not and updated or not, are written out to the output file.
CA JARS Wizard produces a list of execution statistics at the end of all reports. These statistics concern the processing activities. Listed next are some of the execution statistics produced by CA JARS Wizard as displayed in JARSWZ12:
The number of sorted input records read from the primary input file.
The number of records written out to the output file is given. Note that the number of output records is equal to the number of input records, as effected by the OUTPUT ALL statement.
The total number of records read from the input file.
The number of records selected for processing. (This number represents the number of records meeting the selection criteria.) Note that even though only 2119 records were processed through the COMPUTE IF MATCHED logic, all 2168 input records were written out.
The number of records from the input file that failed the selection criteria.
The number of input records that had a match with a secondary file record.
Lists the number of instructions executed in a COMPUTE statement.
In this case, we only have one instruction in a COMPUTE statement. Consequently 2119 COMPUTES were executed on the 2119 selected records. Note: However, that this statistic describes the number of records for which the COMPUTE statement was executed. Suppose the COMPUTE statement had been as follows:
COMPUTE IF MATCHED THEN USER/FIELD 2CC2-17, USER/ID EQ BLANKS
Because there are two instructions in this COMPUTE statement, the number of COMPUTATIONS listed in the execution statistics would be doubled.
The number of records read from the secondary file. In this example, these are the table records.
The number of matches for the primary input file against the secondary input file.
The number of misses for the primary input file against the secondary input file.
Lists the number of bytes of virtual storage used.
| Copyright © 2012 CA. All rights reserved. |
|