Previous Topic

Next Topic

Book Contents

Book Index

Scheduling Library Mode Parameters

Table 138 Scheduling Library Mode Parameters

Parameter

Description

SCHEDULING LIBRARY

Name of the library containing the job scheduling definition.

TABLE NAME

Name of the table containing the job scheduling definition.

JOB NAME

Name of the job scheduling definition.

Note: When specifying scheduling library mode parameters, values for owner, application name, and the JCL library and member of the job are not specified because the utility takes these values directly from the specified job scheduling definition. The name of the JCL member is obtained from the OVERLIB parameter (if specified) instead of the MEMLIB member.

Table 139 AutoEdit Simulation

Parameter

Description

CONTROL-M GLOBAL LIBRARY

Name of the library that contains the members referenced by AutoEdit statement %%GLOBAL.

WDATE

Working date of the job.

ODATE

Original scheduling date of the job.

FUNCTION

Function to be performed by the simulation. Valid values are:

  • LIST – The utility simulates submission of the member from the designated library using the specified date and user ID parameters. Control-M checks the JCL. The output is displayed on the terminal. The JCL is not actually submitted.
  • SUBMIT – Control-M attempts to resolve the AutoEdit statements. If successful, the JCL member lines are also written to the file referenced by the DASUBMIT DD statement and the member is submitted by the utility for execution. In this case, MVS also checks the JCL. This option can also be used to submit jobs when the Control-M monitor is not active (for example, if there is a severe technical problem).
  • SUBSCAN – This function is similar to SUBMIT except that it adds a TYPRUN=SCAN parameter to the job card before performing simulation. As a result, the job is submitted and the JCL is checked by MVS but the job is not executed.

 

Note: When executing the AutoEdit simulation SUBSCAN function, any JES statements that can cause the console subsystem to be triggered are removed from the job's runstream. Examples of such JES2 statements are:

/*MESSAGE

/*NETACCT

/*NOTIFY

/*OUTPUT

/*PRIORITY

/*ROUTE

/*SIGNxxx

/*SETUP

/*XMIT

JES3 statements that have similar effects are also removed.

Utilize this function also if a JCL-checking product (other than JOB/SCAN or PRO/JCL) is in use at the site. The utility creates a copy of the JCL member with all Control-M AutoEdit variables resolved. The JCL-checking product can then be invoked against this copy.

  • JOBSCAN – This option is available at sites where the JOB/SCAN or PRO/JCL product is installed, but only if the utility is activated from the Online Utilities menu. (This option is not displayed and cannot be used if the utility is activated by a CLIST or batch procedure.) This function is similar to SUBMIT except that if Control-M finds no JCL errors, JCL is checked by JOB/SCAN before it is written to the file referenced by the DASUBMIT DD statement.

Enter YES to continue

Confirmation field to help prevent the simulation jobs from being unintentionally run. When blank, the jobs do not run. Enter YES to enable the job run.

To exit the screen without activating the utility, press PF03/PF15.

Parent Topic

M2: Perform an AutoEdit Simulation