Previous Topic

Next Topic

Book Contents

Book Index
Ordering Scheduling Jobs

Although job scheduling in the production environment is generally handled by Control-M automatically (for more information, see Selected Implementation Issues), Control-M provides several mechanisms for scheduling jobs manually. Among these are options to manually request job scheduling from the Table List screen and the Job List screen.

Either of two options, O (Order) and F (Force), can be used in either of these screens to manually request job scheduling. These options work as follows:

Table 45 Options for Manually Ordering Jobs

Option

Description

O (ORDER)

Basic scheduling parameters of the jobs are checked against the requested scheduling date. If the job must be scheduled for that day, a job order is placed on the Active Jobs file.

F (FORCE)

Basic scheduling parameters of the jobs are not checked. A job order is placed on the Active Jobs file that day even if the scheduling criteria of the job are not satisfied.

Note: With one exception, options O (Order) and F (Force) can be used for tables in both the Job List screen and Table List screen.

The exception is: Option O (Order) cannot be entered for individual jobs in SMART Tables.

When you use the O and F options, a confirmation window is displayed. The default confirmation window in the case where the O option has been entered for tables in the Table List screen is illustrated in Figure 28.

Figure 28 Order and Force Confirmation Window (Tables)

LIST OF TABLES IN CTM.PROD.SCHEDULE                             TABLE: BACKUP

COMMAND ===>                                                    SCROLL===> CRSR

OPT  NAME ---------------------------------------------------------------------

      STARTBKP       +--------------------------------------------------------+

  O   BACKPL01  <----| CONFIRM   ODATE 090512 WAIT FOR ODATE N HOLD N UFLOW N |

      BACKPL02       +--------------------------------------------------------+

      BACKPLW1

      BACKPLW2   WEEKLY BACKUP OF FILES FROM APPL-L #2                        

      BACKPLW3   WEEKLY BACKUP OF FILES FROM APPL-L #3                        

      BACKPLW4   WEEKLY BACKUP OF FILES AFTER DAILY FROM APPL-L +             

      DASDRPT1   DASD REPORTS AFTER BACKUPS FOR APPL-L                        

      DASDRPT2   DASD STATISTICS REPORT AFTER BACKUP FOR APPL-L               

      ENDPLBKP   END OF BACKUP INDICATION FOR APPL-L                          

      BACKAC01   DAILY BACKUP OF DATA SETS FrROM APPL-ACCOUNT                  

  O   BACKAC02   DAILY BACKUP OF SPECIAL FILES FROM APPL-ACCOUNT              

      BACKACW1   WEEKLY BACKUP OF FILES FROM APPL-ACCOUNT #1                  

      BACKACW2   WEEKLY BACKUP OF FILES FROM APPL-ACCOUNT #2                  

      BACKACW3   WEEKLY BACKUP OF FILES FROM APPL-ACCOUNT #3                  

      BACKACW4   WEEKLY BACKUP OF FILES AFTER DAILY FROM APPL-ACC +          

      DASDRPT3   DASD REPORTS AFTER BACKUPS FOR APPL-ACCOUNT                  

      DASDRPT4   DASD REPORTS AFTER BACKUP FOR APPL-ACCOUNT                  

  O   ENDACBKP   END OF BACKUP INDICATION FOR APPL-ACCOUNT                    

      BACKDD01   DAILY BACKUP OF DATA SETS FROM APPL-DD                       

OPTIONS S SELECT  O ORDER  F FORCE  G GRAPHIC FLOW  B BROWSE  D DELETE 10.23.58

If the O or the F option is entered for jobs in the Job List screen, a window similar to that in Figure 29 appears.

Figure 29 Order and Force Confirmation Window (Jobs)

JOB LIST     LIB: CTM.PROD.SCHEDULE                             TABLE: BACKUP

COMMAND ===>                                                    SCROLL===> CRSR

OPT  NAME ---------------------- DESCRIPTION ----------------------------------

      STARTBKP        +-------------------------------------------------+     

      BACKPL01  <-----+  CONFIRM   ODATE 150818 WAIT FOR ODATE N HOLD N |     

  0   BACKPL02        |  SETVAR N                                       |     

      BACKPLW1        | ----------------------------------------------- |     

      BACKPLW2   WEEKL|  DYNAMIC SMART TABLE INSERT S DUPLICATE  Y      |     

      BACKPLW3   WEEKL|  (S - SELECT, R - RECENT, N - NEW, A - ALONE)   |     

      BACKPLW4   WEEKL+-------------------------------------------------+     

      DASDRPT1   DASD REPORTS AFTER BACKUPS FOR APPL-L                        

      DASDRPT2   DASD STATISTICS REPORT AFTER BACKUP FOR APPL-L               

      ENDPLBKP   END OF BACKUP INDICATION FOR APPL-L                          

      BACKAC01   DAILY BACKUP OF DATA SETS FROM APPL-ACCOUNT                  

  O   BACKAC02   DAILY BACKUP OF SPECIAL FILES FROM APPL-ACCOUNT              

      BACKACW1   WEEKLY BACKUP OF FILES FROM APPL-ACCOUNT #1                  

      BACKACW2   WEEKLY BACKUP OF FILES FROM APPL-ACCOUNT #2                  

      BACKACW3   WEEKLY BACKUP OF FILES FROM APPL-ACCOUNT #3                  

      BACKACW4   WEEKLY BACKUP OF FILES AFTER DAILY FROM APPL-ACC +           

      DASDRPT3   DASD REPORTS AFTER BACKUPS FOR APPL-ACCOUNT                  

      DASDRPT4   DASD REPORTS AFTER BACKUP FOR APPL-ACCOUNT                  

  O   ENDACBKP   END OF BACKUP INDICATION FOR APPL-ACCOUNT                    

      BACKDD01   DAILY BACKUP OF DATA SETS FROM APPL-DD                       

