Creation and change of UCF members

During job analysis, Job Optimizer scans the active UCF member to determine whether any site-specific actions are to be taken for a given job step or DD statement. During job processing, Job Optimizer scans the active UCF member for overriding instructions for the program and ddnames that it encounters while it is processing JCL statements.

You can create a UCF definition to bypass programs that are unsuited for batch job performance processing. Rather than specifying selection criteria for a job in all job policies that might be active on an image, you can bypass the job at the installation level by using a UCF definition.

When a batch job is initiated in a BatchPlex, Job Optimizer checks the selection criteria that you specify in the UCF definition before reading the job policy. When Job Optimizer encounters selected installation conditions (program names, ddnames, or allocation esoterics), Job Optimizer performs the action that you specify in a UCF definition (such as BYPASS, TARGET, or NOOP).

As a result, you can use a UCF definition to specify additional information for a specific job, or you can specify the NOOP action to instruct Job Optimizer to use the job policy's action definitions. For example, a program that uses control cards to direct its behavior (such as SAS or IDCAMS) might not be a suitable candidate for Job Optimizer performance processing. This is because Job Optimizer cannot determine how the control cards are to be used and cannot split or target the job steps.

For information about creating UCF definitions, see sample member UCFPOL00 in the SAMPLIB data set.