About step constraints

Job Optimizer recognizes various splitting constraints.

Job Optimizer does not split a step if any of the following constraints exist:

  • Data set usage

    • The step uses a dynamically allocated data set that has no history. You can override this constraint with JTL.

    • The step uses a data set that is dynamically allocated and allocated in JCL and one of the data set dispositions is not set to SHR (share). You can override this constraint with JTL.

    • The step uses a VIO data set, and DISP=(,DELETE) is not specified for the VIO DD statement. You can override this constraint with JTL.

    • The step uses a temporary SMS data set with DISP=MOD.

    • The step uses a tape.

  • Conditional processing

    • The step is associated with a job that has the COND (conditional) parameter specified. You can override this constraint when defining job policies or with JTL.

    • The step has a step-level condition code and the named step has not been completed. If conditional execution does not name a step, all previous steps must be complete before the step is split. You can override this constraint when defining job policies, by using JTL, or by updating the History data set.

    • The step contains IF-THEN-ELSE JCL statements and the named step has not been completed. If conditional execution does not name a step, all previous steps must be complete before the step is split. You can override this constraint when defining job policies, by using JTL, or by updating the History data set.

  • Referback usage

    • A PGM=*. nnnnnn referback exists on the EXEC statement.

    • The step uses referback logic that Job Optimizer cannot resolve.

  • Additional constraints

    • The step uses an internal reader.

    • The step has unresolved GDG references.

    • The step has too many DD statements; the maximum size of the internal text file could be exceeded.

    • The step was never completed normally. You can override this constraint with JTL or by updating the History data set.

    • A specified JTL statement prevents the step from splitting.

    • A specified UCF-member keyword prevents the step from splitting.

    • The step was restarted from a checkpoint.

    • The step is associated with an unresolved forward reference.

    • A requested target system is not available.

    • The step accesses the IBM DB2 program.

    • The step accesses the IBM IMS environment.

    • The step contains a data set that Job Optimizer Pipes will convert to a pipe and write to the physical data set.

Job Optimizer issues step summary messages (if step summary messages have been requested) that indicate the reasons that steps were not split.

Was this page helpful? Yes No Submitting... Thank you

Comments