Configuring IBM Tivoli Output Manager for data store
To continue to save an HCL Workload Automation for Z copy of the sysouts in the data store, add a Tivoli Output Manager sub-selector to Tivoli Output Manager. In this way, you have sysouts captured in both Tivoli Output Manager and HCL Workload Automation for Z without impacting either product.
To add a sub-selector, perform the following steps:
- From
Administrative Functions
go theSearch for Selector Rules
dialog to retrieve the selector rule you defined for the HCL Workload Automation for Z sysouts. Enter thess
command next to the selector name to add a sub-selector. For example:The
Subselector Rule
dialog is displayed. - In the
Subselector Rule
dialog, setStatus
toSkip
and specify the destination used for the job log data store in theDestination
field. The value forDestination
must be equal to the value defined for the DSTDEST keyword of the RCLOPTS initialization statement of HCL Workload Automation for Z.Also, select (/)
Advanced Selection criteria
. For example: - In the
Advanced Selection
dialog, specify the JES queue that works for your system. For example, if all the output classes on your system are set as HOLD,HOLD, specifyAll
as shown next: - In the
Subselector Rules
dialog, move the sub-selector that you have just created as the first sub-selector in the list. In this way, IBM Tivoli Output Manager will skip all the sysouts with the destination that you specified in step 2. - Save your changes and return to the list of selector rules. The top level selector rule you just defined is now eligible to process any job log generated by HCL Workload Automation for Z.
- Save and enter the
ACT
primary command to activate your changes.