Defining the group context

To use the product-defined dynamic contexts, specify CONTEXT DSG:dsgroup, where dsgroup is the data sharing group name.

If your site has already defined group contexts, or you want to use your own group context names, complete the following procedures:

• To view defined SSI contexts
• To define an SSI context

To view defined SSI contexts

To define an SSI context

1. On the COMMAND line, type CONACTZ.This view lists all SSI contexts (as known by your CAS and any connected CASs). Your CASID is shown on the window information line.

   If you have multiple BMC AMI Ops products installed, you can observe one of the most powerful features of SSI here: the same context can be defined for several different BMC AMI Ops products. Obviously, because each product might look at different target types, the selection criteria can vary.

2. Select the default context of ALL for BMC AMI Ops Monitor for Db2.The CONACT view showing each of the defined Db2 target subsystems is displayed.

   >W1 =CONACTZ==CONACT===SYSD=====*========ddmmmyyyy==11:02:43====PLEXMGR==D====3
   CMD SSI      Product  Target   Status           Description
   --- Context- -------- Context- of_Target---     ------------
       ALL      MVDB2    DB0HC    ACTIVE           BMC AMI Ops Monitor for Db2
       ALL      MVDB2    DB1HC    ACTIVE           BMC AMI Ops Monitor for Db2
       ALL      MVDB2    DB2HC    ACTIVE           BMC AMI Ops Monitor for Db2
3. Type CONDEF on the COMMAND line.The context definition dialog is displayed.
4. Browse an example of a context definition.If a data sharing group context already exists, hyperlink on the SSI context name to see how the target filters were defined. If you do not see the group, select any other context. (You will at least see the default context of ALL.)
5. Press F3 to return to CONDEF.
6. Type EDIT on the COMMAND line to obtain an edit lock.

7.  Type ADD on the COMMAND line to display the Add SSI Context Definition panel.

   >W1 =CONDEF============SYSD=====*========(00 EDIT          )====PLEXMGR==D===10
     -------------------------- ADD SSI CONTEXT DEFINITION ---------------------
     COMMAND ===>
     SSI Context ===>
     Description ===>
     Inclusion Filters: (Target is included if any are true)
       1TGTNAME IN (DB1P,DB2P)
       2
       3
       4
       5
       6
       7
       8
     Equivalent SUBSTITUTION parameters to be used in filter expression:
      %1=TGTNAME     %2=TGTSYSTEM   %3=TGTPRODUCT  %4=TGTSERVER
      %5=TGTDESC
     Type  END to add the SSI context definition
           CANcel to leave without adding

   In this panel, you define the context name and description, and the selection filters for the targets that will be part of this context. Help is available on each of the fields.

   You can define several filter conditions, but, in this case, all you will need is to filter by TGTNAME. (The shorthand is %1 ). Because most sites use some kind of naming convention for the members, you probably need only one filter condition. The following example would include Db2s named DB1P, DB2P, and so on:

   %1 = DB?P

   If you prefer, you can define an IN list. The following example would include only the Db2s named DB1P and DB2P:

   TGTNAME IN (DB1P,DB2P)

8. Type the following commands to activate this definition:

   Command	Action
   END	To return to the CONDEF view and complete the ADD
   SAVE	To save the information
   INSTALL	To dynamically activate this SSI context in this CAS

9. If multiple CASs are involved, you need to complete this definition in each CAS.CASACT will show you a list of CASs and you can type CON casID to switch to another CAS.

10. If the CASs all share the same BBPARM (you still see the new definition after you switch to another CAS), you only need to type CONDEF, then EDIT, and then INSTALL.

    Note

    If the CASs do not share the same BBPARM, repeat steps Step 7 through Step 9 for each CAS.

11. Press F3 until you return to EZDSSI.