Forces jobs under Control-M.
Figure 154 DO FORCEJOB Parameter Format
Optional. Type FORCEJOB in the DO field and press Enter. The subparameters shown in Table 130 are displayed:
Table 130 DOFORCEJOB Subparameters
Subparameter |
Description |
---|---|
TABLE |
Name of Control-M scheduling table. Mandatory. |
JOB |
Job name. If this field is blank, all jobs in the specified table are forced. Optional. |
UFLOW |
Whether to force a unique job flow for the jobs in a table. Relevant only when the JOB name is left blank. A unique flow is not affected 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. Valid values are:
|
DATE |
Scheduling date for the jobs. Valid values are:
|
LIBRARY |
Name of the Control-M scheduling library containing the specified table. Mandatory. |
The following Auto-Edit system variables are available to newly forced jobs and can be used in the Control-M job scheduling definition or JCL:
Table 130a AutoEdit System Variables
Variable |
Description |
---|---|
%%$DSN |
Name of the data set handled by the rule. Valid only for rules containing an ON DSNEVENT statement. |
%%$DSNDISP |
Disposition of the data set handled by the rule. Valid only for rules containing an ON DSNEVENT statement. Possible values are:
|
%%$JNAME |
Triggering job name. Valid in rules for all types of events. |
%%$SABEND |
System abend code of the step whose termination triggered the rule. |
%%$STEPCC |
Completion code of the step whose termination triggered the rule. |
%%$UABEND |
User abend code of the step whose termination triggered the rule. |
Parent Topic |