Job scheduling definitions

A job scheduling definition specifies criteria that identify decisions to be made, and actions to be taken, regarding the handling of a particular job. Each job scheduling definition contains the following sections:

• General Parameters

  General information about the job (for example, identify the library and member in which the JCL is stored).

• Basic Scheduling Parameters

  Criteria according to which Control-M schedules the job.

• Runtime Scheduling Parameters

  Runtime requirements that must be satisfied before Control-M submits the job.

• Post-processing Parameters

  Actions Control-M performs after the job ends, depending upon the outcome of job execution. For example, Control-M performs one set of actions if the job ends OK, but another set of actions if an abend occurs.

Users of Control-M/Assist are required to define Job Scheduling definitions for jobs or groups of jobs to be managed by Control-M/Assist. When defining jobs definitions in Control-M/Assist environment, consider the following:

• Job definition Basic scheduling parameters and the Runtime Scheduling sections are irrelevant to Control-M/Assist users since the jobs are scheduled externally to Control-M.
• The post-processing section is the most relevant section and specifies the Control-M post-processing logic to be executed after the job enters the Control-M/Assist environment.

The mechanisms used to define job scheduling definitions are discussed in the online facilities chapter of the Control-M for z/OS User Guide.

Once defined, a job scheduling definition is saved. It can be modified later if required. Job scheduling definitions are stored in members in partitioned datasets (libraries), as follows:

• Job scheduling definitions for related applications are generally placed in a single member, called a table.
• Multiple tables are stored in partitioned datasets, called scheduling libraries.
• Multiple scheduling libraries can be defined.