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 .

Logspaces

Each instance of the 

Logger

 agent can support multiple logspaces. Each logspace requires its own 

Next Generation Logger

 (

NGL

) logset which also runs as an agent within the 

DBC

. There is a one-to-one relationship between a logspace and its corresponding 

NGL

 logset. In addition:

  • The default logspace is used by BMC AMI Ops Infrastructure logspaces and (optionally) by other products. This default logspace is also called the primary logspace and is usually where WTO messages are written.
  • The product-specific logspaces are used when products have special data requirements or as a way to organize large numbers of log entries. Product-specific logspaces are installed after installing the primary logspace.
  • You cannot dynamically start and stop a logspaces however, you can dynamically start and stop the NGL logset that maps to the logspace with NGL commands. For more information, see Controlling-Logger-operation.

The NGL logset data sets are created when the Logger agent initializes in the DBC. During initialization, the Logger agent reads the specifications in BBPARM member LOGGER xx to define the NGL logsets. For additional information about the DBC and NGL, see Common mainframe infrastructure.

Related topic

Understanding-Logger


 

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