Collection Services data files: System category and file relationships
When you collect performance data using Collection Services, the data is stored in a management collection (*MGTCOL) object.
The Create Performance Data (CRTPFRDTA) command exports data from that management collection object and then writes the data to the performance data files. Each type of data that can be independently controlled and collected by Collection Services is represented by a data category. Each data category contains or provides data that is written to one or more performance data files. For a database file or member to be created, the category (or group of categories) that the file or member depends on must exist and be processed by CRTPFRDTA. The following table identifies the category-to-file relationships. There are three types of relationships.
| Relationship | Description |
|---|---|
| Primary files | These files are related to and generated from the category. |
| Compatibility files | These files are logical files that join primary files to provide performance database compatibility with the previous file structure. If the system generates all participating files (primary categories), compatibility files are also generated. |
| Secondary files | These files are related to and contain some data that is derived from data that is contained in the category or in the primary file. However, they are not controlled by that category. |
Users should note the following:
- The CRTPFRDTA command generates a database file only when that file is a primary file for the selected category.
- If a primary file is listed for multiple categories, you must select each of those categories to generate the file.
- If a primary file for one category is listed as a secondary file for another category, you must select the second category to ensure complete information in your generated database file. For example, as shown in the following table, to generate a complete database file for QAPMECL, you must select both *CMNBASE and *CMNSTN.
- The system generates compatibility files only when it generates all associated primary files.
The following table illustrates the relationships between system categories and performance database files.
| Category | Primary files | Compatibility files | Secondary files |
|---|---|---|---|
| *APPN | QAPMAPPN | ||
| *CMNBASE | QAPMASYN
QAPMBSC QAPMDDI QAPMECL QAPMETH QAPMETHP QAPMFRLY QAPMHDLC QAPMIDLC QAPMLAPD QAPMPPP QAPMSMCMN QAPMX25 |
||
| *CMNSAP | QAPMSAP | ||
| *CMNSTN | QAPMSTND
QAPMSTNE QAPMSTNL QAPMSTNY none |
QAPMDDI
QAPMETH QAPMECL QAPMFRLY QAPMX25 |
|
| *DISK | QAPMDISK
QAPMDISKRB QAPMSMDSK QAPMXSTGV  QAPMXSTGVC |
QAPMSYSTEM | |
| *DOMINO | QAPMDOMINO | ||
| *DPS | QAPMDPS | ||
| *EACACHE | none | QAPMDISK See Note. | |
| *EXTSTG |
QAPMXSTGD
QAPMXSTGDLQAPMXSTGDRQAPMXSTGDZ |
||
| *HDWCFG | QAPMHDWR | ||
| *HTTP | QAPMHTTPB
QAPMHTTPD QAPMSMHTP |
||
| *IOPBASE | QAPMIOPD
QAPMLIOP QAPMDIOP QAPMCIOP QAPMMIOP |
||
| *IPCS | QAPMIOPD
QAPMTSK |
||
| *JAVA | QAPMJVM | ||
| *JOBMI | QAPMJOBMI
QAPMJOBWT QAPMJOBWTD QAPMJOBWTG QAPMJSUM QAPMSMJMI QAPMISUM |
QAPMJOBL
QAPMSYSL |
QAPMSYSTEM |
| *JOBOS | QAPMJOBOS
QAPMJSUM QAPMJOBSR QAPMSMJOS QAPMISUM |
QAPMJOBL
QAPMSYSL |
QAPMSYSTEM |
| *LCLRSP | QAPMRESP | ||
| *LPAR | QAPMLPARH | ||
| *POOL | QAPMPOOLB
QAPMSMPOL |
QAPMPOOLL | |
| *POOLTUNE | QAPMPOOLT | QAPMPOOLL | |
| *RDMA |
QAPMLINK
QAPMNRG QAPMNRGL |
||
| *RMVSTG | QAPMTAPE | ||
| *SNA | QAPMSNA | ||
| *SNADS | QAPMSNADS | ||
| *SQL | QAPMSQLPC | ||
| *SUBSYSTEM | QAPMSBSD | ||
| *SYSBUS | QAPMBUS
QAPMBUSINT |
||
| *SYSCPU | QAPMSYSCPU
QAPMSYSPRC QAPMSYSAFN QAPMSYSVP |
QAPMSYSL | |
| *SYSINT | QAPMSYSINT | ||
| *SYSLVL | QAPMSHRMP
QAPMSMSYS QAPMSYSTEM QAPMSYSWLC QAPMISUM QAPMJSUM |
QAPMSYSL | |
| *TCPBASE | QAPMTCP | ||
| *TCPIFC | QAPMTCPIFC | ||
| *USRTNS | QAPMUSRTNS | QAPMARMTRT | |
Note: This category is not selectable by CRTPFRDTA. However, it causes more data to
be reported by the *DISK category.
|
|||