The sixth table, IVP5, illustrates and verifies "maybe" job handling and manual conditions.

The SMART Table Entity is created with the ADJUST CONDITIONS parameter set to Y.

The DUMMY1 job is not ordered, so its OUT condition, MANUAL-IN-COND, is not present in the Active Jobs file.

The MANUAL-IN-COND is a prerequisite IN condition required for the following job, DUMMY2. However, because of the setting of the ADJUST CONDITIONS parameter in the SMART Table definition, DUMMY2 does not wait for that condition to become available.

As a result, the CTMBLT job sysout contains the following message:

JOB554I INPUT CONDITION REMOVED: CONDITION=MANUAL-IN-COND ODAT , MEMBER=DUMMY2 , GROUP IVPMCND

The DUMMY3 job has an IN condition named REAL-MANUAL-IN-COND. This really is a manual condition, because it does not exist as an OUT condition of any job. As a result, this condition is not removed, and the job remains in WAIT SCHEDULE status.

The following job executes the IOALDNRS utility and creates the Manual Conditions file. Use Screen 7 to view this file, and verify that the REAL-MANUAL-IN-COND condition is present there.

Because the DUMMY3 job remains in WAIT SCHEDULE status, the IVP5 table cannot end OK. Instead, it remains ACTIVE. However, the following table, IVP6, is dependent on the IVP5 table ending OK.

To enable the IVP to continue, you must do the following:

1. Enter the Active Environment screen (Screen 3).
2. Locate the DUMMY3 job.
3. Use the ? command to enter the SCHEDULING ANALYSIS screen (Screen 3.?).
4. Manually add the missing condition (REAL-MANUAL-IN-COND).