Skip to Content
Information
Limited support BMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Batch Optimizer (Advanced and Standard) 2.9.

Pipe usage through JCL

Pipes can be used through JCL with or without a Pipe Rule.

By coding the SUBSYS parameter in the JCL DD statement, a data set will be replaced by a pipe.

The only required parameters in the DD statement are DSN and SUBSYS. The SUBSYS parameter should specify the Job Optimizer Pipes Subsystem name (as defined in the BatchPlex member BPSSIDR parameter) and the subsystem parameter PRTYPE that contains the participant type. The following code shows an example:

//SYSUT2 DD DSN=TEST.FILE,DISP=(NEW,KEEP),
//  SUBSYS=(MBOP,'PRTYPE=WTR'),
//  DCB=(LRECL=80,BLKSIZE=800,RECFM=FB)

In this example, the participant is identified as a writer by the PRTYPE subsystem parameter. If a Pipe Rule exists for this data set, the pipe parameters are determined according to the Pipe Rule and the Pipe Rule defaults. If no Pipe Rule is defined for this data set, all required parameters are taken from the Pipe Rule defaults.

Related topics

Using-Job-Optimizer-Pipes

Glossary



 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

MainView Batch Optimizer (Advanced and Standard) 2.8