Using groups

Groups are available for grouping together work qualifiers to make classification simpler. You can create groups to collect together work when you don't have a standard naming convention that allows masking or wildcarding. A group is a collection of the same work qualifiers. For example, you may want to create a group of started tasks because you want to assign them all to the same service class.

Start of change Groups are allowed for all work qualifiers except for Priority and zEnterprise Service Class. End of change

Group types are specified by adding G to the type abbreviation. For example, a transaction group name group is indicated as TNG.

Start of change Group types are usually valid for the same subsystem types as the underlying work qualifiers they group. For details on which qualifiers are valid for which subsystems, see Table 8. The only exception to this rule is the Subsystem Parameter Group which is not valid for subsystem type STC although the underlying Subsystem Parameter work qualifier is. End of change

Qualifier groups of more than 5 members are quicker to check than single instances in the classification rules. So if you have, for example, a long list of CICS® or IMS™ transaction names that you want to group in a service class or report class, consider setting up a group.

Example 1: Groups

If you want to assign a large number of CICS transactions to the same service class, you can create a transaction name group (TNG). You name the group, for example CICSCONV, and list all the transaction names you want included in the group.

 Qualifier type . . . . . . . : Transaction Name
 Group name . . . . . . . . . . CICSCONV  (required)
 Description  . . . . . . . . . CICS Conversational Group
 Fold qualifier names?  . . . . Y (Y or N)

 Qualifier Name  Start  Description
 CDBC            ___    ________________________________
 CDBI            ___    ________________________________
 CDBM            ___    ________________________________
 CEBR            ___    ________________________________
 CECI            ___    ________________________________
 CECS            ___    ________________________________
 CEDA            ___    ________________________________
 CEDB            ___    ________________________________

 Qualifier type . . . . . . . : Transaction Name
 Group name . . . . . . . . . . CICSLONG  (required)
 Description  . . . . . . . . . CICS Long-Running Transaction
 Fold qualifier names?  . . . . Y  (Y or N)

 Qualifier Name  Start  Description
 CDB0            ___    ________________________________
 CSGX            ___    ________________________________
 CSNC            ___    ________________________________
 CSNE            ___    ________________________________
 CSSX            ___    ________________________________

Then you use those group names in the classification rules, as shown in this panel:

 Subsystem Type . . . . . . . : CICS
 Description  . . . . . . . . . CICS transactions

   -------Qualifier-------------            -------Class--------
   Type       Name     Start                Service     Report
                                  DEFAULTS: CICSMED     ________
1  TNG        CICSCONV ___                  CICSCONV    ________
1  TNG        CICSLONG ___                  CICSLONG    ________

Start of change For work qualifiers running longer than 8 characters, you can use a start position for each group member to indicate how far to index into the character string for a match. Note that the start position needs not be the same for all group members. Furthermore, groups of such long work qualifiers can be nested. End of change

Example 2: Groups of long work qualifiers

Assume you want to associate all JES2 work from a certain group of accounts with service class JESSLOW, except if it originates in a certain group of departments, in which case JESFAST should be used. The example shows the rules:

 Qualifier type . . . . . . . : Accounting Information
 Group name . . . . . . . . . . ACCOUNTS  (required)
 Description  . . . . . . . . . Accounts for JESSLOW
 Fold qualifier names?  . . . . Y  (Y or N)

 Qualifier Name  Start  Description
 020175          ___    ________________________________
 030275          ___    ________________________________
 040375          ___    ________________________________
 060575          ___    ________________________________
 070675          ___    ________________________________
 080775          ___    ________________________________
 090875          ___    ________________________________
 Qualifier type . . . . . . . : Accounting Information
 Group name . . . . . . . . . . FASTDEPT  (required)
 Description  . . . . . . . . . Department for JESFAST
 Fold qualifier names?  . . . . Y  (Y or N)

 Qualifier Name  Start  Description
 PURCHASE        8      ________________________________
 SALES           8      ________________________________
 SHIPPING        8      ________________________________
 ITDEP*          11     ________________________________
 HRDEP*          11     ________________________________

Then you use those group names in the classification rules, as shown in this panel:

 Subsystem Type . : JES Fold qualifier names?  Y (Y or N)
 Description . . . CICS transactions
   --------Qualifier--------      -------Class--------
   Type       Name     Start       Service     Report
                            DEFAULTS: JESMED   ________
 1 AIG        ACCOUNTS ___            JESSLOW ________
 2   AIG        FASTDEPT ___          JESFAST ________

A job with accounting information '040375,SHIPPING' is then assigned service class JESFAST. Similarly, a job with accounting information '070675,D71ITDEP' is assigned service class JESFAST. A job that contains the job statement '050475,CONTROL ' is assigned service class JESSLOW, because the department is not contained in the FASTDEPT group. A job with accounting information '020177,SALES ' is assigned the default service class JESMED, because the account number does not match group ACCOUNTS, and therefore the system never checks any sub-rules.