Panel 5 input fields
- For a CICS® measurement:
- 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.
- For a single IMS™ region measurement:
- 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.
- For a DB2® DDF measurement:
- 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.
- For a DB2 stored procedure or user defined function 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. This field is mutually exclusive with the DB2 Group Attach Name field.
- DB2 Group Attach Name
- DB2 Group Attach Name field is displayed only when you enter a dash (-) in the Job Name/Pattern field in panel 1. If you want to identify the DB2 group that will be used to run the stored procedure or user-defined function, specify a DB2 group attach name. The DB2 Group Attach Name field is mutually exclusive with the DB2 Subsystem field.
- 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.
- For an IMS multiple region measurement:
- 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.
- For a WebSphere® measurement:
- Request name
- This field is displayed only for WAS filter criteria. It is a string of non-blank characters up to 79 bytes long. A trailing asterisk can be used as a wildcard character. Embedded asterisks are not treated as wildcards. If the field is left blank, no filtering is applied. Otherwise, only WAS requests that match the request name filter will be written to the sample file.
- Application name
- This field is displayed only for WAS filter criteria. It is a string of non-blank characters up to 79 bytes long. A trailing asterisk can be used as a wildcard. Embedded asterisks are not treated as wildcards. If the field is left blank, no filtering is applied. Otherwise, only WAS requests that invoked an application that matches the filter will be written to the sample file.
- Origin
- This field is displayed only for WAS filter criteria. It is a string of non-blank characters up to 79 bytes long. It can be an IP address, a host name, or a job name. Only WAS requests that came from the specified origin will be written to the sample file. A trailing asterisk can be used as a wildcard character. If the field is left blank, no filtering is applied.
- Origin format
- This field is displayed only for WAS filter criteria. It is required
if an origin filter is specified. Enter a slash against the type of
origin filter:
- IP address
- The filter value must be a valid IPv4 or IPv6 address. If a wildcard
is used, it can only appear after a dot separator (for IPv4) or a
colon separator (for IPv6). For example:
However, a wildcard cannot be used with an IPv6 filter if it contains two consecutive colons. For example, the following filter value is invalid:207.245.47.* 2001:db8:85a3:0:*
This is because the two consecutive colons and the asterisk wildcard both represent a varying number of missing values.2001:db8:85a3::8a2e:* - Host name
- The filter value can be from 1 to 79 non-blank characters. The characters are restricted to alpha-numeric, hyphen and underscore. A trailing asterisk can be used as a wildcard. WAS can sometimes show an IP address as a host name. To filter these, you must specify the filter value as an IP address, not a host name.
- Job name
- The filter value can be from 1 to 8 alpha-national characters. A trailing asterisk can be used as a wildcard.
- Filter out image file activity
- This field is displayed only for WAS filter criteria. It specifies
whether or not requests for image files should be filtered out. Image
files are identified by request names that end in any of the following
file extensions:
.gif .jpg .jpeg .png .ico - Filter out requests with these file extensions
- This field is displayed only for WAS filter criteria. It can be
used to specify a series of file extensions, each separated by a space.
Any requests for those file types will be filtered out. For example:
Any WAS request whose request name ends in one of the specified file extensions will be filtered out. Each file extension must begin with a period and must be followed by at least one non-blank character. Wildcards cannot be used in this filter..css .pdf .txt