MainView SRM Allocation and Stopx37/II v7.6 and v7.7 Performance PTFs

Version 2
    Share This:

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


    MainView SRM Allocation


    MainView SRM Allocation



    MainView SRM Allocation v7.6
    MainView SRM Allocation v7.7


    MainView SRM Stopx37/II v.7.6
    MainView SRM Stopx37/II v7.7


    We provide here a list of PTFs that could improve performance in MainView SRM Allocation and/or MainView SRM StopX37/II products.






    Legacy ID:KA408381


    The below list of PTFs were written to improve performance in the MainView SRM Allocation and/or StopX37/II products.
    PTF improvements are carried forward to newer releases of MainView SRM. 


    SMS-managed datasets:
    With many users converting to full SMS-managed shops, the SPACPRIM and SPACSWIR functions were redesigned to prevent multiple “re-drives” of an extend (SPACSWIR) or an allocation (SPACPRIM) during DFSMS volume selection.  A new SPACPRIMACS global parameter was introduced as part of this change in APAR BAG4166.  Documentation for the SPACPRIMACS global is provided after the below list of PTFs. 


    It is not uncommon to see additional changes with any new code design and you should provide the “Recommended PTF” to customers when listed.  In short, any PTF highlighted in BLUE would be the recommended solution for customers.  (Note: TBD is short for to-be-determined.) 


    Ver Originating PTF Recommended                            PTF Performance improvement description


    7.6 BPG6327    BPG6362 (PUT1102A)                       Disables unused hooks for StopX-only customers (X37II) when functions are not active in SMFUNCxx.
    7.7 Base code  BPG6438 (GA code)  


    7.6 BPG6352    BPG6875                                              Determines available space in storage group for SPACSWIR processing and requires only one redrive of EOV for SMS-managed datasets.
    7.7 Base code  BPG6874   


    7.6 BPG6550   BPG6875                                               Determines available space in storage group(s) for SPACPRIM processing and requires only one redrive of allocation for SMS-managed datasets.
    7.7 BPG6555   BPG6874  


    7.6 BPG6627   BPG6735 (PUT1202B)                       Removes call to PRSPOOLV for each device in the EDL (eligible device list) and each pool, which eliminates    ESTAE/GETMAIN overhead in DASDPOOL.
    7.7 BPG6626   BPG6734 (PUT1202B)   


    7.7   BPG6680 (PUT1202A) TBD                                Removes call to PRSPOOLV for each device in the EDL during IDCAMS DEFINE (VSAM). Improves DASDPOOL performance for VSAM datasets created with IDCAMS. 
                                                                                              (Note: Not done for version 7.6.)


    7.6   BPG6697 (PUT1202B)   TBD                             Limits or disables DSAB/SIOT search for trace ddnames during each SRM intercept  (hook). Reduces overhead in MainView SRM module PRS90020 for online systems with many allocated datasets.
    7.7   BPG6698 (PUT1202B)   TBD     


    SPACPRIMACS= SMMSYSxx global parameter                             
    Purpose: The SPACPRIMACS global parameter determines if SPACPRIM will invoke the DFSMS ACS routines to obtain list of available storage group(s) for a single-volume SMS allocation.                                
    When SPACPRIMACS is set to NO, MainView SRM will use the SPACPRIM RLST reduction percentage to lower the primary amount before making another attempt to satisfy the allocation request. Depending on the available space in the storage group(s) and the original primary request, SPACPRIM can make multiple attempts to recover the allocation.                                                        
    When SPACPRIMACS is set to YES, MainView SRM will call the DFSMS ACS routines to obtain the list of available storage groups for a single-volume allocation and determine available space before making another attempt to satisfy the allocation request. This typically leads to much better allocation performance, since SPACPRIM will adjust the primary to the available space and only make one attempt to recover the allocation.                                         


    For better performance, SPACPRIMACS=YES is the preferred setting. 
    If you find SPACPRIM is causing your SMS allocations to select a volume from the wrong DFSMS storage pool, then your ACS routines could be using read-only ACS variables not supplied by MainView SRM during SPACPRIM recovery. MainView SRM supplies many of the DFSMS read-only ACS variables typically used to assign DASD storage group(s). If your ACS routines are using any of the following read-only ACS variables to assign DASD storage pools, then you may want to consider setting SPACPRIMACS=NO:                          
     &MSPDEST    &MSPARM    &MSPOLICY       &EXPDT         &MEMHLQ            
     &MEMLLQ     &MEMN        &MEMNQUAL   &FILENUM    &LABEL             


    Note: MainView SRM only invokes the DFSMS ACS routines for new data allocations (&ACSENVIR=ALLOC). MainView SRM will not invoke the DFSMS ACS routines when a data set is being recalled by HSM.  
    Syntax:    SPACPRIMACS=YES | NO | Y | N                                        
    Default:               SPACPRIMACS=YES                                                     

    Related Products:  
    1. MainView SRM StopX37/II
    3. MainView SRM StopX37/II
    5. MainView SRM Allocation


    Article Number:


    Article Type:

    Solutions to a Product Problem

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