Shutting down a set
If the dependent object or objects are still active, the object is not stopped. Conversely, if an object has no dependents (or those dependents are no longer active) TOM stops the objects within the set. See Creating and managing sets for more information about sets and their uses.
To shut down a set
- On the TSETO view, enter SHU or H in the CMD field next to the name of the set that you want to shut down.
When you issue the H (SHUTSET) line command, any automation that is defined for the objects within the set (pre-stop or post-stop EXECs) is scheduled as part of a set shutdown.
- In the SHUTSET Command Options dialog, select Yes for the Proceed with shutset option.
The following message is written in the message log (MV Logger), indicating that the shutdown process has begun for all objects in the set:
OD7501D Set shutdown for setID commencing
When each object is ready to be stopped, the following messages are written in the message log (MV Logger):
OD2709I Stop initiated for object AAOKMZ23 OD9011I Shutting down AAOKMZ23
The objects are stopped and left in a status of LOCKED. When processing is complete, the following message is written in the message log (MV Logger):
OD9013I All objects for set setID stopped
When all objects in the set have stopped, the set status becomes STOPPED. If objects within the set did not stop properly, the set’s status becomes OTHER. If all of the members of the set have the same failure status (for example, FAILURE-REC-TERM), the set's status will also have that failure status.
If messages OD2709I and OD9011I are not issued for an object in the set, it is likely that the object has a dependent outside of the set that is active. SHUTSET does not issue STOP commands to stop the dependent object. You must manually find and stop the dependent objects. When the dependent object has stopped, TOM stops the appropriate object in the set.