Checking AutoEdit Syntax and Results

When Control-M detects an AutoEdit syntax error in a JCL member during submission, the submission is canceled by Control-M. Therefore, it is good practice to check the syntax of AutoEdit statements while the member is being prepared.

Furthermore, when the syntax is correct, you may want to verify that the AutoEdit statements return the desired results. For example, you may want to check that you specified the correct AutoEdit date variables for a job that performs end-of-year processing.

The AutoEdit Simulation facility, utility CTMAESIM tests AutoEdit syntax and JCL setup. This utility simulates the actions of the Control-M submission mechanism, which performs AutoEdit processing and JCL setup, and produces a printed report of the process.

Utility CTMAESIM can operate in either JCL Library mode or Scheduling Library mode:

• In JCL Library mode, the utility checks the AutoEdit statements in the JCL of the job, but not in the job scheduling definition.

  This mode becomes operational when you specify a JCL member in the utility panel; in this case, the table that contains the job scheduling definition is unknown to the utility, and the job scheduling definition therefore remains unchecked.

• In Scheduling Library mode, the utility not only checks the AutoEdit statements in the JCL of the job, it also checks the impact that SET VAR statements in the job scheduling definition have on the JCL.

  This mode becomes operational when you specify a job scheduling definition in the utility panel. Because the job scheduling definition points to the JCL member, both the job scheduling definition and the JCL can be, and are, checked.