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.

JTL syntax

JTL statements are JCL comment statements and have the following syntax:

//*BSLCNTL <keywordParameter>

Observe the following syntax conventions for JTL statements:

  • Each statement must begin with the string //*BSLCNTL. There must be no intervening spaces in this string.
  • The //*BSLCNTL string must be followed by one space and a keyword.
  • If the keyword has a parameter, include one space between the keyword and its parameter.
  • Comments can follow the keyword (or parameter) when one space separates the keyword (or parameter) and the comment.

The following examples are valid JTL statements:

//*BSLCNTL BYPASS
//*BSLCNTL ANALYZE
//*BSLCNTL SPLIT
//*BSLCNTL CC
//*BSLCNTL NOCC
//*BSLCNTL NOSMF

//*BSLCNTL TARGET SYSP

//*BSLCNTL ACCESS OUTPUT
//*BSLCNTL SERIALIZE
//*BSLCNTL NOSERIALIZE
//*BSLCNTL SERIALIZECC
//*BSLCNTL JESCC
//*BSLCNTL DELHIST
//*BSLCNTL SRP
//*BSLCNTL JOP
//*BSLCNTL AUTO
//*BSLCNTL NOTAPE
//*BSLCNTL TAPE

//*BSLCNTL JOBKEY label

//*BSLCNTL DIRECT

//*BSLCNTL HPU (PTF BPB1552 applied)

//*BSLCNTL NOHPU (PTF BPB1552 applied)

Related topic

Job-Transformation-Language



 

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