Define product-specific LOGSET

MainView Transaction Analyzer uses NGL to store and retrieve transaction data that is collected from other BMC AMI Ops products. You must define an NGL LOGSET, which is a group of z/OS linear data sets (or log files), for use by MainView Transaction Analyzer.

Before you begin

Before you begin, perform the following actions:

• Before you can define an NGL LOGSET for MainView Transaction Analyzer, the following components must be installed and configured:
• DBC subsystem, where NGL run
•  NGL

To configure these components, you must use OZI Customization, as described inInstallation System.

• The NGL LOGSET name that you specify here must match the DSLSNAME parameter that you specify in member MTAPRMxx.
• To estimate your log file space requirements, consider the following factors:
• peak count of component transactions per second at your site
• total number of component transactions per day at your site
• number of days that you want records to be available for online review
• desired size of each individual log file, in megabytes

You will need to estimate the peak and total component transaction rates for your site. For the total number of transactions per day, you can refer to the Total Inserts field on the OPSTATS view. That value is the total number of records that MainView Transaction Analyzer has stored since it was last started (as indicated by the Report Interval field). You can normalize that value to 24 hours to estimate the total number of component transactions per day.

To define an NGL LOGSET by using AutoCustomization

1. In the first AutoCustomization panel, specify the following basic information about the LOGSET and its log files, and press Enter:

   LOGSET type	Description
   LOGSET Name	3- to 16-character name used to identify the LOGSET BMC recommends that you include a product identifier (such as MTA or MVTA) in the name to distinguish this LOGSET from LOGSETs that are being used by other products. Valid characters for a LOGSET name include any printable EBCDIC character, except /, \, the cent sign, and broken-bar character- code points, which are reserved. You can include a period anywhere except as the first character. You cannot use leading or embedded blanks.
   Log File Name Prefix	Data set prefix for the allocated log files
   Log File Storage Class	Nname of a storage class, if the log files are to be managed by SMS
   Log File Mgmt Class	Name of a management class to be used when allocating the log files If you specify a management class, you must specify a storage class; otherwise, the management class is ignored.
   Log File Data Class	Name of a data class to be used when allocating the log files If you specify a data class, you must specify a storage class; otherwise, the data class is ignored.
   Log File Data Volume	Name of a volume where the log file data sets are to be allocated If the log file data sets are to be managed by SMS, leave this field blank.
   Do you need to define your LOGSET	Whether you need to define a new LOGSET If you specify YES, additional panels are displayed to collect more information about your LOGSET requirements. If you specify NO, this step is bypassed and MainView Transaction Analyzer uses a previously defined LOGSET. No additional panels are displayed.

2. To determine the amount of space required for the allocated log files, specify the following information on the next panel, and press Enter.

   Allocated log file information	Description
   Peak Component Rate	Estimated peak count of component transactions per second
   Total Component Rate	Estimated total number of component transactions per day, in millions
   Component Retention Period	Number of days that component transaction records should be available for online review
   Log File Size	Size of the individual log files that will hold component transaction records, in megabytes

3. On the next panel, specify information about the LOGSET definition job that will be created:

   LOGSET definition information	Description
   Target library	Name of the library where the LOGSET definition job is to be placed, such as user.dataset.UBBSAMP
   Definition job	Member name for the LOGSET definition job
   Replace member?	NO Specify YES only if the target library already contains a LOGSET definition job of the same name and you want to replace it; otherwise, specify NO. When you press Enter, a job to define the LOGSET is created and an editing session opens so that you can make further changes, if necessary

4. Use the SUBMIT command to submit the job.
   Submitting the job completes the LOGSET definition.