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.

JOBKEY statement

The JOBKEY statement causes Job Optimizer to substitute the label value as a unique identifier for the job name to manage job-related history and make the job eligible for optimization.

You can specify JOBKEY at the job level only by placing the statement after the JOB statement and before the first EXEC statement in the job.

If you have a set of jobs that have the same steps and data sets but the job names change each time a job is submitted, you can use the JOBKEY statement to provide a static name to store and retrieve the history for each job.

The label value is a string containing up to eight characters (letters A-Z, numbers 0-9, $, #, or @). The first character cannot be a number. Lowercase characters are converted to uppercase.

The JOBKEY statement has the following syntax:

//*BSLCNTL JOBKEY label


Related topic

JTL-statements


 

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