Can RTCS be cycled without affecting MainView SRM products

Version 1
    Share This:

    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


    COMPONENT:

    MAINVIEW SRM Allocation StopX37/II User Guide and Reference


    APPLIES TO:

    MainView SRM Allocation 7.8.00 7.9.00, MainView SRM Automation, MainView SRM Reporting



    QUESTION:

    Can the RTCS (Runtime Component System) Started Task be cycled without affecting MainView SRM products?


    ANSWER:

    RTCS cannot be shutdown until all of the address spaces that are currently using its services have first been shutdown. Since MainView uses RTCS every PAS and CAS must be stopped in addition to any TSO user that has connected to MainView.  

    Customers almost always find it easier to restart RTCS as part of an IPL. However, it can be done.  Please note there is a risk of an unplanned IPL when stopping SVOS; this must be done with caution.

    We suggest the customer first issue the console command:

    F RTCS,SHUTDOWN,LIST
    This will list every address space that must be stopped prior to issuing the STOP RTCS command, the list may extend beyond MainView SRM products.

    If the customer still wants to proceed, it is advisable to reduce running workload before beginning. This can be done by draining initiators and quiescing systems like CICS and DB2, to prevent allocations while SVALLOC is shut down. 


    If after issuing command F SVOS,SHUTDOWN, to bring down MainView SRM, the customer receives message SVO0622W, the  recommendation is to issue the WAIT command to message SVO0623I, and perform the D GRS,RES=(ETILOAD,*) command, to determine what holds the enqueue on the SVOS load module. Unless an IPL is imminent, a reply of KILL is NEVER recommended to message SVO0623I.  See message descriptions below.

    Once all the listed address spaces are stopped, RTCS can be stopped. Restart RTCS as normal and then restart the other address spaces that were stopped.  Do not issue the FORCE,ARM command to take RTCS out of the system unless all address spaces have disconnected and STOP does not work. Doing so could result in numerous unpredictable failures.

    RTCS (and the CAS) leave behind some storage in CSA that they reuse when they hot start. Most CSA is freed as the owning PAS and or CAS terminates.

    Also reference documentation on the site:  https://docs.bmc.com/docs/  and search for “Stopping RTCS”.

    Note: MainView SRM StopX37/II stand-alone does not require RTCS to be run, but some installations may be using RTCS without realizing it, based on specifications in the SMMSYSxx member and/or the license key applied.   
     

                                                
    SVO0622WWAITING FOR prdName. TO BECOME DORMANT ON subsys

    Explanation: SVOS is waiting to deactivate the product. Another task is currently using the product. SVOS waits until the task no longer requires the product's services before deactivation is allowed. subsys is the subsystem name used by this instance of SVOS.
    User response: No action is necessary.
    SVO0623ISHUTDOWN CANNOT COMPLETE. REPLY 'WAIT' or 'KILL'
    ********************************************************************************************* *** Another task holds enqueue on ETILOAD.
    ***
    *** Tasks holding enqueue: jobName1 jobName2 etc.
    *** ASIDs: jobAsid1 jobAsid2 etc.
    ***
    *** System command /D GRS,RES=(ETILOAD,*) might be used to
    *** list the tasks holding the enqueue.
    ***
    *** Reply of WAIT is the recommended response. Reply of
    *** KILL should only be used as a last resort for impending
    *** IPL.
    ***
    *** You must reply WAIT or KILL. ************************************************************************************************

    Explanation: These messages follow the SVO0622I message, prompting the operator for a response on how to continue the shutdown of SVOS. One or more tasks are holding enqueue on 'ETILOAD' that prevents completion of the SHUTDOWN command. Shutdown halts awaiting operator response.
    User response: Under normal circumstances, the operator should respond WAIT to permit current tasks with enqueue on ETILOAD time to be completed. BMC Software only provides the KILL option for an impending IPL. The D GRS,RES=(ETILOAD,*) console command can be used to identify current tasks that hold enqueue on ETILOAD. Up to four jobs and their address space identifiers will be listed in the messages to identify who holds the enqueue.

     


    Article Number:

    000170803


    Article Type:

    FAQ/Procedural



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