When the MainVIew SRM started task (SVOS) is shutdown, the task orphans 21K of storage in CSA

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 Allocation


    APPLIES TO:

    MainView SRM StopX37/II, MainView SRM Reporting, MainView SRM ESA



    QUESTION:

    Customer reports that when the MainVIew SRM started task (SVOS) is shutdown, the task orphans 21K of storage in CSA


    ANSWER:

    Loader stubs remain after each MainView SRM (SVOS) shutdown and are chained if multiple shutdowns occur.  They are vehicles to allow processes to find their way back to the original IBM modules hooked.  They allow multiple vendors to work in the same space without regard to which product is started first.  Vendors that do not follow such schemes require to be started first and shutdown last prior to an IPL.  If the stubs did not remain in place then any allocation using the respectively hooked IBM modules abends and only IPL resolves the situation.  The storage is not orphaned.  It is utilized by the next startup.   


    Article Number:

    000135435


    Article Type:

    FAQ/Procedural



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