Manually shutting down remaining objects in the set

When TOM reports that set shutdown processing is cancelled, this indicates that some objects could not be stopped.

Failure to stop an object can occur for the following reasons:

An object within the set has a dependency on another object that is not in the set.
An object with a dependency on this set has not been shut down.
An object within the set is in SUSPEND mode.
Errors were encountered during the shutdown process, such as one of the following conditions:
- A Verify Stop condition was defined for an object, and a write-to-operator (WTOR) message was issued, but nobody replied to it.
- A nonzero return code was returned from a pre-stop command that is associated with an object.
- An invalid shutdown validation message, command, or ALERT ID was specified in the object’s definition.
- Invalid or unresolvable variables were specified in the STOP command.
- The STOP command timeout value was exceeded.
- An object’s dependents were not stopped.

To find exceptions to the shutdown process

On the TOBJO view, scroll right (PF11) until you find the Excptn column.
Look for objects that display YES in the Excptn column.If shutdown processing was cancelled for some reason, you will see YES in the Excptn column.
After identifying and correcting the exception, enter RES (reset) in the CMD field next to each object to take the object out of Exception mode (use the RUNSTAT option of the RESET command).
Enter P or STO in the CMD field next to each object to manually stop the object.