Performance data files: Collection Services 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 Service 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 is dependent on must exist and be processed by CRTPFRDTA. The table below 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 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 table below, 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 table below illustrates the relationships between system categories and performance database files.

Category	Primary files	Compatibility files	Secondary files
*SYSBUS	QAPMBUS
*POOL	QAPMPOOLB	QAPMPOOLL
*POOLTUNE	QAPMPOOLT	QAPMPOOLL
*HDWCFG	QAPMHDWR
*SUBSYSTEM	QAPMSBSD
*SYSCPU	QAPMSYSCPU	QAPMSYSL
*SYSLVL	QAPMSYSTEM	QAPMSYSL
*JOBMI	QAPMJOBMI QAPMJOBWT QAPMJOBWTD QAPMJSUM	QAPMJOBL QAPMSYSL	QAPMSYSTEM
*JOBOS	QAPMJOBOS QAPMJSUM	QAPMJOBL QAPMSYSL	QAPMSYSTEM
*SNADS	QAPMSNADS
*DISK	QAPMDISK		QAPMSYSTEM
*IOPBASE	QAPMIOPD QAPMLIOP QAPMDIOP QAPMCIOP QAPMMIOP
*IPCS	QAPMIOPD QAPMTSK
*CMNBASE	QAPMASYN QAPMBSC QAPMDDI QAPMECL QAPMETH QAPMFRLY QAPMHDLC QAPMIDLC QAPMLAPD QAPMPPP QAPMX25
*CMNSTN	QAPMSTND QAPMSTNE QAPMSTNL QAPMSTNY none		QAPMDDI QAPMETH QAPMECL QAPMFRLY QAPMX25
*CMNSAP	QAPMSAP
*LCLRSP	QAPMRESP
*APPN	QAPMAPPN
*SNA	QAPMSNA
*EACACHE	none		QAPMDISK See Note.
*TCPBASE	QAPMTCP
*TCPIFC	QAPMTCPIFC
*DOMINO	QAPMDOMINO
*HTTP	QAPMHTTPB QAPMHTTPD
*USRTNS	QAPMUSRTNS		QAPMARMTRT
*DPS	QAPMDPS
*LPAR	QAPMLPAR
Note: This category is not selectable by CRTPFRDTA. However, it causes additional data to be reported by the *DISK category.