Deactivating a bundle instance

You deactivate a bundle instance that is open to stop the collection of reports and print the accumulated reports.

To do so, you use the BUNDLE DEACT command. By default, when you issue this command, Output Manager automatically submits the bundle print job that you specified in the bundle definition. You can prevent the automatic submission of this print job by setting the Submit print job at deactivation option to No in the bundle definition. In this case, the bundle data remains in the database so that you can reprint it later from the Bundle History panel.

Output Manager writes the accumulated bundle reports, arranged by recipient, in a single output stream. In the output, the bundle recipients and their reports appear in the same order in which they are listed in the bundle definition.

In addition to the usual BUNDLE DEACT command, Output Manager provides the following deactivation commands that apply to all open bundle instances:

  • BUNDLE DEACTALL deactivates and prints all open bundle instances. Usually, you issue this command prior to stopping the Output Manager started task.
  • BUNDLE LIST lists the open bundle instances that will be deactivated and printed when you issue the BUNDLE DEACTALL command. No bundle instances are actually deactivated and printed. Use this command to check the bundle instances that will be processed by the BUNDLE DEACTALL command.
  • BUNDLE REACT deactivates and prints the reports captured for the specified bundles and then activates the selected bundles to resume collection of reports in the bundle.

To issue any of the bundle deactivation commands, use either one of the following methods:

  • If you created a batch job for issuing the bundle deactivation command, run the batch job by itself or as a job step within another batch job. Before submitting the batch job for execution, ensure that it meets all of the syntax requirements for jobs that issue bundle control commands. For more information, see Summary of batch job customization steps.
  • Issue a bundle deactivation command by using the Modify operator command. Use the proper command syntax, as follows:
    • MODIFY started_task_name,BUNDLE DEACT bundle name

      Where started_task_name is the name of the Output Manager started task that you are using and bundle name is the unique bundle name that you specified in the bundle definition.

After deactivation, Output Manager resumes the individual automatic printing of the reports that are listed in the bundle definition until the bundle is activated again.

Deactivating all bundles

Use SBJTSAMP member BJT@BUNP to deactivate all bundles:
  1. Modify your customized copy of SBJTSAMP member BJT@BUNP to specify:
  2. Submit BJT@BUNP.