As previously discussed, the occasional job scheduling request can be made using the Order or Force option in the Scheduling Definition facility. At some sites, however, access to Scheduling Definition facility may be restricted for security reasons, for example, to prevent the changing or deletion of job scheduling definitions.
As an alternative to ordering or forcing a job in the Scheduling Definition facility, you can order or force a job using Online Utility M1.
---------------------------- JOB REQUEST UTILITY ----------------------------
COMMAND ===>
SCHEDULING LIBRARY ===> CTM.TEST.SCHEDULE
TABLE NAME ===>
JOB NAME ===> (* for all jobs)
SCHEDULED RUN DATE ===> 02 02 01 (ODATE - format MM DD YY)
FORCED SCHEDULING ===> NO (YES,NO)
ENTER YES TO CONTINUE ===>
GROUP ===> (Optional)
CALENDAR LIBRARY ===> IOA.TEST.CAL
In this panel you can
To request all jobs in a table, specify an asterisk in the job name field.
The basic scheduling criteria of the jobs are checked against this date to see if the job should be ordered as requested.
This tells Control-M where to look if a calendar name is specified in the job scheduling definition. Calendars are discussed in Additional Features.
Note: The GROUP field is generally useful in tables whose jobs do not inherit the GROUP from the table, and only if an * is specified in the JOB NAME field. It limits the jobs ordered to those belonging to the specified group.
In general, it is probably quicker to use batch utility CTMJOB, especially if you are ordering several jobs. Perhaps the only advantage of online utility CTMJOBRQ is that you do not need to know the format of the order statements—you merely fill in the parameter fields presented in the panel. But CTMJOBRQ is definitely not a powerful utility.
Parent Topic |