DROP – Circumvent occurrence split for ALTER DROPSUCC/PRED

The OPTIONS DROP keyword provides mechanisms that circumvent occurrence inconsistencies.

Two mechanisms are provided:
Method 1
Makes both sides of the broken dependencies a successor to a specified operation number, providing that the operation number is in a status of Complete.
Method 2
Adds an operation using a named workstation and job name, or reuse a matching pre-existing one that has no successors, and makes this a success to both sides of the broken dependency.
The syntax of the OPTIONS DROP keyword is the following:
DROP(<predop>,<succws>,<succjob>,<succtext>)
where:
<predop>
An operation number, such as 001, to be used as a predecessor to both sides of a dropped dependency, but only if <predop> is in a Complete status. It does not add <predop>, if it does not already exist.
<succws>
Name of the workstation used to become a successor to both sides of the dropped dependency. It must be a non-reporting general workstation.
<succjob>
Name of the job used to become a successor to both sides of the dropped dependency. The default is ZRELINK
<succtext>
The operation description used if a successor operation is inserted. The default is Relink dropped deps.