Using internal results of summing checks
On detecting global summation consistency errors BCHECK generates an output file named
UTI.tsn.time-stamp.BCHECK
tsn
Four-digit task sequence number
time-stamp
Date and time of file generation
Format: ddhhmmss
This file holds the internal results from the summing run, which BCHECK can then evaluate as input information for a subsequent sort run.
In order to have BCHECK evaluate the output file from the summing run, the following actions must be completed before the sort run:
the output file UTI.tsn.time-stamp.BCHECK must be assigned the file link name BCHECK, and GENERATE SORTING must be specified in the CHECK statement for the sort run.
If there is no usable data for a SORTING run in the UTI file, the file will be deleted when global errors occur.
Evaluating the output log
In a summing run BCHECK writes the following information to SYSLST:
all messages and, on detecting global summation consistency errors,
the command sequence for a sort run coordinated with the summing run (excluding the CREATE-FILE and ADD-FILE-LINK commands for the two work files SORTWK and SCRTCH1).
Editing the SYSLST file
If you assign SYSLST to a file prior to a summing run, you can edit the BCHECK output using EDT. The edited file with the generated SORTING statements can be used for the sort run.
Within the summing run, BCHECK identifies the record types, sets or keys in which errors are present, and the consistency criteria involved. The SORTING statements generated contain only these objects and the corresponding TYPE clauses. Realm selection is limited to the minimum necessary.