TARGET statement

The TARGET statement names the MVS image on which Job Optimizer is to execute the job step if the job step is split.

The TARGET statement does not affect whether the job step is split.

You can specify TARGET at the step level only. The TARGET statement never overrides a job-level BYPASS or ANALYZE statement.

When a TARGET statement overrides a job-level SPLIT statement and a step-level SPLIT statement is not specified, the step is targeted to run on the specified MVS image if all constraints are relieved. If all constraints are not relieved or if the targeted MVS image is not active, the step is not split. This step runs in the JES initiator of the MVS image on which the job was initiated.

When a TARGET statement is used with a step-level SPLIT statement, the step is targeted to the run on the specified MVS image, regardless of whether constraints are relieved. If the MVS image is not active or if Job Optimizer is not running on the named MVS image, the affected step is bypassed and runs in sequence in the JES initiator on the MVS image on which the job was initiated originally.

You must include one parameter on the TARGET statement, which causes the referenced step to be targeted to run on the MVS image that is named by the parameter.

Value

Description

systemName

Name of an MVS image that is included in the BatchPlex definition

@HOME

MVS image on which the job was originally initiated

^HOME

Any valid image in the BatchPlex except for the home image

The TARGET statement has the following syntax:

 //*BSLCNTL TARGET {systemName | @HOME | ^HOME}

Was this page helpful? Yes No Submitting... Thank you

Comments