The data that performance explorer collects is stored in performance explorer database files.
The following table shows the performance explorer (PEX) data files collected by the system when using data collection commands. Type the Display File Field Description (DSPFFD) command as follows to view the contents for a single file:
DSPFFD FILE(xxxxxxxxx)
where xxxxxxxxx is the name of the file that you want to display.
| Type of information contained in file | File name |
|---|---|
| Trace Resources Affinity |  QAYPEAFN |
| Auxiliary storage management event data | QAYPEASM |
| Auxiliary storage pool (ASP) information data | QAYPEASPI |
| Base event data | QAYPEBASE |
| Basic configuration information | QAYPECFGI |
| Communications event data | QAYPECMN |
| Disk event data | QAYPEDASD |
| Disk server event data | QAYPEDSRV |
| Event type and subtype mapping | QAYPEEVENT |
| File Serving event data | QAYPEFILSV |
| Configured filter information | QAYPEFTRI |
| Performance measurement counter (PMC) selection | QAYPEFQCFG |
| Heap event data | QAYPEHEAP |
| Hardware monitor data | QAYPEHMON |
| Hardware monitor total data | QAYPEHTOT |
| Performance explorer Java™ event data | QAYPEJVA |
| Performance explorer Java class information data | QAYPEJVCI |
| Performance explorer Java method information data | QAYPEJVMI |
| Performance explorer Java name information data | QAYPEJVNI |
| Licensed Internal Code (LIC) bracketing data | QAYPELBRKT |
| Machine interface (MI) complex instructions collected on | QAYPELCPLX |
| Jobs collected on | QAYPELJOB |
| Licensed Internal Code (LIC) modules to collect data on | QAYPELLIC |
| Metrics to collect data on | QAYPELMET |
| Machine interface (MI) program, module, or procedures collected on | QAYPELMI |
| Task names to collect data on | QAYPELNAMT |
| Task number to collect data on | QAYPELNUMT |
| Configured tasks | QAYPELTASK |
| Machine interface (MI) program bracketing data | QAYPEMBRKT |
| Machine interface (MI) complex instructions mapping | QAYPEMICPX |
| Addresses of machine interface (MI) pointer | QAYPEMIPTR |
| Machine interface (MI) user event data | QAYPEMIUSR |
| Portable Application Solutions Environment (PASE) event data | QAYPEPASE |
| Page fault event data | QAYPEPGFLT |
| Program profile data | QAYPEPPANE |
| Licensed Internal Code (LIC) address resolution mapping | QAYPEPROCI |
| Resource management process event data | QAYPERMPM |
| Resource management seize lock event data | QAYPERMSL |
| Reference information | QAYPEREF |
| Miscellaneous resolution data | QAYPERINF |
| Database level indicator | QAYPERLS |
| General information | QAYPERUNI |
| Segment address range (SAR) data | QAYPESAR |
| Segment address resolution mapping | QAYPESEGI |
| Basic statistics data | QAYPESTATS |
| Synchronization event data | QAYPESYNC |
| Process and task resolution mapping | QAYPETASKI |
| Trace job equivalent event data | QAYPETBRKT |
| Common trace data for all events | QAYPETIDX |
| Trace index data (by time and task) | QAYPETIDXL |
| Trace index data (by time) | QAYPETID2L |
| Task switch event data | QAYPETSKSW |
| User-defined bracketing hook data | QAYPEUSRDF |
Migration of performance explorer database files
The performance explorer (PEX) database files change from release to release, as new events and new data are added to the files. When you migrate to a new release of i5/OS™, if the system finds incompatible PEX database files, it moves these files to the QPEXDvrmxx library, where vrm=version. The system displays a status message that indicates that the files are being moved. After the files are moved, the system displays a completion message that indicates whether the move succeeded or failed. If the move fails, the system displays the Incompatible repository message.