Using IBM Application Development Tools for z/OS and OS/390

204 Using IBM Application Development Tools for z/OS and OS/390

5.3.4 Analyzing historical data

One of the nicest things about Application Monitor is that it allows you to create history files

(even in the CICS subsystems) that keep the raw data the analysis was done from. This

means that an Application Monitor can go back after the actual run and re-analyze the data

from a different perspective (perhaps only looking at a portion of the time, or at how the

application performance profile changed over time).

All reports that are available during active analysis are available when analyzing historical

data with primary option 4. This option also has the ability to do interval analysis, which allows

you to narrow the time frame that you are looking at, or look at equal segments of time across

a given run. All of the reports that were available for the whole time period will also be

available for each interval (if sufficient data exists).

Finally, if a listing data set for a COBOL or PL/I application was not available during live

analysis, it can still be used during historical analysis. This will allow Source Statement level

analysis to be done on the history files.

5.3.5 Named sets: what they are and why they can help

Problem: You want to monitor a job in a sysplex or a CICS Multi-Region environment, but

you do not know which system/region it will run on.

Solution: Named Sets.

One of the new features that is provided with Application Monitor V2R1 is Named Sets.

Named Sets allow you to name a group of subsystems in your sysplex, or transactions or

regions under CICS (if you are running the CICS Multi-Region Option) and use that to monitor

a job that could be executed on any of the systems.

Option 3 was created to allow users to analyze a job that could occur on any of the systems

or regions in a given named set.

Named sets are created using option 7 (Administration option).

For more information on Named Sets, refer to the IBM Application Monitor for z/OS V2R1

Users Guide, SC18-9084-00.

5.4 Some available reports

Application Monitor provides many possible reports. This section just gives you a quick run

down of some of them.

5.4.1 Program reports

Program reports allow you to determine the percentage of time spent in a given module,

CSECT, source line statement, or assembler instruction.

5.4.2 Delay Analysis reports

Delay Analysis reports attempt to show where any waits in the application occur. This is

sometimes quite useful and we recommend that it be tried with your application to see if it is

helpful. Note that in some cases the delays are in system modules that it may be hard to

connect to a specific portion of an application.