Application Performance Analyzer handles source program mapping differently for Java than for other programming languages.
If the source is not loaded, your A04: Source Mapping Dataset List is searched for the source member. If no source member is found in any of the data sets, the common list as defined in A05: Source Mapping Common List is searched. If no source member is found in any of the data sets in the list, the A01: Source Program Mapping panel is displayed, allowing you to enter the source mapping information for the current observation session.
When one or more source members are found in your A04: Source Mapping Dataset List or the A05: Source Mapping Common List, the behavior of Application Performance Analyzer depends on whether or not you requested to match the compile date and time. When you request to not match the compile date and time, the first instance of a source member is loaded regardless of its date and time and the source is displayed in the P01: Source Program Attribution report.
When you request to match the compile date and time, the first source member found that matches the load module compile date and time is loaded and the source is displayed in the P01: Source Program Attribution report.
If none of the source members match the compile date and time, a pick list of datasets that contain the source member is displayed in the A011: Source Programming Mapping Pick List panel. When you select one of these source members, it is loaded and you are returned to the report from which you entered the ‘P' line command. You must then re-enter the ‘P' line command to display in the P01: Source Program Attribution report.
Typically, source mapping for C/C++ programs is dependent on an exact match between the listing timestamp and the CSECT timestamp generated at compile time. A recompiled C/C++ source listing cannot be loaded directly from the A01, A04 or A11 panels. In some cases, this function is required when the source listing that matches the compiled program is not available. To accommodate this situation, Application Performance Analyzer will allow a listing to be loaded for a specific CSECT with no timestamp matching. You must enter the ‘P' line command on a CSECT in one of the supporting reports. You are then directed to the A01: Source Program Mapping panel where you specify the listing to be loaded. This listing will then be loaded and related to the CSECT selected, without timestamp checking, and you are returned to the report. You must then re-enter the ‘P' line command to display the P01: Source Program Attribution report.
You can also go directly to the P03 USS Source Program Attribution report (without going through the P04 report), by using the "P" line command on an object code address report line in the C03 report, or an attribution offset line in the W03 report.
The absolute pathname to the debug file is contained within the CSECT for the compiled program. APA is able to extract this file name from the executable USS file during sampling. Hence you do not need to identify the debug file via the A01 panel for source mapping. However, APA can only extract information from the executable USS file if it can locate it during sampling. If the program is executed using a relative path name, then you will have to specify the directory in which it can be found. You do this in the Options panel (panel 2) when you create the request.
[ Top of Page | Previous Page | Next Page | Contents | Index ]