About printing bundle instances

You must manually define a bundle print job for any bundles that you want to print. Then, in the bundle definitions, you specify the name of the PDS member that contains the bundle print job.

Only one print job can be specified in a bundle definition. You can specify the same print job member in multiple bundle definitions, or create and specify different print job members for different bundle definitions. For more information, see Creating a bundle print job.

By default, when you deactivate a bundle instance, the Output Manager started task automatically submits the bundle print job that is specified in the bundle definition to print the entire bundle instance as a single output stream. The output is written to the location that you specified in the print job, for example, to a printer, a SYSOUT data set on the spool, or DASD data set. Usually, a bundle instance is physically printed on a printer.

If necessary, you can temporarily disable the automatic submission of the bundle print job at deactivation. For example, you might want to prevent printing because your printer is not working. To disable the automatic submission of the print job, you must set the Submit print job at deactivation option to No in the bundle definition.

If you do not specify the name of a bundle print job in the bundle definition, or if you disable the automatic submission of the print job at deactivation, the bundle instance will still be stored in the bundle history table (BJTBHI). You can "reprint" the bundle later from the Bundle History panel.

From the Bundle History panel, you can reprint a deactivated bundle instance in full or in part. If you do so, Output Manager uses the print job that you specified in the bundle definition by default. However, you can specify another print job when you confirm the reprint request. For example, if you are reprinting reports for a particular recipient, you might want to create a print job that prints the reports on a printer that is located near the recipient.

If you link an optional PRSET member to the report definition for a bundle report, Output Manager will insert the binary control characters from that member into the bundle output stream to control the physical printing and formatting of that bundle report. If the printer does not support the control characters, the control characters will just appear in the bundle output stream and not affect print processing.

Note: During bundle printing, Output Manager ignores any printing-related "report behaviors" (including a set of printer attributes) that are specified in a recipient ID for a bundle recipient.