Configure performance explorer

To collect detailed trace information, you need to tailor performance explorer to work optimally with the application process from which the trace is being taken.

1. Create a session definition that informs the iSeries™ server which performance data you want to collect. On the Add Performance Explorer Definition (ADDPEXDFN) display, specify the collection type and a name for the definition. This definition is stored as a database member by that name in the QAPEXDFN file in library QUSRSYS. The name that you specify is used on the Start Performance Explorer (STRPEX) command.
2. Add a filter (Add PEX Filter (ADDPEXFTR) command). A performance explorer filter identifies the performance data that is to be collected during a performance explorer session, and is meant to limit the amount of data collected by specifying a compare value for specific events.
3. Start collecting data (Start Performance Explorer (STRPEX) command). A job may be in more than one performance explorer collection if the *PMCO event is not being collected. If the *PMCO event is being collected, then a job can be in more than one collection only if all the collections have the same interval specification (ADDPEXDFN INTERVAL() parameter). You can specify a definition and optional filter on the STRPEX command.
4. Run your command, program, or workload for data that you want to analyze.
5. Stop collecting the data and save it to database files for analysis. Use the End Performance Explorer (ENDPEX) command to stop the collection.
6. Analyze the performance data. The Print Performance Explorer Report (PRTPEXRPT) command, included in the Performance Tools licensed program, provides unique reports for each type of data (statistical, profile, trace profile, or trace).
   The following are other options for analysis:

   • Write your own queries for the set of database files.
   • Use iDoctor for iSeries. iDoctor is a set of software performance analysis tools and associated services that extend your ability to evaluate the health of your system by gathering detailed information and providing automated, graphical analysis of this data.
   • Use the IBM^® Performance Trace Data Visualizer for iSeries (PTDV). PTDV is a Java™ application that you can use for performance analysis of applications. PTDV works with the Performance Explorer to allow you to view program flows and get details such as CPU time, wall clock time, number of cycles, and number of instructions, summarized by trace, job, thread, and procedures.

   
7. To end the performance explorer session, use the End Performance Explorer (ENDPEX) command.

• Ending performance explorer
  To end the performance explorer session, use the End Performance Explorer (ENDPEX) command.