|
|
|
|
|
It is most common to process (decollate) a specific group of reports that have identical criteria using generic decollating missions. For example, all production reports are retrieved by Control-D, made available for online viewing for three days and archived for one month. In this case, one generic decollating mission can achieve that goal. Printing characteristics can then be assigned to the output class, enforcing data center standards for this type of output.
In the above example, all production MSGCLASS output is processed by one (generic) decollating mission, making data center standard enforcement quite easy. What happens, though, if data center standards need to be enforced for a number of different decollating missions? This situation can become even more complicated if many or all decollating missions in the data center are required to meet the standards set. The OUTPARM option enables you to enforce data center standards on a global level (that is, for one or more different decollating missions, whether generic or non-generic).
The advantages of being able to enforce data center standards can be demonstrated with the following example. Many components in the system may produce "dumps," usually as a result of an abend. These dumps are usually extremely large and utilize high percentages of system spool space. The dumps are important for debugging purposes, so that even if the system spool is almost full, purging the dumps from the spool is not a practical alternative. This then results in having to print the dumps unnecessarily (which wastes paper when compared to online viewing). At times it may be necessary to print dumps – for example, vendors of software products may require a printed dump. You can force printing a dump 2-up or, even better, 4-up.
Parent Topic |