Activating a bundle

You activate a bundle to open a bundle instance and begin the collection of reports for that instance.

While the bundle instance is open, Output Manager defers the automatic printing of all reports that are listed in the bundle definition. Instead, Output Manager records all bundle report instances that are captured for the bundle instance in the database. If an application generates the same report multiple times during the bundle window, all instances of that report will be included in the bundle instance for each recipient that is to receive the report.

For a single bundle definition, only one bundle instance can be open at a time. If you attempt to activate a bundle definition that is already activated, Output Manager issues an error message.

While a bundle instance is open, any changes that you make to the bundle definition or the related administrative definitions will not affect the open bundle instance. The changes apply only after you deactivate the current bundle instance and then activate the bundle again to open a new bundle instance.

To issue the bundle activation command, use either one of the following methods:

• If you created a batch job for issuing the BUNDLE ACT command for the bundle instance, 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 the BUNDLE ACT command by using the Modify operator command. Use the following syntax:

  MODIFY started_task_name,BUNDLE ACT 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.

Activating all bundles