This section explains how JCL checking at submission time can be extended to jobs that are normally held before Job Analysis.

Introduction

In a system with BMC ThruPut Manager, comprehensive JCL checking is provided as soon as the job is submitted. The early JCL checking facility applies to all jobs processed by BMC ThruPut Manager. If an error is found, an appropriate message is provided, and the job is failed as soon as it is submitted. With this facility there are no costly reruns and no resources wasted.

There are certain type of jobs that do not receive the benefits from the early JCL verification, unless you instruct BMC ThruPut Manager to process them too. There are three distinct groups:

• Jobs submitted with TYPRUN=SCAN.
  • SCAN jobs receive a cursory JCL checking, where gross errors can go undetected. You can choose to give these jobs full BMC ThruPut Manager JCL checking.
• Jobs submitted with TYPRUN=HOLD.
  • Jobs that are submitted with HOLD do not receive full JCL checking until execution time. With BMC ThruPut Manager, you can choose to give these jobs full JCL checking at submission time.
• Jobs submitted with a /*SETUP JES2 control statement.
  •  Jobs submitted with a /*SETUP statement are normally held before Job Analysis. You can choose to give jobs of this type BMC ThruPut Manager processing as soon as they enter the system.

JCL Validation Service

The installation can now offer a JCL Validation Service to their users. Jobs that are submitted with TYPRUN=SCAN can receive the BMC ThruPut Manager's comprehensive JCL verification. If any error is encountered, informative messages are included with the JCL listing. This is a BMC ThruPut Manager option that your installation can activate.

Implementation Summary

Keywords are provided with the JES2 TMPARM statement to define what you want BMC ThruPut Manager to do with TYPRUN=SCAN, TYPRUN=HOLD and /*SETUP jobs.

This keyword is used to indicate to BMC ThruPut Manager that jobs using the /*SETUP statement should not be held. Note that the standard /*SETUP message is sent to the console. If you want the jobs to be held after Job Analysis, you must make a specific request in JAL. The logic variable $SETUP is provided to allow you to determine the presence of a /*SETUP control statement.

This parameter does not affect jobs which are exempt from BMC ThruPut Manager processing; the /*SETUP statement receives standard processing for jobs submitted in an Exempted class.

If this keyword is not included, jobs with a /*SETUP statement receive standard JES2 processing.

If this keyword is coded, jobs receive BMC ThruPut Manager processing. After Job Analysis the jobs are put in HOLD status. The installation can alter this with JAL. The logic variable $TYPHOLD is provided to allow you to determine whether or not this keyword was present.

If this keyword is not included, jobs submitted with TYPRUN=HOLD receive standard JES2 processing. In this case, the jobs are held prior to BMC ThruPut Manager analysis.

If this keyword is coded, BMC ThruPut Manager does JCL analysis for jobs submitted with TYPRUN=SCAN. After the JCL analysis phase, the jobs are not allowed to continue to execution. When errors are found, appropriate messages appear with the JCL listing.

If this keyword is not included, jobs submitted with TYPRUN=SCAN receive standard JES2 processing. In this case, the jobs are not processed by BMC ThruPut Manager, therefore they do not benefit from the JCL analysis provided by the Job Analyzer.

To implement JCL verification, code the appropriate keyword in the TMPARM statement.

Dependencies

There are no other dependencies with this facility.

TMSS Initialization Statements

There are no TMSS initialization statements for this function.

Facilities Summary