When print stream reports are decollated using transformation, Control-V can perform the same decollation functions for print stream reports that it does for text reports.
Transformation is the process used in decollation to extract the text from print stream reports (as illustrated in Figure 466) as it appears in print reports (as illustrated in Figure 467).
Figure 466 Print Stream Displayed in Raw Format
Figure 467 Print Stream Displayed in Print Format
As Figure 466 illustrates, it is not simple nor practical to locate the text directly from a raw formatted print stream report. To accommodate this, the transformation process performs the following three actions on a print stream report:
Specifically, the Normalization process does the following
Normalized AFP reports have additional 2 NOP (comment) records for each page. These records include the IMM that is active for the page, and indicate whether the page is a front page or back page for duplex reports.
All Group information and TLE records are removed from the Normalized report.
Normalized Xerox reports are always Metacode, with DJDE lines in EBCDIC for each page.
All reports use the same JSL (PROMETA) and the same JDE. During the creation of the Normalized report STARTON is used, and for viewing the Normalized report NMOJOB is used.
If the original report was an LCDS report, after Normalization it becomes a Metacode report.
This information enables you to view a report using the same resources that the report used during decollation.
If a report resource changes, a new version of that resource is stored in the resource library. After the changed resource is stored, all subsequent versions of the report use the new version of the resource when you view the report. Earlier versions of the report continue to use the previous resource as defined for them. This enables you to view or print a report with its own original resource, even after the original resource is no longer in use.
During the report decollation process, a special Resource Set record associated with the report is created in the Permanent User File, whose key is stored in an associated SYSDATA record. The Resource Set record references all resources used by the decollated report. Duplicate Resource Set records are not created, so that the SYSDATA record points to the existing Resource Set record if the current decollation uses the same set of resources as one of the previous decollations. Record Set records can be accessed through the Resource Sets (DO.2) screen. For more information on the DO screen as related to Resource Sets, see Resource Sets.
Parent Topic |