Defining dummy objects by using Infrastructure Discovery

Important

The MainView Explorer host server is required to use the Infrastructure Discovery component.

When you create a playpen, you can define dummy objects in the object Definition Base by using the DEMO action. You to start and stop dummy objects without adversely impacting the system on which the playpen is running.  

Using the information that Infrastructure Discovery finds, you can define dummy versions of the objects that run in the local system. After you have defined all the objects and you have established the appropriate dependency structure, you can simulate the startup and shutdown of the system. Testing allows you to verify whether objects start as expected at IPL and stop as expected during shutdown. You can also set up schedules for starting and stopping objects according to your needs. 

Dummy objects use the AATWAIT program and the TOMSCMOB cataloged procedure, both of which are distributed with the product. Each STC that uses AATWAIT consumes minimal CPU and storage resources. For more information, see Familiarizing-yourself-with-TOM-in-a-simulated-environment.

Related topics

Finding-objects-to-manage-by-using-Infrastructure-Discovery

Familiarizing-yourself-with-TOM-in-a-simulated-environment

Defining-new-objects-by-using-Infrastructure-Discovery

Discovering-and-creating-TOM-objects

To define a dummy object

  1. Navigate to the TDSCOBJS view. 
  2. Issue the DEM line command next to an object to create a dummy version of that object.
  3. Use the Confirm Selected Discovered Objects (DEMO) dialog box to confirm that you have selected the correct object. It displays the S line command next to the object that you have selected to define. To confirm your selection, issue the Next command. If you have selected the wrong object, issue the CANCEL command to cancel the request.
  4. In the Object Creation Options (DEMO) dialog box, enter the following information: 

    1. (Required) In the Object Naming field in the Naming Standards section, type S next to Job Name or InstanceID to select it.

      Best practice
      If you are defining a started task, we recommend that you select Job Name.

    2. (Optional) In the Short Name field in the Naming Standards section, type S next to Job Name or InstanceID to make the variable names unique from object to object. The short name determines if automation variables need to be created in the variable pool of the AMI OpsA PAS associated with the TOM address space. 

      Important

      If you do not need automation variables, leave this field blank. Creating automation variables uses up resources in the system.

    3. Best practice
      We recommend that you leave the field blank to let TOM provide a distribution model for the object if one is available.       (      Optional) Leave the Use TOM distributed models field blank to let TOM provide a distribution model for the object. If you don't want TOM to provide a distribution model, enter a value in the field to define the object yourself. 

    4. (Required) In the Convention field in the Object naming section, type a naming convention for the object. Type ? to view a list of possible naming conventions. Select a line from the list by typing S next to it, and issue the END command to indicate the convention that you want to follow. Be consistent in your choice of naming conventions across the system. For more information, see Naming-conventions-for-objects-and-items.
    5. (Optional) In the Convention field in the Layer Object naming section, type a the name of the layer to define the object as a layer object. Type ? to view a list of possible naming conventions. Select a line from the list by typing S next to it, and issue the END command to indicate the convention that you want to follow. This field is not necessary for a dummy object. For more information, see Naming-conventions-for-objects-and-items.
  5. Issue the Next command to continue to the next step.
  6. (Optional) In the Objects To Create (DEMO) dialog box, issue the B(rowse) line command to browse the definition before writing it into the DEMOBASE definition base. Issue the END command to return to the previous dialog box.
  7.  In the Objects To Create (DEMO) dialog box, issue the END line command to create the dummy object.

After you've created a dummy object, the TOBJ view is displayed. The Active DefBase field displays that there are currently no active definition bases, and the Edit DefBase field displays DEMOBASE. On the TOBJ view, you can issue a line command to browse the complete definition of the dummy object that you created, or make additional edits to the object.

 

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