AutoEdit Usage in the Job Scheduling Definition

Certain AutoEdit components can be used in job scheduling definitions. In job scheduling definitions, AutoEdit components in certain statements (SET VAR and DO SET) directly affect JCL. In other statements (SYSOUT and DO SYSOUT, SHOUT and DO SHOUT, MEMLIB and OVERLIB) they do not affect the JCL.

WARNING: When using AutoEdit variables in job scheduling definitions, always test the definitions for proper AutoEdit syntax with the AutoEdit simulation utility. For more information, see Testing AutoEdit Syntax.

In the job scheduling definition, AutoEdit components can be specified in the following parameters:

• SET VAR and DO SET statements

  These two job scheduling definition statements and the %%SET control statements are used to assign values to user-defined variables in the JCL and in Control-M job definition post-processing parameters (for example, in the SHOUT message text).

  Example

  In this example, AutoEdit statements in the job scheduling definition and the JCL allocate space for the job. If the job abends due to insufficient space, the AutoEdit statements adjust the allocated space and rerun or restart the job.

  The following step in the job’s JCL sets the quantity of available space to five units of whatever type (track or cylinder) is specified in the job scheduling definition.

The job scheduling definition contains the following SET VAR statement that sets the space type to "track":

In this case, the second line in the above DD statement resolves to:

The job scheduling definition also contains the following statements that are activated if the job abends due of lack of space (code S*37). These statements change the space type to "cylinder", which provides enough space, and rerun the job. If Control-M/Restart is active, the job is restarted from the abended step.

If the job abends as above, the second line of the earlier JCL DD statement resolves to:

when the job is submitted for rerun (or restart).

• SYSOUT and DO SYSOUT

  File names for SYSOUT and DO SYSOUT handling can be specified using AutoEdit variables whenever SYSOUT option F (copy to file or sysout archiving) is specified. For example:

• SHOUT, DO SHOUT, and DO MAIL

  System AutoEdit variables and variables defined in the Control-M SET VAR or DO SET job definition parameters can be used in shouted messages. For example:

• MEMLIB and OVERLIB

  System AutoEdit variables and variables defined in SET VAR parameters can be used in the MEMLIB and OVERLIB fields to specify the appropriate library. Examples of this usage are shown on the following pages.

• IN, OUT, and DO COND

  You can use an AutoEdit variable in a condition name, provided that the AutoEdit variable has a value that is known before the job is ordered (for example, a system auto-edit variable). That same value will be used in the condition name regardless of whether the condition name is used in a run-time parameter (IN parameter) or in a post-processing parameter (OUT or DO COND parameters) to ensure that the relationship between the IN and OUT condition names are synchronized.

  Note, that as far as AutoEdit variables in condition name parameters are concerned, the values of SET VAR or DO SET parameters in the job definition are not resolved. Likewise, AutoEdit variables defined in a SMART table entity are not resolved in any of the SMART table job definition condition names.