GROUP command

Usage

Use the GROUP command to collect several OMEGAMON® XE for DB2® PE identifier values under one name. When you request a report and specify this name by using the INCLUDE or EXCLUDE subcommand option, the events for all individual items are consolidated into one.

Usage notes

• With the GROUP command you can define a named set of OMEGAMON XE for DB2 PE identifier values. A set name can contain values or lists of values for a particular identifier.
• When you request a report and specify this name in INCLUDE or EXCLUDE, the events for all individual items are consolidated into one. For example, you might request that all PRIMAUTHs used by the accounting department be reported under the set name ACCTS. Thus, the entire department is reported in one entry rather than in individual entries for each PRIMAUTH.
• The GROUP command is only used to collect OMEGAMON XE for DB2 PE identifier values. It is not related to DB2 data sharing groups, and should not be confused with the GROUP keyword of the SCOPE subcommand option, or the GROUP OMEGAMON XE for DB2 PE identifier.
• Sets can be used in the REDUCE and REPORT subcommands of the following report sets:
  • Accounting
  • I/O Activity
  • Locking
  • SQL Activity
  • Utility Activity
• Sets can also be used in the following report sets and commands, however, OMEGAMON XE for DB2 PE treats them as lists:
  • Statistics
  • Audit
  • Record Traces
  • GLOBAL in all report sets
  • FILE and TRACE in all report sets

General rules regarding the use of GROUP

• Each GROUP command defines one set.
• You can use as many GROUP commands as you want.
• All values associated with a set must be for the same OMEGAMON XE for DB2 PE identifier.
• You can use more than one GROUP command for the same OMEGAMON XE for DB2 PE identifier.
• The combination of set name and OMEGAMON XE for DB2 PE identifier must be unique in the job step.

Rules applying to the use of GROUP with INCLUDE and EXCLUDE

• All set names that are referenced with INCLUDE or EXCLUDE must be defined by a GROUP command in the same job step.
• Set definitions are searched in the order that they are specified in.
• If more than one set name is used in INCLUDE or EXCLUDE, and the sets contain common values, the data is assigned to the first set that the value is found in. When OMEGAMON XE for DB2 PE has found a value in a set, it does not attempt to find other occurrences of the same value.

Syntax

>>-GROUP-------------------------------------------------------->
 
                                     .-,--------------------------.
                                     V                            |
>--(--PE_identifier--(--set name--(----+-value------------------+-+--)--)--)-><
                                       +-L(list name)-----------+
                                       '-R(from_value,to_value)-'
 

Subcommand options

The syntax diagram shows the options that are available with this subcommand. See OMEGAMON XE for DB2 PE subcommand options for comprehensive descriptions of these options. The following list gives additional or specific descriptions of selected options, where appropriate.

PE_identifier

The OMEGAMON XE for DB2 PE identifier that the set contains. Identifiers valid for the different report sets are shown in the following table.

Table 30. OMEGAMON XE for DB2 PE identifiers used with GROUP

OMEGAMON XE for DB2 PE Identifier	Accounting	I/O Activity	Locking	Utility Activity	SQL Activity
CONNECT	•	•	•	•	•
CONNTYPE	•	•	•	•	•
CORRNAME	•	•	•	•	•
CORRNMBR	•	•	•	•	•
DATABASE		•	•
DATASET		•
ENDUSER	•
MAINPACK	•
ORIGAUTH	•	•	•	•	•
PACKAGE	•
PAGESET		•	•
PLANNAME	•	•	•	•	•
PRIMAUTH or AUTHID	•	•	•	•	•
REQLOC	•	•	•	•	•
TRANSACT	•
WSNAME	•

set name

The name of the set. It must be unique within the job step. Set names can consist of up to eight alphanumeric characters (A -- Z, _, #, $, @, 0 -- 9) with no embedded spaces. Set names must begin with a character in the range A to Z.

value

A value for the specified OMEGAMON XE for DB2 PE identifier.

Identifier values must consist of the following characters: A -- Z, #, $, @, >, <, or 0 -- 9. If the value you want to include contains a character that is not in this list, use an asterisk in its place or place the string in quotes.

Except for the CONNTYPE identifier, a value can be specified in generic form. Place an asterisk (*) in the value to indicate that any value is valid. For example:

• * processes any value.
• ABCD* processes any value starting with ABCD.
• *BCDE processes any value in the first character position where the second, third, fourth, and fifth character positions contain BCDE.
• **CDE processes any value in the first and second character positions where the third, fourth, and fifth character positions contain CDE.
• A*CDE processes any value in the second character position where the first character position contains A, and the third, fourth, and fifth character positions contain CDE.

L

Indicates that the following value is a list name. You cannot use the generic form for list names. For example, L(ABC*E) cannot be used.

R

Denotes a range of values beginning with from_value and ending with to_value. The from_value must be less than to_value. The generic form can be used only in the last character position in range values. For example, R(AUTH1*,AUTH2*) is acceptable, but R(AUTH*1,AUTH*2) is not.

Note:

1. Quoted values can also be specified. Any quoted string is accepted, provided that it passes length and format checking.
2. Range cannot be specified for CONNTYPE.