Why does MainView SRM SGP address space use a lot of central storage?

Version 1
    Share:|

    This document contains official content from the BMC Software Knowledge Base. It is automatically updated when the knowledge article is modified.


    PRODUCT:

    MainView SRM Reporting


    COMPONENT:

    MainView SRM Reporting


    APPLIES TO:

    V7.7.00 V7.8.00



    QUESTION:

    MainView SRM SGP address space is using a lot of central storage.


    ANSWER:

     

    SGP (performance monitor) does indeed take up a lot of storage.  It has a large structure in the main address space which cannot be customized.  There are three data spaces that it defines and uses.  One is called SGPSMFB, which is used to collect SMF records processed by SGP.  Again no changes can be made to this data space.

      

    The other two data spaces you have some control over.  The SMFRECB data space accumulates information about the various resources.  Data in this data space is then written to the database data sets at the end of each interval.  Each resource type has a value in the SMMSYSxx member that controls how much of the data space may be used for that resource.  For example SGP_MAXLCUS determines how much space is allowed for logical control unit information.  You could artificially make this value very small.  You would probably get warning messages from SGP, urging you to increase this value.  You could ignore those messages knowing that information for that resource type would probably be of little or no value.

      

    The third data space is SGPDSNI.  This contains data set names and a little control information for each name.  There is currently a problem with how we are handling this data space (APAR BAG4586), fix are PTF BPG7337 (for V7.8.00) and BPG7338 (for V7.7.00). In addition to apply the PTF, customer could then restrict the data sets to be monitored using the SGPFILTR function (under SVOS).  We recommend excluding temporary data sets.  Some customers may wish to exclude generation data sets, as each one is monitored separately.  Further data set name restrictions are at the desire of the customer.

     


    Article Number:

    000105896


    Article Type:

    FAQ/Procedural



      Looking for additional information?    Search BMC Support  or  Browse Knowledge Articles