Setting up a product-specific logspace


Some BMC AMI Ops products require or can use a product-specific logspace.

Tip

This task is optional for all BMC AMI Ops products.

Before you begin

If you are customizing a product that uses a product-specific logspace, perform this task after configuring the default logspace.

Each logspace requires its own BBPARM member LOGGERxx. A started task procedure is required on each system image where product-specific logspaces are used.

To create a BBPARM LOGGERxx member

  1. Copy the BBSAMP member NGLOGGER to your UBBPARM data set.This data set is the one that you will identify on the BBIPARM DD statement in the Logger started task procedure.
  2. Rename member NGLOGGER to LOGGERxx, where xx is a two-character suffix that is unique to this logspace.During initialization, BMC AMI Ops Infrastructure processing reads the LOGGERxx member specified from one of the following locations:
    • The value from the PARMSDSN= parameter in BBPARM member MVINGIxx
    • The value(s) within the <PARM> and </PARMS> tags located in the BBPARM member MVIAGNT

      The LOGS= keyword is located within the <PARM> and </PARMS> tags, which defines a partitioned data set that contains BBPARM member MVINGIxx (and possibly LOGGERxx) members. Be sure to review the settings in BBPARM member MVIAGNT.

  3. Update the parameters in the LOGGERxx member. For more details, see To create a BBPARM LOGGERxx member.

    Important

    You should not change the order of the parameters as they appear in the distributed NGLOGGER member.

 

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