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 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 contained in the category or in the primary file. However, they are not controlled by that category.

Users should note the following:

  1. The CRTPFRDTA command generates a database file only when that file is a primary file for the selected category.

  2. If a primary file is listed for multiple categories, select each of those categories to generate the file.

  3. If a primary file for one category is listed as a secondary file for another category, 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, select both *CMNBASE and *CMNSTN.

  4. 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
QAPMFRLY
QAPMHDLC
QAPMIDLC
QAPMLAPD
QAPMPPP
QAPMX25

*CMNSAP QAPMSAP
*CMNSTN

QAPMSTND
QAPMSTNE
QAPMSTNL
QAPMSTNY
none

QAPMDDI
QAPMETH
QAPMECL
QAPMFRLY
QAPMX25

*DISK QAPMDISK QAPMSYSTEM
*DOMINO QAPMDOMINO
*DPS QAPMDPS
*EACACHE none QAPMDISK See Note.
*HDWCFG QAPMHDWR
*HTTP

QAPMHTTPB
QAPMHTTPD

*IOPBASE

QAPMIOPD
QAPMLIOP
QAPMDIOP
QAPMCIOP
QAPMMIOP

*IPCS

QAPMIOPD
QAPMTSK

*JOBMI

QAPMJOBMI
QAPMJOBWT
QAPMJOBWTD
QAPMJSUM

QAPMJOBL
QAPMSYSL

QAPMSYSTEM
*JOBOS

QAPMJOBOS
QAPMJSUM

QAPMJOBL
QAPMSYSL

QAPMSYSTEM
*LCLRSP QAPMRESP
*LPAR QAPMLPAR
*POOL QAPMPOOLB QAPMPOOLL
*POOLTUNE QAPMPOOLT QAPMPOOLL
*SNA QAPMSNA
*SNADS QAPMSNADS
*SUBSYSTEM QAPMSBSD
*SYSBUS QAPMBUS
*SYSCPU QAPMSYSCPU QAPMSYSL
*SYSLVL QAPMSYSTEM QAPMSYSL
*TCPBASE QAPMTCP
*TCPIFC QAPMTCPIFC
*USRTNS QAPMUSRTNS QAPMARMTRT

This category is not selectable by CRTPFRDTA. However, it causes additional data to be reported by the *DISK category.

 

Parent topic:

Performance data files
Related information
Collection Services