OPTIONS S SEL D DEL I INS O ORDER F FORCE J JCL C COPY P PLN T JOBSTAT 15.37.39

The default confirmation window contains the following fields:

Table 46 Order and Force Confirmation Window Fields

Field

Description

CONFIRM

Whether to process the Order or Force request.

Valid values are:

  • Y (Yes) – Process the Order or Force request.
  • N (No) – Cancel the request.

ODATE

Scheduling date of the job or table, in mmddyy, ddmmyy or yymmdd format, depending on the site standard. The specified date can be modified.

The default setting of the ODATE is determined by the setting of the PSCHDTYP profile variable. For further information, see the discussion of profile variables in the INCONTROL for z/OS Administrator Guide.

Note: The job is only ordered if the basic job scheduling criteria are satisfied at the ODATE. However, the job is not necessarily executed on the ODATE. If the job is ordered, it becomes eligible for execution immediately when its run-time criteria have been satisfied.

ODATE has the following additional functions:

  • If an IN or OUT condition uses a relative dateref (for example if the value of dateref is ODAT, PREV, or NEXT), ODATE is used to set the dateref. For more information on IN and OUT conditions, see IN: Runtime Scheduling Parameter and OUT: Post–Processing Parameter.
  • The calculation of the MAXWAIT of a job is based on the ODATE of the job, and not on the actual date on which the job is ordered. For more information on the MAXWAIT parameter, see MAXWAIT: Basic Scheduling Parameter.
  • It is used by the WAIT FOR ODATE option (as described in this table).

For more information on the meaning of ODATE, see the discussion of Time Zone support in the Control-M chapter of the INCONTROL for z/OS Administrator Guide.

WAIT FOR ODATE

Whether to wait for a specific date, or process the Order or Force request immediately.

Valid values are:

  • Y (Yes) – The Order or Force request is not executed before the date set in the ODATE field, even if all required conditions and resources are available.
  • N (No) – The Order or Force request is processed immediately. Default.

HOLD

Whether or not jobs should be held immediately after being ordered.

Valid values are:

  • Y – Jobs will be held immediately after being ordered.
  • N – Jobs will not be held. Default.

UFLOW

Enables you to Order or Force a unique job flow for the table.

Valid values are:

  • Y – Flow will be unique.
  • N – Flow will not be unique. Default.

The unique flow feature is used to ensure that the new flow, which is being ordered, will not be effected by conditions that might already exist as relationships between jobs in the AJF. This is accomplished by automatically adding unique suffixes (up to 3 characters long) to the new condition names.

A typical use case for the unique flow feature is where the same table is ordered multiple times a day, and there is a need for an independent job flow for each invocation.

When you apply a unique job flow, names of long conditions must not exceed 36 characters (due to the 3-character suffix).

SETVAR

Enables you to review and manage the AutoEdit variables used in the job's SETVAR statements for the current order.

When set to Y (yes), this field opens the Job Variables List window, where you can review the job's AutoEdit variables and their assigned values, dynamically assign new values to variables, and insert additional variables in an ad-hoc manner. For more information, see Reviewing and managing job variables.

Valid values are:

  • Y – Review and manage variables before proceeding with the order.
  • N – Proceed with the job order. Default.

DYNAMIC SMART TABLE INSERT

Enables you to insert a job into a SMART Table. Valid values are:

  • A - Order or Force the job. Default.
  • S - Opens a window with a list of SMART Tables. For more information, refer to Selecting Dynamic Jobs.
  • R - Adds the job to the SMART Table Entity (where the job is listed) that was most recently ordered into the AJF. The insertion of the SMART Table Entity to the AJF is done as FORCE.
  • N - Force a job, and its SMART Table, to the AJF.

Notes:

  • If an attempt is made to use option "R" (recent) to add a job to a deleted SMART Table, error message JOB53BE is displayed. Also, if an attempt is made to use option "R" (recent) to add multiple jobs (ASK FOR EACH ONE=N), only the first job is ordered.
  • If the "T" (SMART Table) option is entered for the SMART Table, the added job is displayed after the SMART Table Entity and not at the end of the list.

DUPLICATE

Determines whether you can dynamically insert duplicate jobs (meaning, jobs that already exist in the SMART Table Entity of the AJF). Valid values are:

  • Y - A duplicate job can be inserted. Default
  • N - A duplicate job can not be inserted. Attempting to insert a duplicate job results in the display of an error message

This parameter is only valid if the Dynamic Insert Job into SMART Table parameter is set to S or R.

ASK FOR EACH ONE

This line is displayed only if more than one order or force option is requested. It determines whether individual confirmation is required for each order or force request.

Valid values are:

  • Y (Yes) – Individual confirmation is required for each order or force request. The specified CONFIRM value (Y or N) applies only to the current order or force request.
  • N (No) – Individual confirmation is not required for each order or force request. The specified CONFIRM operation is applied to all order or force requests. If CONFIRM is Y, all order or force requests are processed; if CONFIRM is N, no order or force requests are processed.

Fill in the confirmation window and press Enter. If at least one order or force request has been specified for a table or job, the original list screen disappears and a message screen is displayed. This screen displays messages that contain the following information about the jobs that were scheduled.

JOB name ODATE date ID=ordered PLACED ON ACTIVE JOBS FILE-descr

Each iteration of the message screen displays job information for one table only. Press END (PF03/PF15) to exit the message display for that table. If multiple tables, or jobs in multiple tables, have been scheduled, the messages for the next table are displayed. When messages for all tables have been displayed, pressing END displays the Table or Job list screen.

Parent Topic

Scheduling Definition Facility