Hierarchical structure of bundle output

The output for a report bundle can contain the following elements, in the order shown:

  • Bundle banner (optional)
    A bundle banner is printed at the beginning of the bundle if you defined a bundle banner page with the banner type of Heading or Both and linked that banner definition to the bundle definition from the Bundle Detail panel.
    Note: You can associate only one banner member with a bundle definition. If you specify Both as the banner type the content for the heading and trailing banners will be the same unless you included the special /BEGSEP and /ENDSEP tags in the banner member to divide the content into different heading and trailing sections. This also applies to bundle recipient banners and report banners.
  • Bundle manifest

    Output Manager automatically prints a manifest for the bundle instance. The manifest lists all of the reports that were collected for the bundle instance, arranged by bundle recipient.

  • Bundle recipient packages. Information for each bundle recipient. Bundle recipients and reports are included in the bundle output in the same order in which they are listed on the Bundle Detail panel and the Bundle Recipient Detail panel. If no reports are collected for a recipient, the recipient is not included in the bundle output.
    • Bundle recipient banner (optional)

      A bundle recipient banner is printed at the beginning of the information for a recipient if you defined a bundle-recipient banner page with the banner type of Heading or Both and linked that banner definition to the bundle-recipient definition.

    • Bundle recipient manifest

      Output Manager automatically prints a manifest for each bundle recipient. The manifest identifies the recipient and then lists the reports that were collected for the recipient.

    • Reports for the recipient. For each report that a recipient is to receive, the following information can be displayed:
      • Report banner (optional)

        A report banner is printed before the report data and any optional PRSET characters if you defined a report banner with the banner type of Heading or Both and linked that banner definition to the report definition.

      • PRSET print-control characters (optional)

        If you specified a PRSET member in the report definition, the binary control characters that this member contains are inserted into the report output at this location. A PRSET member usually contains control characters for controlling how a report is physically printed on a printer. For example, if you use a printer that supports Advanced Function Printing (AFP), you can define a PRSET member that contains AFP structured fields. If you assign a PRSET member to a bundle report but do not physically print the bundle on a printer that supports the PRSET control characters, the characters are just inserted into the report output stream before the report data.

      • Report data

        The basic or custom report data is presented. If the SYSOUT for a report was not generated and archived, the report is not included in the bundle instance.

      • Report banner (optional)

        A report banner is printed after the report data if you defined a report banner with the banner type of Trailing or Both and linked that banner definition to the report definition for the report.

    • Bundle recipient banner (optional)

      A bundle recipient banner is printed after all of the reports for a recipient if you defined a bundle recipient banner page with the banner type of Trailing or Both and linked that banner definition to the bundle recipient definition.

  • Bundle banner (optional)

    A bundle banner is printed at the end of the bundle if you defined a bundle banner page with the banner type of Trailing or Both and linked that banner definition to the bundle definition.