×
 
 
  •  
$helper.renderConfluenceMacro('{bmc-global-announcement:$space.key}')

Limited support

   

BMC 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.
MainView Batch Optimizer (Advanced and Standard) 2.8 ... Reference Job Transformation Language

Step-level statement usage

A step-level statement must follow immediately after an EXEC PGM= programName statement. A step-level statement affects only the step that precedes it. Step-level statements are not required. If you do not supply a step-level statement, the step is processed according to the specified job-level statement, the job-level default of SPLIT, or as set by the READJTL command.

Step-level statements do not override the BYPASS or ANALYZE job-level statements. If a step-level JTL statement is detected when the BYPASS or ANALYZE job-level statement is in effect, the step-level statement is ignored (treated as a JCL comment).

Related topic

Job Transformation Language



Was this page helpful? Yes No Submitting... Thank you
Last modified by Amruta Hingane on Jan 15, 2019
job_transformation_language_jtl step-level_statements reference

Comments

Log in or register to comment.

Job-level statement usage
DD-level statement usage
© Copyright 2013 - 2017 BMC Software, Inc.
Legal notices

Powered by Atlassian Confluence and Scroll Viewport

© Copyright 2005-2024 BMC Software, Inc. Use of this site signifies your acceptance of BMC’s Terms of Use . BMC, the BMC logo, and other BMC marks are assets of BMC Software, Inc. These trademarks are registered and may be registered in the U.S. and in other countries.