Chapter 5. Using Application Monitor 205
5.4.3 Data Set Analysis reports
Data Set Analysis reports list the data sets used in when running the application. They also
show data set attributes, access method used, and any EXCPs that were encountered. This
can be used to work with your system programmer to tune I/O. It may be useful when
determining if you wish to cache a file.
5.4.4 CICS reports
There are several CICS specific reports. Application Monitor allows you to analyze a whole
CICS region, but allows you to view the information in many different ways:
򐂰 At the module level.
򐂰 At the transaction level.
򐂰 Instance specific information for every instance of the transaction run during the analysis
򐂰 EXEC CICS instructions and the time spent processing them (from a transaction or an
instance perspective).
With the V2R1 version of Application Monitor, these reports are now all available during
historical analysis as well as live analysis.
5.4.5 DB2 reports
Application Monitor supports many different reports for DB2 applications. These reports are
available if you have requested that DB2 information be collected (on the default page or on
option 2 or 3). These reports are too detailed to do justice to in this small paragraph. For
complete information, please see the IBM Application Monitor for z/OS V2R1 Users Guide,
5.4.6 IMS reports
Like the CICS and DB2 case, using Application Monitor with IMS is very similar to using it to
monitor a normal batch transaction. There are IMS specific reports available on:
򐂰 IMS Messages Processed by Region
򐂰 IMS Message Analysis
򐂰 IMS Call Analysis
򐂰 IMS Segment Search Criteria Analysis
5.5 Things to remember when using Application Monitor
Please keep the following information in mind:
1. All pale blue fields in Application Monitor are selectable, or editable.
If the pale blue field has a line below it, then it will accept data and allow you to change
its value.
If the pale blue field does not have a line under it, the pale blue color indicates that
more specific information is available on this item. You can place the cursor on this
field and press the Enter key. This action will “drill down” and provide more specific
information about the item that was selected.
206 Using IBM Application Development Tools for z/OS and OS/390
2. The Defaults option is used to set the defaults for option 1 (Analyze an active program).
Other Primary options will present their own version of certain fields (like Max Samples
and Max Durations, history file name). These fields should always be verified to ensure
they meet your requirements.
If a panel contains a field with the same name as something on a Defaults panel, the value
given on the local panel will be used.
3. The data can always be re-analyzed later with the history file (even under CICS) and the
History file option allows you to view your analysis data in three different ways. This can
help you get more out of the data. We recommend that the majority of the analysis be
done through option 5 (Analyze Historical Data).
4. To effectively use the Analyze Historical Data option, you may wish to carefully use the
default option (or other options) to specify a memorable history file name. Alternatively,
you can keep a directory of matching history file names to content.
5. The fields containing asterisks at the top of the columns of the Select an Active Job to
Analyze panel can be used to suppress the display of some types of jobs (for example,
only show batch jobs).
6. A listing data set can be added at any time. The name of the listing data set is not stored in
the history file. Listings are always searched for in the data sets specified under 6.2. So
you may use a listing data set to get more value from analyzing a history file, regardless of
whether you used one during the original analysis and history file capture.

Get Using IBM Application Development Tools for z/OS and OS/390 now with O’Reilly online learning.

O’Reilly members experience live online training, plus books, videos, and digital content from 200+ publishers.