What would be the impact of defining all BMC Impact Integration for z/OS cells to each of the MainView AutoOPERATOR PASes?

Version 2
    Share:|

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


    PRODUCT:

    MainView AutoOPERATOR


    APPLIES TO:

    MainView AutoOPERATOR



    QUESTION:

    MainView AutoOPERATOR - all supported versions
    BMC Impact Integration for z/OS - all supported versions

     What would be the impact of defining all BMC Impact Integration for z/OS cells to each of the MainView AutoOPERATOR PASes?

    We have a total of 18 cells. If we use one common definition in BBPARM member AAOGMExx to define all 18 cell connections to all our PASes, does that have an impact that we should consider?  
    Or is it better selectively to connect the cells to the PAS where we expect direct communication?  


    ANSWER:

     

    Legacy ID:KA418121

      

    The recommendation is to define to the PAS only the cells you want to communicate directly with, and to use the BBCFG ddname to define the suffix of the BBPARM AAOGMExx member.  

      

    If you are preparing for a change in connections, you can define multiple AAOGMExx members and have automation reset the connections with a .E P AAOGMExx,RECYCLE command. This command would allow you to change from one suffixed member to another, in effect allowing you to change which cells are connected to the PAS.  

      
      Besides the storage consideration, this direct connection to only the cells communicating with the PAS provides for less overhead and a simpler implementation.   
      
        
      
      It is recommended that each PAS be connected to no more than 5 cells. It is difficult to be exact about this number, as the amount of storage below the line available to the PAS varies by system configuration, and according to what else is running within the same PAS. It is likely that the number that works well in MainView AutoOPERATOR with BMC Impact Integration for z/OS is less than what will work well when BMC Impact Integration for z/OS runs by itself in its own PAS (when you do not own AutoOPERATOR). This is due to the amount of other activity that may occur within each PAS.   
      
    Related Products:  
       
    1. MainView AutoOPERATOR
    2.  
    3. BMC Impact Integration for z/OS

     


    Article Number:

    000026509


    Article Type:

    FAQ/Procedural



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