This parameter is applied to all jobs in the SMART Table. It provides the options shown in Table 164 when job dependency is defined between jobs in a SMART Table by their respective conditions.
Such a job dependency arises when one job in a SMART Table is dependent on a condition that is triggered by another job in the SMART Table. If the triggering job is not ordered, meaning, placed on the Active Jobs file, because the scheduling criteria of the triggering job do not match the current Odate, the dependent job cannot run.
The options provided by the ADJUST CONDITIONS parameter enable you to avoid this difficulty.
ADJUST CONDITIONS Set to Yes
If you enter the value Y for the ADJUST CONDITIONS parameter, the following principles apply:
Control-M erases IN conditions from each job in the SMART Table that is placed on the AJF. The following criteria must be met before an IN condition is erased:
The IN condition in the job is triggered by a predecessor job.
The scheduling criteria of the predecessor job are such that the predecessor job will not be ordered during the current day.
The erasing of these IN conditions frees the successor job from its dependency on the predecessor job.
Only the image of the job on the AJF is affected. The original job scheduling definition remains unchanged.
The erased condition does not appear in the Zoom screen.
ADJUST CONDITIONS Set to No
If you enter the value N for the ADJUST CONDITIONS parameter, the following principles apply:
Control-M runs normally.
You must release any jobs that are likely to wait indefinitely on the AJF because they are dependent on predecessor jobs with scheduling criteria such that they will not be ordered. To release the dependent jobs, use one of the manual options, such as those available in
the IOA Conditions/Resources screen (Screen 4)
the IOA Manual Conditions file (Screen 7)
ADJUST CONDITIONS Set to Dummy
If you enter the value D for the ADJUST CONDITIONS parameter, the following principles apply:
Control-M places all the jobs in the SMART Table onto the AJF when the SMART Table is ordered.
Jobs in the SMART Table with scheduling criteria that fit the current ODATE remain unchanged.
Jobs in the SMART Table with scheduling criteria that do not fit the current ODATE, and would not ordinarily be ordered, are placed on the AJF as DUMMY jobs (the MEMLIB parameter is changed to DUMMY). This permits the original logical flow of the SMART Table to be maintained by preserving the relationships of the IN and OUT conditions of these dummy jobs.
Only the image of the job on the AJF is affected. The original job scheduling definition remains unchanged.
ADJUST CONDITIONS Set to Bridge
If you enter the value B for the ADJUST CONDITIONS parameter, the following principles apply:
Control-M bridges over jobs in the SMART Table that have scheduling criteria that do not fit the current ODATE, and would not ordinarily be ordered. This permits the original logical flow of the SMART Table.
If a scheduled job contains an IN condition that should be inherited from an unscheduled predecessor job, this condition is replaced by the IN conditions of the unscheduled predecessor job.
Conditions that are deleted by an unscheduled (bridged over) job are handled as follows:
If the deleted condition is used only once in the SMART Table as an IN condition, the job that inherits the IN condition also inherits the delete action.
If the deleted condition is used by more than one scheduled job in the SMART Table, the delete action is performed by the SMART Table (when the table completes), to avoid premature deletion.
In certain scenarios the SMART Table is ordered without applying a bridge, based on the following principles:
A bridge is not applied to jobs that contain complex IN conditions, such as conditions with OR, Not, or parentheses.
If more than one job adds the same OUT condition, this is considered an implicit OR and the jobs are not bridged. For example, if there are two job flows A and B, which connect to job C with the same OUT condition E1, it is considered an implicit OR, as job C can wait for E1 either from job flow A OR job flow B.
Conditions that were defined using AutoEdit variables are resolved based on the values of the original job before the bridge is applied.
Messages from the Bridge action appear in the job log or SMART Table log.
You can control the level of detail of the messages using the ADJBCMSG parameter in the CTMPARM member in the IOA PARM library.
