Editing a KIPGLB member
KIPGLB members in the RKIPGLBL DD data set are source members that contain global monitoring options for OMEGAMON® for IMS. KIPGLB members contain a series of statements that define groups and group items that you want to monitor. They also control default Bottleneck Analysis options and Response Time Analysis (RTA) options.
Although users can dynamically update some of the global values, those values are lost when OMEGAMON for IMS is recycled, the KIPGLB member is reloaded, or another KIPGLB member is loaded. You can
make the changes permanent by editing the KIPGLB member that the OMEGAMON for IMS
task uses or edit another KIPGLB source member to use for testing, for example. Save the changes,
then run KIPGLBVR to verify the contents. When you are ready to implement the changes, you do not
have to stop OMEGAMON for IMS to apply them. You can run the GLBL
command to load the
KIPGLB member, and your changes automatically go into effect. If you implement your changes in
another KIPGLB member and want that member's default global settings to automatically be loaded when
you start OMEGAMON for IMS, make sure that you update GLOBAL=xx in the
PARM setting of the startup procedure to specify the new suffix.
KIPGLB syntax
<
>
characters.- <GROUPS>
- In the
<GROUPS>
section, you specify parameters that control groups, including the maximum number of groups that are allowed. You also define each group, including its name, number, and response time options. Each group is defined in its own subsection, which is identified by the<<GROUP>>
heading. See <GROUPS> for a list of the parameters. - <GROUP_ELEMENTS>
- In the
<GROUP_ELEMENTS>
section, you specify each transaction, PSB, class, and logical terminal to be monitored and which group or groups that each item is in. You can also include item-specific response time options. Each item is defined in its own subsection, which is identified by the<<ID>>
heading. See <GROUP_ELEMENTS> for a list of the parameters.Note: A group can contain transactions, PSBs, and classes, or it can contain logical terminals (LTERMs). - <BOTTLENECK_ANALYSIS>
- In the
<BOTTLENECK_ANALYSIS>
section, you specify options that pertain to data collection for the Bottleneck Analysis component and other Bottleneck Analysis options. See <BOTTLENECK_ANALYSIS> for a list of the parameters. - <RESPONSE_TIME_COLLECTION>
- In the
<RESPONSE_TIME_COLLECTION>
section, you specify options that control Response Time Analysis features such as the time slots during which you monitor response times for time slot analysis. See <RESPONSE_TIME_COLLECTION> for a list of the parameters.
<GROUPS>
<GROUPS>
section. The definitions
for each group begin with a <<GROUP>>
heading.- MAXIMUM_GROUPS=nn
- Specify the maximum number of groups, where nn is
1 - 30. You can dynamically override this value by using the
MAXG
immediate command. - MAXIMUM_IDS=nnnn
- Specify the maximum number of PSB, transaction, and class items to monitor, where nnnn is 1 - 1000.
- MAXIMUM_TERMINALS=nnnn
- Specify the maximum number of logical terminals (LTERMs) to monitor, where nnnn is 1 - 1000.
- UNITS=MILLIS | SECONDS
- Specify the precision for moving time slot analysis (GRSP) displays and the ARSP exception. Use MILLIS for millisecond precision.
- <<GROUP>>
- Specify the start of the definitions for a group. Under each
<<GROUP>>
heading, you have the following parameters.- NAME=(xxxxxxxx | SYSTEM | OTHER)
- Specify the 1 - 8 character name of the group. The name can include
blanks. SYSTEM and OTHER are special RTA monitoring groups. SYSTEM
is a composite of response times for all transactions. OTHER is a
composite of response times for transactions that are not monitored
within any specific group. Do not specify
NUMBER
when you specify SYSTEM or OTHER. - NUMBER=nn
- Specify the number of the group, where nn is
1 - 30. The value for nn cannot exceed
MAXIMUM_GROUPS
. Do not specifyNUMBER
if theNAME
is SYSTEM or OTHER. - RESPONSE_TIME_THRESHOLD=(nnnn,ALL | nnnn,nnnn,nnnn,nnnn,nnnn,nnnn,nnnn,nnnn,nnnn)
- Specify the response time thresholds in tenths of a second or
in milliseconds (based on UNITS) for RTA moving time slot analysis
(
GRSP
), where nnnn is 0 - 9999. A group displays dynamically on the moving time slot analysis (GRSP
) graph when it exceeds the response time threshold. A value of 0 means that the group is not eligible for dynamic display. Use the(nnnn,ALL)
format to assign the same threshold to every type of response time for the group, or you can specify a different threshold for each type of response time component, which are specified in this order.- Input queue time
- Program input queue time
- Processing time
- Output queue time
- Response time 0
- Response time 1
- Not used
- Not used
- Local output time
You can dynamically override the values by using the
ISET
immediate command. If you do not specify theRESPONSE_TIME_THRESHOLD
parameter, the default thresholds are 0. - FIX=(YES,ALL | NO,ALL)
- FIX=(YES|NO,YES|NO,YES|NO,YES|NO,YES|NO,YES|NO,YES|NO,YES|NO,YES|NO)
- Specify whether the group always displays (YES) or dynamically
displays (NO) on the RTA moving time slot analysis (
GRSP
) graph. A group displays dynamically on the graph when it exceeds the response time threshold. A value of 0 means that the group is not eligible for dynamic display. Use the(ccc,ALL)
format to assign the same value to every type of response time for the group, or you can specify a different value for each type of response time component, which are specified in this order.- Input queue time
- Program input queue time
- Processing time
- Output queue time
- Response time 0
- Response time 1
- Not used
- Not used
- Local output time
You can dynamically override the values by using the
ISET
immediate command. If you do not specify theFIX
parameter, the defaults are NO. - EXCEPTION_THRESHOLD=(nnnn,ALL | nnnn,nnnn,nnnn,nnnn,nnnn,nnnn,nnnn,nnnn,nnnn)
- Specify the critical exception thresholds in tenths of a second
or in milliseconds (based on UNITS) for average response time (ARSP)
exception analysis, where nnnn is 0 - 9999. ARSP
exception analysis displays a warning message when the average response
time for the group exceeds the threshold. A value of 0 means that
the group is not eligible for ARSP exception analysis. Use the
(nnnn,ALL)
format to assign the same exception threshold to every type of response time for the group, or you can specify a different exception threshold for each type of response time component, which are specified in this order.- Input queue time
- Program input queue time
- Processing time
- Output queue time
- Response time 0
- Response time 1
- Not used
- Not used
- Local output time
You can dynamically override the values by using the
ISET
immediate command. If you do not specify theEXCEPTION_THRESHOLD
parameter, the default exception thresholds are 0.
<GROUP_ELEMENTS>
<GROUP_ELEMENTS>
section.
The definitions for each item begin with a <<ID>>
heading.
Typically, items are monitored within context of the group or groups
in which they are contained. However, if you want to monitor specific
items in the RTA moving time slot analysis (GRSP
)
graph, set RESPONSE_TIME_THRESHOLD
and FIX
.
For ARSP exception analysis, set EXCEPTION_THRESHOLD
.
The settings for a group item affect the item in all groups that contain
it.- <<ID>>
- Specify the start of the definitions for an item. The items are
the transactions, PSBs, classes, and logical terminals that you want
to monitor. Under each
<<ID>>
heading, you have the following parameters.- item=xxxxxxxx
- Specify the item. The item can be a transaction, PSB, class, or
logical terminal (LTERM). Use one of the following formats to identify
the item.
- TRAN=xxxxxxxx
- Specify the 1 - 8 character name of the transaction. You can use
the asterisk (*) as a wildcard in positions in the name or at the
end of the name. For example,
TRAN=ADD*
includes all transactions that begin withADD
in the specified group or groups. - PSB=xxxxxxxx
- Specify the 1 - 8 character name of the PSB. You can use the asterisk
(*) as a wildcard in positions in the name or at the end of the name.
For example,
PSB=AB*CD*
includes all PSBs that begin withAB
and containCD
in the fourth and fifth positions of the name. - CLASS=nnn
- Specify the number of the class, where nnn is 1 - 255.
- TERM=xxxxxxxx
- Specify the 1 - 8 character name of the logical terminal. You can use the asterisk (*) as a wildcard in positions in the name or at the end of the name.
- ELIGIBLE_GROUPS=(nn,nn,...,nn)
- Specify the number of the group that includes the item, where nn is
1 - 30. If more than one group contains the item, separate the group
numbers with a comma (
,
).Note: A group can contain transactions, PSBs, and classes, or it can contain logical terminals (LTERMs). - RESPONSE_TIME_THRESHOLD=(nnnn,ALL | nnnn,nnnn,nnnn,nnnn,nnnn,nnnn,nnnn,nnnn,nnnn)
- Specify the response time thresholds in tenths of a second or
in milliseconds (based on UNITS) for RTA moving time slot analysis
(
GRSP
), where nnnn is 0 - 9999. A group item displays dynamically on the moving time slot analysis (GRSP
) graph when it exceeds the response time threshold. A value of 0 means that the group item is not eligible for dynamic display. Use the(nnnn,ALL)
format to assign the same threshold to every type of response time for the group item, or you can specify a different threshold for each type of response time component, which are specified in this order.- Input queue time
- Program input queue time
- Processing time
- Output queue time
- Response time 0
- Response time 1
- Not used
- Not used
- Local output time
You can dynamically override the values by using the
ISET
immediate command. If you do not specify theRESPONSE_TIME_THRESHOLD
parameter, the default thresholds are 0. - FIX=(YES,ALL | NO,ALL)
- FIX=(YES|NO,YES|NO,YES|NO,YES|NO,YES|NO,YES|NO,YES|NO,YES|NO,YES|NO)
- Specify whether the group item always displays (YES) or dynamically
displays (NO) on the RTA moving time slot analysis (
GRSP
) graph. A group item displays dynamically on the graph when it exceeds the response time threshold. A value of 0 means that the group item is not eligible for dynamic display. Use the(ccc,ALL)
format to assign the same value to every type of response time for the group item, or you can specify a different value for each type of response time component, which are specified in this order.- Input queue time
- Program input queue time
- Processing time
- Output queue time
- Response time 0
- Response time 1
- Not used
- Not used
- Local output time
You can dynamically override the values by using the
ISET
immediate command. If you do not specify theFIX
parameter, the defaults are NO. - EXCEPTION_THRESHOLD=(nnnn,ALL | nnnn,nnnn,nnnn,nnnn,nnnn,nnnn,nnnn,nnnn,nnnn)
- Specify the critical exception thresholds in tenths of a second
or in milliseconds (based on UNITS) for average response time (ARSP)
exception analysis, where nnnn is 0 - 9999. ARSP
exception analysis displays a warning message when the average response
time for the group item exceeds the threshold. A value of 0 means
that the group item is not eligible for ARSP exception analysis. Use
the
(nnnn,ALL)
format to assign the same exception threshold to every type of response time for the group item, or you can specify a different exception threshold for each type of response time component, which are specified in this order.- Input queue time
- Program input queue time
- Processing time
- Output queue time
- Response time 0
- Response time 1
- Not used
- Not used
- Local output time
You can dynamically override the values by using the
ISET
immediate command. If you do not specify theEXCEPTION_THRESHOLD
parameter, the default exception thresholds are 0.
<BOTTLENECK_ANALYSIS>
<BOTTLENECK_ANALYSIS>
section.- SHORT_TERM_BUCKET_MINUTES=nn
- Specify the interval at which the short-term buckets are cleared,
where nn is 0 - 99. You can dynamically override
the value by using the
CLRS
minor command ofIDEG
. The default is 5. - LONG_TERM_BUCKET_MINUTES=nnn
- Specify the interval at which the long-term buckets are cleared,
where nnn is 0 - 480. You can dynamically override
the value by using the
CLRL
minor command ofIDEG
. The default is 30. - SCALING_FACTOR=nnn
- Specify the scaling factor for the MDEX display, where nnn is
1 - 100. You can dynamically override the value by using the
SCAL
minor command ofIDEG
. The default is 1. - SAMPLE_TIME_INTERVAL=nn
- Specify the frequency of data collection in tenths of a second,
where nn is 1 - 99. You can dynamically override
the value by using the
STIM
minor command ofIDEG
. The default is 5. - MINIMUM_PERCENT_THRESHOLD=nn
- Specify the minimum percent threshold for the PDEX display, where nn is
0 - 99. Any Bottleneck Analysis execution state whose short-term and
long-term percent values fall below the threshold is not shown on
the PDEX display. You can dynamically override the value by using
the
THRS
minor command ofIDEG
. The default is 0. - MINIMUM_COUNT_THRESHOLD=nnnn
- Specify the minimum count threshold in tenths for the MDEX display,
where nnnn is 0 - 9999. Any Bottleneck Analysis
execution state whose short-term and long-term average transaction
count values fall below the threshold is not shown on the MDEX display.
You can dynamically override the value by using the
MTHR
minor command ofIDEG
. The default is 0. - EXCLUDE_MESSAGE_DRIVEN_BMPS=OFF | ON
- Specify whether Bottleneck Analysis should ignore message-driven
BMP transactions. Use ON to exclude message-driven BMP transactions.
You can dynamically override the value by using the
BMPX
minor command ofIDEG
. The default is OFF. - EXCLUDE_NON_MESSAGE_DRIVEN_BMPS=OFF | ON
- Specify whether Bottleneck Analysis should ignore non-message
driven BMP transactions. Use ON, the default, to exclude non-message
driven BMP transactions. You can dynamically override the value by
using the
NMSX
minor command ofIDEG
. - DISPLAY_OPTIONS=COMPETING | EXECUTING | ALL | TOTAL
- Specify whether Bottleneck Analysis should display information
about transactions that are competing or executing. Use ALL or TOTAL
for all transactions, including non-competing ones. You can dynamically
override the value by using the
DOPT
minor command ofIDEG
. The default is COMPETING. - DB_IO_BY_DATABASE=OFF | ON
- Specify whether Bottleneck Analysis should record I/O activity
by database name. You can dynamically override the value by using
the
DBSW
minor command ofIDEG
. The default is ON.
<RESPONSE_TIME_COLLECTION>
<RESPONSE_TIME_COLLECTION>
section.- TIME_INTERVALS=(nnn,nnn,nnn)
- Specify the first, second, and third short-term intervals that
are analyzed by RTA time interval analysis (
IRSP
) in minutes, where nnn is 0 - 999. The second argument must be a multiple of the first, and the third argument must be a multiple of the second, for example, (15,30,60). You can dynamically override the value by using theICTL
immediate command. - SCALE=(nnn,ALL | nnn,nnn,nnn,nnn,nnn,nnn,nnn,nnn,nnn)
- Specify the scale, in seconds or millisecond based on UNITS, for
the vertical axis on the RTA moving time slot analysis (
GRSP
) graph, where nnn is 1 - 999. The RTA component divides the vertical axis into 10 points, each 1/10 of the scale height. Use the(nnn,ALL)
format to assign the same value to every type of response time or you can specify a different value for each type of response time component which are specified in this order.- Input queue time
- Program input queue time
- Processing time
- Output queue time
- Response time 0
- Response time 1
- Not used
- Not used
- Local output time
You can dynamically override the values by using the
ISET SCALE
immediate command. The default is 2 for all response time components. - WINDOW=nn
- Specify the number of one-minutes periods that are analyzed by
RTA moving time slot analysis (
GRSP
), where nn is 1 - 10. Moving time slot analysis reviews each of the last nn minutes to determine transactions that exceed a response time threshold. You can dynamically override the value by using theISET WINDOW
immediate command. The default is 10. - TIME_SLOT=(nnnn,nnnn)
- Specify the beginning and ending time of a time period that is
analyzed by RTA time slot analysis (
SRSP
), where nnnn is specified by using the 24-hour clock, 0000 - 2400. You can specify a maximum of 48 time slots, where each time slot is represented by aTIME_SLOT
parameter, as shown in the following example.TIME_SLOT=(1100,1130) TIME_SLOT=(1130,1200) TIME_SLOT=(1200,1300) TIME_SLOT=(1300,1400)
KIPGLB example
The following example illustrates the contents of a KIPGLB global definitions member.
*
* GLOBAL KIPGLBXX
*
<GROUPS>
MAXIMUM_GROUPS=10
MAXIMUM_IDS=25
MAXIMUM_TERMINALS=25
UNITS=MILLIS
*
<<GROUP>>
NAME=(SYSTEM)
RESPONSE_TIME_THRESHOLD=(3,ALL)
FIX=(YES,ALL)
*
<<GROUP>>
NAME=(OTHER)
RESPONSE_TIME_THRESHOLD=(3,ALL)
FIX=(YES,ALL)
*
<<GROUP>>
NAME=(CLASS 1 )
NUMBER=1
RESPONSE_TIME_THRESHOLD=(1,ALL)
EXCEPTION_THRESHOLD=(5,ALL)
FIX=(YES,ALL)
*
<<GROUP>>
NAME=(CLASS2 )
NUMBER=2
RESPONSE_TIME_THRESHOLD=(2,ALL)
*
<<GROUP>>
NAME=(GROUP 03)
NUMBER=3
RESPONSE_TIME_THRESHOLD=(3,ALL)
*
<<GROUP>>
NAME=(GROUP 04)
NUMBER=4
RESPONSE_TIME_THRESHOLD=(4,ALL)
*
*
<GROUP_ELEMENTS>
*
<<ID>>
CLASS=1
ELIGIBLE_GROUPS=(01)
*
<<ID>>
CLASS=2
ELIGIBLE_GROUPS=(02)
*
<<ID>>
CLASS=3
ELIGIBLE_GROUPS=(03)
*
<<ID>>
CLASS=4
ELIGIBLE_GROUPS=(04)
*
*
<BOTTLENECK_ANALYSIS>
SHORT_TERM_BUCKETS_MINUTES=5
LONG_TERM_BUCKETS_MINUTES=30
SCALING_FACTOR=1
SAMPLE_TIME_INTERVAL=5
MINIMUM_PERCENT_THRESHOLD=0
MINIMUM_COUNT_THRESHOLD=0
EXCLUDE_MESSAGE_DRIVEN_BMPS=OFF
EXCLUDE_NON_MESSAGE_DRIVEN_BMPS=ON
DISPLAY_OPTIONS=COMPETING
*
*
<RESPONSE_TIME_COLLECTION>
TIME_INTERVALS=(15,30,60)
SCALE=(2,ALL)
TIME_SLOT=(0000,0800)
TIME_SLOT=(0800,0900)
TIME_SLOT=(0900,1000)
TIME_SLOT=(1000,1030)
TIME_SLOT=(1030,1100)
TIME_SLOT=(1100,1130)
TIME_SLOT=(1130,1200)
TIME_SLOT=(1200,1300)
TIME_SLOT=(1300,1400)
TIME_SLOT=(1400,1430)
TIME_SLOT=(1430,1500)
TIME_SLOT=(1500,1530)
TIME_SLOT=(1530,1600)
TIME_SLOT=(1600,1700)
TIME_SLOT=(1700,1800)
TIME_SLOT=(1800,1900)
TIME_SLOT=(1900,2000)
TIME_SLOT=(2000,2400)