Limited supportBMC provides limited support for this version of the product. As a result, BMC no longer accepts comments in this space. If you encounter problems with the product version or the space, contact BMC Support.BMC recommends upgrading to the latest version of the product. To see documentation for that version, see BMC AMI Ops Infrastructure 7.1 .

Allocating Total Object Manager data sets

Use the following procedure to allocate the data sets that are required by 

Total Object Manager

 (

TOM

).

Tip

This task is optional for BMC AMI Ops Automation and does not apply to other products.

This procedure uses member TOMALLOC to allocate a TOM registry data set and two log data sets for TOM.

To allocate the TOM data sets

  1. Copy BBSAMP member TOMALLOC to your UBBSAMP data set.
  2. Make the following changes to TOMALLOC:
    1. Add a valid JOB card for your site.
    2. Change all occurrences of #prefix# to the high-level qualifier for the TOM data sets.
    3. Change all occurrences of #ssid# to the subsystem ID of the BBI-SS PAS with which this instance of TOM will be associated.
    4. Change all occurrences of #volume# to the DASD volume where you want to store the TOM data sets.

  3. Save the member and submit the job.

    Note

    TOM will issue a WTOR message whenever it encounters an uninitialized registry or log data set. This process ensures that the TOMALLOC JCL specifies the correct data set name. After you reply to the WTOR, TOM formats the data set and continues its initialization.

Related topic

Manual-customization


 

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