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.

Scope of JTL statements

The scope of a Job Transformation Language (JTL) statement is determined by its placement in the job stream. JTL statements are valid only when they are placed immediately after a JOB (job level), EXEC PGM= (step level), or DD (DD level) statement. JTL statements that are placed at any other location within the job stream are treated as JCL comment statements (they are ignored). No JTL statements are supported at the EXEC procedure name level.

At the job level, the following JTL statements are valid:

  • BYPASS
  • ANALYZE
  • SPLIT (the default action, or as set by the READJTL command)
  • NOCC
  • NOSMF
  • JOBKEY
  • DIRECT

At the step level, the following JTL statements are valid:

  • BYPASS
  • SPLIT
  • TARGET systemName
  • SERIALIZE
  • NOSERIALIZE
  • SERIALIZECC
  • JESCC
  • CC
  • NOCC

At the DD level, the following JTL statement is valid:

  • ACCESS type

You can specify multiple JTL statements at each level. If the statements do not conflict, all of the statements are observed. If the statements conflict, the last JTL statement that is encountered is used. For example, the SPLIT and NOCC statements conflict. If both statements are specified for a job step and NOCC is specified second, NOCC is observed, and the SPLIT statement is ignored.

Related topic

Job-Transformation-Language



 

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