Creating Logger BBPARM member LOGGERxx


This topic describes how to create BBPARM member LOGGERxx for the Logger agent.

Important

You must create this member for all BMC AMI Ops products and for each Logger logspace.

Before you begin

You use the BBSAMP member NGLOGGER to create initialization parameters for the primary logspace. Consider the following points:

  • By default, the Logger reads LOGGERxx member from the BBPARM data set, which is specified with the PARMDSN parameter in the BBPARM MVINGIxx member. However, if the SYSP=(xx[,yy,zz...]) parameter in  the BBPARM MVINGIxx member specifies more than one suffix, Logger can read multiple LOGGERxx members.
  • Logger performs syntax checking, starting with the group of parameters that follows MVSSYSTEM=sysname. Syntax checking stops with the next MVSSYSTEM parameter or the end of the member.
  • The LOGGERxx member supports the of system variable substitution.

To create a BBPARM LOGGERxx member

  1. Copy the BBSAMP NGLOGGER member to your UBBPARM data set.This is the data set that you have specified with the PARMDSN parameter in BBPARM MVINGIxx member. 
  2. The LOGGERxx member contains the following parameters:

    Parameter

    Description

    MVSSYSTEM=sysName

    Specifies the  name of the system to which the parameters in this member apply

    This name must match the current system name in CVTSNAME.                                                                                                           

    If you specify the system variable &SYSNAME,  you can use a single set of parameter statements to start Logger on multiple system images.

    LOGPREFIX=dsnPrefix

    Specifies the data set prefix for the allocated log data sets

    ARCHIVE=YES | NO

    Enables or disables the archiving of NGL logs for this LOGGERxx member.

    Default value: YES

    MVINGIxx is the global declaration if you don't specify it in any LOGGERxx members coded in SYSP= parm.
    If you specify ARCHIVE=YES/NO in the LOGGERxx member, it will override what is specified in the MVINGIxx member.

    You can check message BBMZL496I or BBMZL497I in the DBC joblog to make sure it reflects the value you expect:

    BBMZL496I  MVL/NGL Archive set to YES by default
    BBMZL497I  MVL/NGL Archive set to YES/NO

 

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