

Introduction › Types of Report Processing › Stacked Report Processing
Stacked Report Processing
Stacked reports are processed as follows:
- Output records for a page accumulate in memory until either
- Exclusive segments within the report identification text are examined in order by report for a match.
- Any exclusive segment that has already been used and is not defined as reusable, is not examined, and is ignored.
- The first exclusive segment for which a match occurs is marked as currently selected, and the exclusive segment previously marked as currently selected, if any, is unmarked (that is, not currently selected).
- If matching text is not found, the exclusive segment previously marked as currently selected remains marked as currently selected.
- The beginning definitions of overlapping segments within the report identification text are examined for matches.
- Any overlapping segment that has already been used and is not defined as reusable is not examined and is ignored.
- Any overlapping segment for which a match is found on its beginning definition is marked as currently selected.
- Any overlapping segments already marked as currently selected remain marked as currently selected.
- The page is written to any report with a currently selected segment.
If no reports have currently selected segments, the page is discarded (only if the undefined report identifier UNDEF, which is described later in this guide, is not used).
- Currently selected segments are identified as used, and in the case of non-reusable segments, are no longer examined when searching for subsequent matches.
- The ending definitions of overlapping segments within the report identification text are examined for matches.
Any overlapping segment for which a match is found is unmarked (that is, not currently selected).
Copyright © 2013 CA.
All rights reserved.
 
|
|