Panel 2 is used to enter extended measurement options ("Data Extractors"), and also to specify additional load libraries or HFS directories to be searched for external symbol information.
Enter a slash "/" beside each of the data extractors required for the measurement. The data extractors are used to measure additional information about CICS®, DB2®, IMS™, Java, MQSERIES, Adabas and Natural. When the CICS or IMS data extractor is specified, further transaction information can be specified in panel 5.
Panel 2 is show here:
File View Navigate Help -------------------------------------------------------------------------------- R03: Schedule New Measurement Row 00001 of 00027 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 2. Measurement Options Data Extractors. /''to select extended measurement options: CICS CICS information CICS+ CICS service/CPU time DB2 SQL call information DB2+ SQL service/CPU time/counts CDB2 Collateral DB2 activity DB2V SQL Variables IMS DLI call information IMS+ DLI service/CPU time/counts Java Java information MQ MQSeries call information Ada Adabas call information Nat Natural information Specify up to 10 load libraries, or up to 440 bytes of HFS directories, to search for external symbol information. The load libraries apply only to sampled modules that are fetched from dynamically allocated load libraries. The directories apply only to sampled HFS programs that do not have absolute path names. Enter multiple directories separated by at least one space. _ Specify L for load libraries, D for directories 1 ______________________________________________ 2 ______________________________________________ 3 ______________________________________________ 4 ______________________________________________ 5 ______________________________________________ 6 ______________________________________________ 7 ______________________________________________ 8 ______________________________________________
If your installation has configured Application Performance Analyzer to display the maximum number of trace entries for DB2+ and IMS+, two additional input fields are displayed in Panel 2 as shown here:
File View Navigate Help -------------------------------------------------------------------------------- R03: Schedule New Measurement Row 00001 of 00027 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 2. Measurement Options Input more data or ENTER to submit Data Extractors. /''to select extended measurement options: _ CICS CICS information _ CICS+ CICS service/CPU time / DB2 SQL call information / DB2+ SQL service/CPU time/counts _ CDB2 Collateral DB2 activity _ DB2V SQL Variables / IMS DLI call information / IMS+ DLI service/CPU time/counts _ Java Java information _ MQ MQSeries call information _ Ada Adabas call information _ Nat Natural information 50__ DB2+ Maximum number of trace entries in thousands 60__ IMS+ Maximum number of trace entries in thousands Specify up to 10 load libraries, or up to 440 bytes of HFS directories, to search for external symbol information. The load libraries apply only to sampled modules that are fetched from dynamically allocated load libraries. The directories apply only to sampled HFS programs that do not have absolute path names. Enter multiple directories separated by at least one space. _ Specify L for load libraries, D for directories 1 ______________________________________________ 2 ______________________________________________ 3 ______________________________________________ 4 ______________________________________________ 5 ______________________________________________ 6 ______________________________________________ 7 ______________________________________________ 8 ______________________________________________ 9 ______________________________________________ 10 ______________________________________________
DB2+ and IMS+ are used to collect additional data about DB2 and IMS respectively, allowing exact call counts, service times, and CPU times to be measured and reported. DB2+ also ensures that SQL text reported is accurate, without DB2+ turned on, it is possible for the SQL text to be incorrect.
DB2V is used to turn on the DB2 variable extractor during the measurement. DB2V is a DB2 measurement option that will extract SQL variable names for sampled SQL calls. The variable names will then be substituted in place of the :H place holders when the SQL text is displayed.
CDB2 is used to turn on the collateral DB2 extractor during measurement. When the CDB2 data extractor is selected, Application Performance Analyzer measures DB2 activity in stored procedures and user-defined functions that are invoked as a result of this observation request. In the R02 Observation List, the collateral DB2 measurements are created separately and are grouped under this observation request. When CDB2 is specified, the DB2 and DB2+ options are automatically included.
The MQ data extractor provides the ability to observe/sample and report on MQSeries interface calls (both dynamic and static) in Batch, IMS and CICS application programs. This extractor is not used to measure the MQ address space itself. For more information on measuring MQ calls, refer to Overview of MQSeries data extractor.
CICS+ is used to collect additional data about CICS transactions, allowing exact transaction counts, service times and CPU times to be measured and reported. Your installer might have chosen to limit access to this data extractor.
If your installation has enabled Adabas in Application Performance Analyzer, you will see the Adabas extractor. If you select the Adabas extractor, data about Adabas calls is collected. There are no special Adabas reports. Adabas calls are reported under the ADABAS category in several reports. The C08 CPU Usage Referred Attribution report can also be used to see the Attribution offset for Adabas calls and to source map the program.
If your installation has enabled Natural in Application Performance Analyzer, you will see the Natural extractor. If you select the Natural extractor, data about Natural programs is collected and reported in the C10 CPU Usage by Natural Program.
For DB2+, enter the value (in thousands) to limit the number of DB2+ SQL call interceptions for which full details will be written to the sample file. Collecting full details on every interception allows the F02 Timeline report to report exact times for all SQL calls. The F02 report will be truncated at the number of calls specified in this field. The DB2+ data extractor continues to collect the data it requires for the other reports for the duration of the measurement. The value is entered in thousands of calls to be recorded and cannot exceed the default value specified for DB2IMaxTraceSize during Application Performance Analyzer installation. The default value is displayed in this field for NEW observation requests.
For IMS+, enter the value (in thousands) to limit the number of IMS+ DLI call interceptions for which full details will be written to the sample file. Collecting full details on every interception allows the I02 and I03 Timeline reports to report exact times for all DLI calls and IMS transactions. The I02 and I03 reports will be truncated at the number of calls specified in this field. The IMS+ data extractor continues to collect the data it requires for the other reports for the duration of the measurement. The value is entered in thousands of calls to be recorded and cannot exceed the default value specified for IMSIMaxTraceSize during Application Performance Analyzer installation. The default value is displayed in this field for NEW observation requests.
It is sometimes necessary to specify additional libraries for Application Performance Analyzer to use to resolve sampled addresses to CSECT plus offset, instead of load module plus offset.
When one program issues a LOAD or LINK macro to fetch other load modules, they are typically loaded from STEPLIB or JOBLIB or a LINKLIST library. In this case Application Performance Analyzer will find them automatically during sampling.
However, the LOAD macro can be coded to reference a DCB for which a load library was OPENed. The library might have been allocated to a temporary DDNAME and after the LOAD is done, the DCB is closed and the DDNAME released. In this situation, Application Performance Analyzer has no way of determining what load library the module came from. Hence, it is unable to get CSECT (EBE) information. This would prevent such modules from being source mapped.
[ Top of Page | Previous Page | Next Page | Contents | Index ]