CA OPS/MVS

Expand all | Collapse all

Understanding status update by OPSMAIN

Jump to Best Answer
  • 1.  Understanding status update by OPSMAIN

    Posted 10-11-2017 05:04 AM

    Hello!

     

    I was having problems with some rules which were setting status of subsystem. I want to understand what is the source of this action (in bold):

     

    07:00:00  STCTBL.PCSE UPDATED by OPSMAIN LPAR.TOPC1 DESIRED_STATE=DOWN      
    07:00:10  STCTBL.PCSE UPDATED by PCSE LPAR.TOPC2 CURRENT_STATE=BATCH        
    07:01:48  STCTBL.PCSE UPDATED by JSIPCSE LPAR.TOPC3 CURRENT_STATE=UNKNOWN   
    07:01:48  STCTBL.PCSE UPDATED by JSIPCSE LPAR.TOPC3 DESIRED_STATE=UP        
    07:01:48  STCTBL.PCSE UPDATED by OPSMAIN STATESET CURRENT_STATE=DOWN

     

     

     

    As you can see we had some rule before which put the subsystem PCSE into UKNOWN state. We don't know what put PCSE in status DOWN - it just says OPSMAIN (no rules, no details).

     

    Thank You



  • 2.  Re: Understanding status update by OPSMAIN
    Best Answer

    Posted 10-11-2017 03:41 PM

    Hello Wladyslaw,

     

    Setting the CURRENT_STATE of a resource to UNKNOWN makes SSM to trigger the SSMSTATE request rule. This rule and its user exit SSMSTAUX have code to detect the current state of some pre-defined resources. You may need to update the user exit SSMSTAUX to include code to detect if this PCSE subsystem is really active otherwise SSM will just try to see if there is an active started task with this name and set the current state to DOWN if it doesn't find one.

    Please, read the comments section of the rule SSMSTATE and user exit SSMSTAUX in the CCLXRULM library for details.

     

    Regards,

    Mario

     

    Carlos Mario Filho
    Principal Support Engineer

    CA Technologies



  • 3.  Re: Understanding status update by OPSMAIN

    Posted 10-24-2017 10:25 AM

    Thank you very much!