Output Manager administrative basics tutorial
This section is a high-level tutorial of Output Manager administrative objects: how they are linked together, and how you can use them to select, store, process, and distribute your data. This section will introduce you to basic concepts to get you started on the right track. Tasks are included to help you follow along and see how the administrative objects work together.
Output Manager fundamentals can be broken down into the following steps:
- Tell Output Manager what to capture and where to store what is captured
- Define a report
- Specify who should receive the report
To perform this tutorial, you need the following SBJTSAMP members:
- BJT@JCBP: This sample batch job provides
JCL for generating the report output on which the custom report is
based. It is recommended that you use this sample batch job as a learning
tool: the appropriate values to capture this job will be provided
in the following tasks. This JCL is for tutorial and demonstration
use only. Normally, a business application generates the base report,
and Output Manager captures
all or some of its data from the JES spool based on the selection
criteria that you define. Note: Before you begin, copy BJT@JCBP to a PDS library that you have access to, and make the following edits:
- Edit the Job card to meet your company's standards. If you have to change the job name, note what you change it to. In the tasks below, we will define the selector rule to match these jobs, and you will need to know the values you specified.
- Specify a MSGCLASS and a SYSOUT class (in SYSUT2) that will remain on the spool. If the default values X and N cannot be used, take note of which SYSOUT classes are used: you'll need to know the class when defining your selector rule.
- BJT@PRBP: This member contains the sample report data that is generated by BJT@JCBP. This data covers six bank branches. Your custom report will contain a subset of this data (the data for the Ash branch).