CA OPS/MVS

Expand all | Collapse all

Creating compound resources

  • 1.  Creating compound resources

    Posted 03-08-2018 06:31 AM

    Any guidelines for creating a 'compound' SSM resource in Ops/MVS? For example, if application X requires that CICS regions A & B are up, MQ-queues C & D are not in an alert status and started task E is also up, then we can say that X is up if all of it's sub-components are up.

     

    Does anyone have any ideas for this or done anything like this?

     

    One approach might be to have an SSM table for these compound resources and ensure that all the sub-components are also managed by SSM, with a new field describing what 'compound resource(s)' each sub-component is part of. The compound SSM table could then be updated when any other SSM component is updated E.g.

     

    STCTBL

    NAME   CURRENT_STATE APPLICATION(S)

    CICSA   UP                          X, Y

    CICSB   DOWN                    X, Z

    STCE    UP                           X 

     

    MQTBL

    NAME       CURRENT_STATE APPLICATION(S)

    QUEUE1   NORMAL                X, Y, Z

    QUEUE2   PROBLEM              X

    QUEUE3   NORMAL                X, Y, Z

     

    APPTBL

    NAME CURRENT_STATE

    X         NOT_OK         (Because CICSB is DOWN and QUEUE2 is in PROBLEM state)

    Y         OK                   (all component tasks are OK) Z NOT_OK (Because CICSB is DOWN)

     

    Is this functionality implemented via the 'Groups' facility in SSM V3?

     

    Thanks,

     

    Steve

     



  • 2.  Re: Creating compound resources

    Posted 03-08-2018 06:39 AM

    Ok - I think need to look at the 'groups' manager.