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.

ACCESS statement

The ACCESS statement instructs Job Optimizer how the immediately preceding DD statement is used in the current run (for input, for output, or for update). Job Optimizer saves this information in the History data set and uses it to establish pipes between writers and subsequent readers of data sets.

You can specify ACCESS at the DD level only.

If you change a DD statement's access intent from what is saved in the History data set, Job Optimizer must reevaluate this job before making decisions to execute steps in parallel and establish pipes for the current run.

If you include multiple ACCESS statements in the JCL stream after one DD statement, only the last ACCESS statement is processed and saved in the History data set.

Note

You are responsible for properly recording the type of ACCESS that will be made with the referenced DD statement. The ability of Job Optimizer to properly execute steps in parallel and establish pipes is affected by the accuracy of the data in the History data set.

The ACCESS statement has the following syntax:

//*BSLCNTL ACCESS {INPUT | OUTPUT | UPDATE}


Related topic

JTL-statements


 

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