TOM user interfaces
Total Object Manager (TOM) offers various user interfaces. Each interface has its advantages, and the decision on which interface to use depends on your preferences.
You can use the following interfaces with TOM:
- 3270
- MainView Explorer
- BMC AMI Ops User Interface 2.0
- TOMEXEC API
- Operator console
Here are some factors that you should consider before choosing an interface.
3270 interface
Consider the following factors:
- The 3270 interface is best suited to the TDEPORDx views, which display object and set relationships illustrated with dependency trees. The TDEPORDA (all objects and sets) and TDEPORDR (objects) tabular views display parent and child relationships by indenting the object and set names according to descendance. These views request queries with model inheritance and resolved variables.
- The Curr Sys Status field on the TDEPORDx views provides hyperlinks that display the reason for the status of the object or set. You can use these hyperlinks to analyze the reason for the status of objects and sets.
- You can use standard BMC AMI Ops features such as SSI, windows, split screen, and filtering.
MainView Explorer interface
Consider the following factors:
The MainView Explorer interface is best suited to the TDEPCHA and TDEPCHR views, which display object and set relationships illustrated with dependency trees. The TDEPCHA and TDEPCHR views display object and set relationships in the form of a chart containing rectangular boxes and lines connecting them. Hovering over a box displays the status of objects and sets. You can also use all available actions by right-clicking a box. In addition, you can use the TDEPCHA and TDEPCHR views to adjust the chart by scaling, zooming, filtering, and isolating sub-trees.
- When using the MainView Explorer interface, you can use standard MainView Explorer features (as with any other BMC AMI Ops product).
BMC AMI Ops User Interface (BMC AMI Ops UI) 2.0
BMC AMI Ops UI is a web-based user interface component that is hosted on IBM z/OS. BMC AMI Ops UI provides access to the same TOM views and information as the 3270 interface.
TOMEXEC API
Consider the following factors:
- If you need custom automation beyond what TOM provides, use the TOMEXEC API.
When you use the TOMEXEC API, operator-type requests (such as STOP, START, and RESET) wait for completion before returning control to the EXEC.
- In the TOMEXEC API, you can adjust the timeout value for operator requests. If it takes too long to complete, control returns to the EXEC and the REXX variable TOMRC is set to value 148. Although TOM continues to process the request, the EXEC cannot determine the results. The timeout default is 30 seconds, but you can adjust this value by using the configuration parameter TOMEXEC_MAX_WAIT in member MAMINIxx.
- The MAMEXPRT, MAMIVP, MAMSTAT, and TOMREPRT utilities use the TOMEXEC API. For examples of how to use the TOMEXEC API and these utilities, see the following topics:
Operator console
Consider the following factors:
- When the BMC AMI Ops Infrastructure Coordinating Address Space (CAS) is not available, use the operator console during an IPL or SHUTSYS,
- Operators who are not trained to use other TOM interfaces can use the operator console.
- When you use the operator console, operator requests don't wait for completion.
- If the CAS is not available, you can use the MAMSTAT utility to view object information such as that found on the TOBJOR view.
- You can use the OBJECT SHOW command to view the status of objects.
You can use the OBJECT SHOW command with the REL=Children|Parents parameter to view relationships between objects.