Use this panel to specify information about the measurement of
a CICS® region, IMS selection
parameters, specific DB2® stored procedures or user-defined
functions, or DDF filtering criteria. CICS, IMS, DB2 and DDF information
are all mutually exclusive. The available fields
on panel 5 differ when a dash (-) is entered in the Jobname field
in panel 1. In this case, Application Performance Analyzer displays fields on this panel
that are specific to DB2 stored procedures and user-defined functions,
and IMS transactions that execute across multiple IMS regions.
For CICS, you can specify the CICS tran codes and
terminals for which CICS measurement information is to be recorded.
Limiting the CICS transactions and terminals you are interested in
can have a significant impact on the resources consumed by the measurement
process.
For IMS, when you are measuring one MPP or IFP region, you can specify a transaction,
program name, and user ID to limit the measurement information. When
you are measuring an IMS transaction that executes across
multiple MPP regions, you specify the IMS subsystem
name or IMSPlex group name, and the IMS transaction name.
For specific DB2 stored
procedures or user-defined functions, you specify the DB2 susbsystem
name, either a P or F, the schema name and the stored procedure or
user-defined function name.
For DDF measurements, you may filter the measurements
by specifying the Correlation Id, End User Id and/or Workstation Id
you are interested in.
A sample panel 5 for CICS, an IMS region and DDF is
shown here:
File View Navigate Help
--------------------------------------------------------------------------------
R03: Schedule New Measurement Row 00001 of 00025
Command ===> __________________________________________________ Scroll ===> CSR
o 1. Job Information 3. Multi Steps 5. Subsystems 7. Schedule
2. Options 4. Active Jobs 6. Sysplex 8. Sched Options
________________________________________________________________________________
Panel 5. Subsystems Measurement Criteria
Specify up to 16 CICS trancodes for which measurement data is to be
recorded.
01 *___ 02 ____ 03 ____ 04 ____ 05 ____ 06 ____ 07 ____ 08 ____
09 ____ 10 ____ 11 ____ 12 ____ 13 ____ 14 ____ 15 ____ 16 ____
Include CICS system transaction in measurement(Y/N): N
Wildcard character *'' can be specified at the end of a partial name.
*'' by itself specifies all transactions of terminals.
Specify up to 8 CICS terminal IDs for which measurement data is to be recorded.
01 *___ 02 ____ 03 ____ 04 ____ 05 ____ 06 ____ 07 ____ 08 ____
Include CICS non-terminal transactions in measurement(Y/N): Y
Enter IMS/TM selection parameters:
Transaction ________ Program Name ________ User ID ________
Specify filter criteria for DDF observation. Wildcards are accepted.
Correlation Id _____________ or _ '/' for null (binary zero)
End User Id ___________________ or _ '/' for null (binary zero)
Workstation Id ____________________ or _ '/' for null (binary zero)
A sample panel 5 where you can enter information about
a specific DB2 stored procedure or an IMS transaction
and IMS subsystem or IMSPlex group is shown here. This
panel is displayed only when a dash (-) is entered in the Job Name/Pattern
field in Panel 1.
File View Navigate Help
--------------------------------------------------------------------------------
R03: Schedule New Measurement Row 00001 of 00010
Command ===> __________________________________________________ Scroll ===> CSR
o 1. Job Information 3. Multi Steps 5. Subsystems 7. Schedule
2. Options 4. Active Jobs 6. Sysplex 8. Sched Options
________________________________________________________________________________
Panel 5. Subsystems Measurement Criteria
Enter DB2 stored procedure or user-defined function parameters:
DB2 Subsystem ______ Specify P for procedure or F for function _
Schema ________________________________________________________________________
Name ________________________________________________________________________
Enter IMS/TM selection parameters:
IMS Subsystem Id ____ or IMSPLEX Group Name ________
Transaction __________
Panel 5 input fields
- CICS Trancode
- Specify a CICS transaction name or pattern.
This identifies CICS transactions to be included in
the measurement. You can also specify a partial name terminated by
an asterisk (*) to indicate a wildcard pattern. You can specify up
to 16 names/patterns. Specify an asterisk (*) by itself to measure
all transactions.
- Include CICS System Txns
- Specify Y or N to indicate if the measurement is to include
data on CICS system transactions. (Normally set to No).
- CICS Terminal ID
- Specify a CICS terminal ID name or pattern.
This identifies CICS terminals to be included in the
measurement. You can also specify a partial name terminated by an
asterisk (*) to indicate a wildcard pattern. You can specify up to
eight names/patterns. Specify an asterisk (*) by itself to measure
all terminals.
- Include CICS non-terminal
transaction
- Specify Y or N to indicate if the measurement is to include
data on CICS non-terminal transactions.
- IMS Transaction
- Specify an IMS transaction id or pattern. This
identifies IMS transactions to be included in the measurement
when measuring an IMS/MPP
or IMS/IFP region. You can also specify a partial name terminated
by an asterisk (*) to indicate a wildcard pattern.
Any values in
Transaction Id, Program Name and User ID are ANDed together to determine
if a transaction should be included in the measurement.
- IMS Program
- Specify an IMS program name or pattern. This
identifies IMS programs to be included in the measurement
when measuring an IMS/MPP
or IMS/IFP region. You can also specify a partial name terminated
by an asterisk (*) to indicate a wildcard pattern.
Any values in
Transaction Id, Program Name and User ID are ANDed together to determine
if a transaction should be included in the measurement.
- IMS User
ID
- Specify a userid or pattern. This identifies that transactions
initiated by the userid are to be included in the measurement when
measuring an IMS/MPP
or IMS/IFP region. You can also specify a partial name terminated
by an asterisk (*) to indicate a wildcard pattern. Any values in
Transaction Id, Program Name and User ID are ANDed together to determine
if a transaction should be included in the measurement.
Note:
When
limiting the observation to specific IMS transactions, programs or
users in an MPP or IFP region, Application Performance Analyzer samples
only when the transactions are running. The observation continues
to run for the requested duration.
- Correlation Id
- Specify a DB2 correlation id or pattern. This identifies a DB2
correlation id to be included in the measurement when measuring a
DDF address space. A correlation id of null (binary zero) may be specified
by entering a '/' in the selection field next to the Correlation Id
field. You may also specify a wildcard pattern using an asterisk (*)
or a percent sign (%). An asterisk is used to indicate one or more
characters that can appear in place of the asterisk. It can be used
as a prefix or a suffix, or both. Alternatively, a percent sign is
used to indicate any single character, and can appear any number of
times. Any values in Correlation Id, End User Id, and Workstation
Id are ANDed together to determine if an SQL request is included in
the measurement.
- End User Id
- Specify an end user id or pattern. This identifies an end user
id to be included in the measurement when measuring a DDF address
space. An end user id of null (binary zero) may be specified by entering
a '/' in the selection field next to the End User Id field. You may
also specify a wildcard pattern using an asterisk (*) or a percent
sign (%). An asterisk is used to indicate one or more characters that
can appear in place of the asterisk. It can be used as a prefix or
a suffix, or both. Alternatively, a percent sign is used to indicate
any single character, and can appear any number of times. Any values
in Correlation Id, End User Id, and Workstation Id are ANDed together
to determine if an SQL request should be included in the measurement.
- Workstation Id
- Specify a workstation id or pattern. This identifies a workstation
id to be included in the measurement when measuring a DDF address
space. A workstation id of null (binary zero) may be specified by
entering a '/' in the selection field next to the Workstation Id field.
You may also specify a wildcard pattern using an asterisk (*) or a
percent sign (%). An asterisk is used to indicate one or more characters
that can appear in place of the asterisk. It can be used as a prefix
or a suffix, or both. Alternatively, a percent sign is used to indicate
any single character, and can appear any number of times. Any values
in Correlation Id, End User Id, and Workstation Id are ANDed together
to determine if an SQL request should be included in the measurement.
- DB2 Subsystem
- This field is displayed only when a dash (-) is entered in
the Job Name/Pattern field in Panel 1. Specify a DB2 subsystem.
This identifies the DB2 subsystem that will be used to
run the stored procedure or user-defined function.
- Specify procedure or function
- This field is displayed only when a dash (-) is entered in
the Job Name/Pattern field in Panel 1. Identify this request as a
stored procedure or user-defined function. Enter P for stored procedure
or F for a user-defined function.
- Schema
- This field is displayed only when a dash (-) is entered in
the Job Name/Pattern field in Panel 1. Specify the schema name for
this stored procedure or user-defined function. You can specify a
schema name pattern; for example, a schema name prefix followed by
an asterisk (*) or an asterisk by itself. Application Performance Analyzer will measure
the first DB2 stored procedure or user-defined function executed
by the DB2 subsystem that matches that schema name pattern
and name concatenation. If a single asterisk is coded in both schema
and name, Application Performance Analyzer will measure the first stored procedure
or user-defined function executed by the DB2 subsystem.
- Name
- This field is displayed only when a dash (-) is entered in the
Job Name/Pattern field in panel 1. Specify the name of the stored
procedure or user-defined function. You can specify a name pattern;
for example, a name prefix followed by an asterisk (*) or an asterisk
by itself. Application Performance Analyzer will measure the first DB2 stored
procedure or user-defined function executed by the DB2 subsystem
that matches that schema name and name pattern concatenation. If a
single asterisk is coded in both schema and name, Application Performance Analyzer will
measure the first stored procedure or user-defined function executed
by the DB2 subsystem.
- IMS Subsystem Id
- This field is displayed only when a dash (-) is entered in the
Job Name/Pattern field in panel 1 to indicate an IMS MASS
request. Specify an IMS subsystem. This identifies the IMS subsystem
in which the IMS transaction you are measuring runs.
- IMSPLEX Group Name
- This field is displayed only when a dash (-) is entered in the
Job Name/Pattern field in panel 1 to indicate an IMS MASS
request. Specify the IMSPlex XCF group name. This identifies the IMSPlex
where the IMS transaction will run. Either the CSL group
name, which is defined by the IMSPLEX parameter in the DFSCGxxx member
of the IMS proclib, prefixed by the characters "CSL",
or the IMS Shared Queues group name, which is defined
by the SQGROUP parameter in the DFSSQxxx member of the IMS proclib,
can be specified. These parameters can also be found in the DFSDFxxx
member of the IMS proclib. IMS Subsystem
ID and IMSPLEX Group Name are mutually exclusive.
- Transaction
- This field is displayed only when a dash (-) is entered in the
Job Name/Pattern field in panel 1 to indicate an IMS MASS
request. Specify an IMS transaction code. This identifies
the IMS transaction to be included in the measurement.
All active MPP regions that are eligible to process the transaction
code on the specified IMS subsystem are returned on panel
4.
[ Top of Page | Previous Page | Next Page | Contents | Index ]