Limited supportBMC 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.

Naming conventions


The MainView Batch Optimizer BatchPlex control data set contains several types of definition members.

The MainView Batch Optimizer dialog identifies these members by using their member name prefix, the first keyword in the member, or the user ID. The appropriate member name prefix, keyword value, and user ID depend on the member type. For example, a new data policy should have a name that starts with DATPOL (for example, DATPOL02), keyword DATAPOLICY, and user ID DATAPOL, if needed.

Note

The MainView Batch Optimizer dialog sets the appropriate member values. Consequently, BMC recommends using this dialog to create all members.

The following table shows the allowable member name prefix, first keyword, and user ID for each member type. In the table, xx can be any two characters that are alphabetic, numeric, or the characters $, @, or #.

Name

Keyword

User ID

Description

BPLEXxx

BATCHPLEX

BPLEX

BatchPlex definition member that identifies the MVS images to which Job Optimizer can direct job steps for processing, and on which Data Optimizer can provide I/O performance processing

DATPOLxx

DATAPOLICY

DATPOL

Data policy definition that associates one or more data set characteristics with a Data Optimizer response or type of I/O performance processing

JOBPOLxx

JOBPOLICY

JOBPOL

Job policy definition that associates one or more batch job characteristics with a Job Optimizer response or type of job performance processing

UCFPOLxx

UCFPOLICY

UCFPOL

UCF policy definition that defines BatchPlex environmental 'special handling' conditions for Job Optimizer processing

BCSCMDxx

None

User ID of the user that last edited the member

BMC Software Consolidated Subsystem (BCSS) commands data set member that defines start-up characteristics for the subsystem

PIPPRMxx

PIPEPARMS

PIPPRM

Pipe initialization parameters member that contains the Job Optimizer Pipes Subsystem startup parameters

PIPLSTxx

PIPELIST

PIPLST

Pipe Policy List member that contains a list of Pipe Policy Table member and data set names

Job Optimizer Pipes loads the rule definitions that are contained in each of these members during subsystem startup.

PIPPOLxx

PIPEPOLICY

PIPPOL

Pipe Policy Table member that contains a set of rule definitions

These rules define pipe data set information such as the pipe name, attributes, and jobs that will participate in the piping.

This section provides more information about the following topics:



 

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