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 .

Defining Next Generation Logger and Logger agents

Use the following procedure to define the Next Generation Logger (NGL) and Logger agents.

Tip

This task is required for all BMC AMI Ops products.

Related topic

Manual-customization

Before you begin

The Logger requires that a BMC Execution Component for z/OS (DBC) address space is running in the LPAR. If a DBC address space is not already running in the LPAR, complete the procedure in section Creating-the-started-task-for-the-DBC-address-space before starting this task.

To define the NGL and Logger agents

  1. Determine the DBC system ID.
    You can determine the DBC system ID by:
    • Viewing the definition in the DBC started task procedure.
    • Viewing the data set and member pointed to by the DDNAME=DBCPARMS statement in the DBC PROC

  2. Enter the DBC system ID in BBPARM member MVINGIxx for the MainView Logger agent and the NGL agent.
    At this point the DBC should be running with the DBC SSID for this LPAR.

  1. Make any modifications by following the instructions in the comments section at the top of XXSAMP members NGLIPROD and NGLSAGNT.

  2. Make any modifications by following the instructions in the comments section at the top of BBSAMP member MVIAGNT.

  3. Review the JCL in MVISAMP (MVIDBCU) and make any modifications by following the instructions in the member.
    The MVIDBCU job defines the Logger and NGL agent product definitions.

  4. Submit the MVIDBCU job.

 

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