X hits on this document

1354 views

0 shares

0 downloads

0 comments

47 / 236

Interface Operation

FIGURE 3. Sample Collector Option Member (continued)

SMFNUM(185)

******************************************************************* ** **

** ** ** **

GROUPS ARE FOR COLLECTION PURPOSES AND ARE # PSB IDENTIFIES A PSB IN THE GROUP *ARE USED TO IDENTIFY GENERIC NAMES

1-30

** ** ** **

******************************************************************* GROUP(1) PSB(A*) SYMNAME(PSB1 1) GROUP(2) PSB(B*) SYMNAME(PSB2 2) GROUP(3) PSB(C*) SYMNAME(PSB3 3) GROUP(4) PSB(D*) SYMNAME(PSB4 4) GROUP(5) PSB(E*) SYMNAME(PSB5 5) GROUP(6) PSB(F*) SYMNAME(PSB6 6) GROUP(7) PSB(G*) SYMNAME(PSB7 7) GROUP(8) PSB(H*) SYMNAME(PSB8 8) GROUP(9) PSB(I*) SYMNAME(PSB9 9) GROUP(10) PSB(J*) SYMNAME(PSB10 10)

Data collection groups

The information collected by the bottleneck collector is organized by PSB groups. This allows you to target service-level analysis to a set of similar applications so that your tuning efforts can be focused on the specific bottlenecks that impact your system. You can define up to 30 different groups.

The GROUP keyword defines PSB groups. If you do not define any groups, EPILOG uses a default of 10 groups (groups 110) shown above.

The PSB names must be in parentheses and separated by spaces, commas, or both. You can specify up to 255 entries between the set of parentheses. For example, the following command groups four different PSBs:

GROUP(1) PSB (PSB1,PAYROLL EMPLOY,SALES)

PSB names can use from 18 alphanumeric characters (including three special characters: #, $, and @). A name can start with any character allowed in the name. Only PSBs that are actually defined to IMS can be defined in groups.

Collector Operation

47

Document info
Document views1354
Page views1354
Page last viewedWed Jan 18 06:24:15 UTC 2017
Pages236
Paragraphs8116
Words69808

Comments