Recommended TOM utilities

Total Object Manager (TOM) provides utilities that make implementation, administration, and maintenance tasks easier.

Registry export utility (MAMEXPRT)

The MAMEXPRT EXEC in BBSAMP uses the TOMEXEC API for exporting Definition Bases in the form of an import EXEC, which also uses the TOMEXEC API. You can modify and run the output (import) REXX EXEC to add items to a new or existing Definition Base. MAMEXPRT is useful for change management, Registry backup, deploying layer-generated objects and sets to their target TOMPLEXs, and reporting problems to BMC Support. You can also use the MAMEXPRT utility to quickly and easily make mass changes to a Definition Base by creating an import EXEC, editing it, and then running it to create a new Definition Base with the required changes. For more information, see Registry-export-utility.

Related topics

Setting up a playpen

Logger

Discovering-and-creating-TOM-objects

Log reporting utility (MAMLXRPT)

The BBSAMP member MAMLXRPT runs as a batch job to extract messages from the Logger. MAMLXRPT has many message and record selection capabilities that you can use to save, extract, report, and archive audit-type messages. You can also use it to extract messages regarding the time of an incident, and to gather documentation when requesting assistance from BMC Support.

When using MAMLXPRT, you can make the report easier to read by specifying the following statements in the SYSIN DD:

  1. Specify FROM(LSPACE=logspaceid) to indicate the logger from which records should be extracted, or omit it to use the default logger.
  2. Specify SELECT(RECTIME,MSG) to select only the time and message text fields of the records that you want to report.
  3. Specify WHERE(DIRECTION=Forward,TimeRange=(hh:mm:ss.000/yymmdd-hh:mm:ss.000/yymmdd) to print the records in chronological order and to indicate the time range of the records to report. 

For more information, see Logger.

Best partice
If you have system auditing requirements, we recommend that you specify the MAMINIxx AUDIT=YES parameter and use the MAMAUDTD and MAMAUDTR utilities to print auditing messages from the Logger. These utilities print messages related to changes made to your system. For more information, see Producing audit reports.

Infrastructure Discovery

You can use the Infrastructure Discovery component to add objects for STCs and USS processes that are discovered (running) on the system in which the TOM PAS is running. On the discovered items (TDSCOBJS) view, use the ADD action on the row of an STC or USS process to open a dialog box in which you can select choices for naming the object and create a demonstration (AATWAIT) or an actual managed object. For more information, see Discovering-and-creating-TOM-objects.

You can use Infrastructure Discovery to create a Definition Base of dummy objects for the TOM playpen. You can then populate the actual Definition Base of objects for a new implementation of TOM. For more information, see Setting up a playpen.

You can also use Infrastructure Discovery to create layer objects and to determine if there are running items (STC and USS processes) that TOM does not manage. 

Installation Verification Program

After installing or upgrading TOM, it is important to use the Installation Verification Program (IVP) to make sure that all the necessary components, including the BMC AMI Ops Infrastructure component, are working correctly. IVP (MAMIVP EXEC) writes a report of the results to either the BMC AMI Ops Automation Journal, the system console, or both. You can also create BMC AMI OpsA ALERTs for any problems or errors that IVP finds in the installation. For more information, see Verify-installation-with-Installation-Verification-Procedure-IVP.

IVP uses the TOMEXEC API and BMC AMI Ops Automation IMFEXEC requests to create a new Definition Base and performs the following actions:

  1. Creates sample "demonstration" STM objects (by using TOMSCMOB cataloged procedure and AATWAIT program)
  2. Creates a set containing all the objects
  3. Activates the new Definition Base and waits for all the objects to have an ACTIVE status

  4. SHUTSETs the set of all objects

    Important

    SHUTSET is used instead of SHUTSYS to allow reactivation of the previously active Definition Base.

  5. Waits for all objects to have a LOCKED status and activates the previously active Definition Base

  6. Deletes the Definition Base of sample objects

    Important

    You can specify KEEPBASE=YES when the IVP is started to save the new Definition Base of sample objects for practice and experimentation by operators and administrators without affecting actual system resources.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*