Getting started with Total Object Manager
TOM provides user and programming interfaces that you can use to:
- Define started tasks, USS processes, or Workload Manager Resources (WLM Resources) to TOM as individual objects or grouped together in sets
- Set up calendar dependencies to specify when objects should be stopped or started
- Associate automation commands with an object that can be scheduled before TOM starts an object, after the object starts, before TOM stops the object, and after the object stops
- Define multiple systems on which an object is eligible to be started
- Determine which available systems an object can be started on or moved to
- Determine when an object should be active
TOM also provides:
- An export utility that creates an EXEC containing TOMEXEC API ADD statements.
The resulting EXEC can be edited and scheduled to import definitions to the Registry. - Commands that control objects, sets, systems, and Definition Bases from the z/OS operator console
- BMC AMI Ops Automation views that manage objects and sets of objects from either a 3270 session or MainView Explorer.
- A log that captures TOM activity (including the starting and stopping of objects).
Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*