DISTRIBUTE command
This section provides an overview of the Auxiliary command
DISTRIBUTE.
Usage
The DISTRIBUTE command is a stand-alone
command used to generate frequency distribution information. It is
used for OMEGAMON® XE for DB2® PE data
associated with Accounting, I/O Activity, Locking, SQL Activity, and
Utility Activity report sets.
Usage notes
- You can control the collection of this data by specifying OMEGAMON XE for DB2 PE identifiers
in the DISTRIBUTE command. You can also alter the frequency distribution
limits to accumulate the data in appropriate ranges. After batch execution,
the collected frequency distributions, which have been written to
the frequency distribution data set, can be viewed by using graphics.
- In the reports, data is averaged for many occurrences. If there
is a large number of events that the data is averaged over, the result
can be difficult to analyze. An average value can also make a small
number of events that have exceptionally high or low values difficult
to detect. However, the DISTRIBUTE command can help you locate unusual
values by dividing the events into ranges.
- You can specify as many DISTRIBUTE commands as you want in a job
step.
- You can specify the same field in several DISTRIBUTE commands,
with different OMEGAMON XE for DB2 PE identifiers.
- You can define up to ten distribution ranges for a particular
field. During data reduction, OMEGAMON XE for DB2 PE keeps
count of the number of records with values in each of the defined
ranges. The following information is generated for each of the defined
fields:
- Frequency distribution
- Average value
- Standard deviation
- Maximum value
- The data generated by DISTRIBUTE is, by default, written to the
DD statement DISTDD. You can change this ddname by using the GLOBAL
command. For more information about GLOBAL, see GLOBAL command.
Syntax

>>-DISTRIBUTE--(--| FIELDID block |--| DISTRIBUTE block |--)---><
FIELDID block
|--FIELDID--(--field name--+------------+--)--------------------|
'-.qualifier-'
DISTRIBUTE block
|--+-| LIMITS block |------+------------------------------------|
+-| UNITS block |-------+
'-| IDENTIFIERS block |-'
LIMITS block
.-(9)-------------------------------.
V .-1 5 10 30 50 100 300 500 1000-. |
|--LIMITS--(----+-value-------------------------+-+--)----------|
UNITS block
(1)
.-MILSECS------.
| (2) |
|--UNITS--(--+-COUNT--------+--)--------------------------------|
+-SECONDS------+
+-MINUTES------+
'-HOURS--------'
IDENTIFIERS block
.-(3)---------------.
V .-PRIMAUTH------. |
|--IDENTIFIERS--(----+-PE_identifier-+-+--)---------------------|
Notes:
- This is the default for time fields.
- This is the default for numeric fields.
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.
- FIELDID (field name)
- The keyword for the field. Valid values are shown for:
- Accounting
- For details refer to Keywords
- I/O Activity
- Refer to Table 24
- Locking
- Refer to Table 25
- SQL Activity
- Refer to Table 26
- Utility Activity
- Refer to Table 27
- qualifier
- Accounting buffer pool, DDF, package, and RLF fields can be qualified
by buffer pool ID, remote location, package name, and RLF type, respectively.
An example for a buffer pool ID is BP32K.
- LIMITS
- The limits of the ten ranges for frequency distribution. At least
one limit is required. Ranges can be entered in any sequence. Duplicate
values are ignored. Counts are kept for each of the ten ranges. The
default for LIMITS is:
LIMITS(1,5,10,30,50,100,300,500,1000)
This
counts records in the following ranges:
- > 0 and <= 1
- > 1 and <= 5
- > 5 and <= 10
- > 10 and <= 30
- > 30 and <= 50
- > 50 and <= 100
- > 100 and <= 300
- > 300 and <= 500
- > 500 and <= 1 000
- > 1 000
- UNITS
- The units for the LIMITS. This keyword is optional. The default
is the count for fields containing numeric data, and milliseconds
for time fields. The following values are valid:
- MILSECS (milliseconds)
- SECONDS
- MINUTES
- HOURS
- COUNT
- IDENTIFIERS
- The OMEGAMON XE for DB2 PE identifiers
used in collecting distribution data. You can specify up to three
types of identifiers. Frequency distribution data is collected for
each unique combination of the selected identifiers. This keyword
is optional. The default is PRIMAUTH.
Note:
DISTRIBUTE uses REDUCE
filters and interval/boundary values.
The following
table shows the OMEGAMON XE for DB2 PE identifiers
valid for the different report sets.
Table 11. OMEGAMON XE for DB2 PE identifiers used with DISTRIBUTE
| OMEGAMON XE for DB2 PE Identifier |
Accounting |
I/O Activity |
Locking |
Utility |
SQL Activity |
| CONNECT |
• |
• |
• |
• |
• |
| CONNTYPE |
• |
• |
• |
• |
• |
| CORRNAME |
• |
• |
• |
• |
• |
| CORRNMBR |
• |
• |
• |
• |
• |
| DATABASE |
|
• |
• |
|
|
| DATASET |
|
• |
|
|
|
| ORIGAUTH |
• |
• |
• |
• |
• |
| MAINPACK |
• |
|
|
|
|
| PAGESET |
|
• |
• |
|
|
| PLANNAME |
• |
• |
• |
• |
• |
| PRIMAUTH or AUTHID |
• |
• |
• |
• |
• |
| REQLOC |
• |
• |
• |
• |
• |
Example using the DISTRIBUTE command
In
this example, QBACGET.BP32K (Getpage requests for the 32 KB buffer
pool) is the field identifier for frequency distribution. A frequency
distribution is calculated for every combination of PRIMAUTH and PLANNAME
occurring in the input data. The data is accumulated in one of the
eight ranges specified in the LIMITS option. The ranges are less than
1, between 1 and 10, between 10 and 20, and so on. The last range
is greater than 2 000.
The following JCL fragment is an
example of the distribute command:
·
·
·
//SYSIN DD *
DISTRIBUTE (
FIELDID (QBACGET.BP32K)
IDENTIFIERS (PRIMAUTH,PLANNAME)
LIMITS (
1
10
20
50
200
1000
2000
)
)
EXEC
/*