Collection Services data files: QAPMCONF

This database file contains general information about the collection.

QAPMCONF includes information about collection options, characteristics of the database files generated, and information about the system on which the data was collected. One record is written to this file for each item reported (see the GKEY field). This file is not optional. Data in this file is generated for every database collection. This data is reported only at the beginning of the collection. Although most of the data in this file does not change during the collection, some data might change. Changes are not reported.

The GKEY fields B1-B5 apply to the disk response time bucket data in the QAPMDISK file. The GKEY fields G1-GA apply to the disk response time bucket data in the QAPMDISKRB file.

GRES: Reserved.
Attributes: C (4)
GKEY: Identifier to indicate what data is contained in the GDES field. See descriptions in the following table.
Attributes: C (2)
GDES: Data for the associated GKEY value. See values in the following table. Unless otherwise noted, all system values pertain to the partition for which the data was collected. Unless otherwise indicated, all the data is left-aligned in this field.
Attributes: C (10)

GKEY	GDES
1	Performance data start date, expressed in local system time. Date is reported as a C(7) value with the following format: (yymmddc).
2	Performance data start time, expressed in local system time. Time is reported as a C(6) value with the following format: (hhmmss).
3	A 4-character model number followed by a 4-character system type.
4	Memory for the partition (zoned (10,0)) in KB (kilobytes). If this field is set to the largest number it can hold (9999999999), the memory for the partition is too large to fit in this record. Use the record with GKEY PM instead.
5	Communications data is collected, which is set to Y only if any communication files were created.
6	Physical machine serial number (character 10).
6B	Virtual serial number (character 8). If a virtual serial number is not being used, this field will contain the physical machine serial number.
7	First response time boundary (zoned (10,0)) in milliseconds. The first response time monitor bracket is from 0 up to and including the first response time boundary.
8	Second response time boundary (zoned (10,0)) in milliseconds. The second response time monitor bracket is from the first response time boundary up to and including the second response time boundary.
9	Third response time boundary (zoned (10,0)) in milliseconds. The third response time monitor bracket is from the second response time boundary up to and including the third response time boundary.
10	Fourth response time boundary (zoned (10,0)) in milliseconds. The fourth response time monitor bracket is from the third response time boundary up to and including the fourth response time boundary. Responses greater than the fourth response time boundary fall under the fifth response time monitor bracket.
11	System ASP capacity (zoned (10,0)) in KB (kilobytes). This value is the total amount of auxiliary storage that is allocated to the system ASP for the storage of data in KB. If this field is set to the largest number it can hold (9999999999), the system ASP capacity is too large to fit in this record. Use the record with GKEY 21 instead.
12	Checksum protection on (Y/N).
13	Number of virtual processors assigned to the partition (PD (3,0)) followed by the installed physical processor count (2-byte binary) followed by the active physical processor count (2-byte binary). Virtual processors: For uncapped partitions, the number of virtual processors that are assigned to the partition establishes the maximum amount of physical processor resources that can be used by the partition. For capped partitions, the maximum amount of physical processor resources that the partition can use is limited by the number of processing units that are assigned, regardless of the number of virtual processors assigned. Installed physical processors: The maximum number of physical processors that can be active in the physical machine without installing more processors. This number includes the number of permanently activated processors, the number of temporarily activated processors, and the number of any standby processors that might be present in the physical machine that are not activated. Active physical processors: The number of physical processors in the physical machine that are permanently or temporarily activated.
14	First remote response time boundary (zoned (10,0)) in milliseconds. The first response time monitor bracket is from 0 up to and including the first response time boundary. This data appears only when requested with the Start Performance Monitor (STRPFRMON) command.
15	Second remote response time boundary (zoned (10,0)) in milliseconds. The second response time monitor bracket is from the first response time boundary up to and including the second response time boundary. This data appears only when requested with the Start Performance Monitor (STRPFRMON) command.
16	Third remote response time boundary (zoned (10,0)) in milliseconds. The third response time monitor bracket is from the second response time boundary up to and including the third response time boundary. This data appears only when requested with the STRPFRMON command.
17	Fourth remote response time boundary (zoned (10,0)) in milliseconds. The fourth response time monitor bracket is from the third response time boundary up to and including the fourth response time boundary. Responses greater than the fourth response time boundary fall under the fifth response time monitor bracket. This data appears only when requested with the STRPFRMON command.
21	System ASP capacity in KB (kilobytes). This value is the total amount of auxiliary storage that is allocated to the system ASP for the storage of data in KB. This number is reported as an unsigned 8-byte binary value.
AP	Permanent 16 MB addresses that remain for the machine. This address is reported as an unsigned 8-byte binary value.
AT	Temporary 16 MB addresses that remain for the machine. This address is reported as an unsigned 8-byte binary value.
B1	The first disk response time boundary in milliseconds (B(9,0)). The first disk response time bucket is from 0 up to the first response time boundary.
B2	The second disk response time boundary in milliseconds ((B(9,0)). The second disk response time bucket is from and including the first response time boundary up to the second boundary.
B3	The third disk response time boundary in milliseconds ((B(9,0)). The third disk response time bucket is from and including the second response time boundary up to the third boundary.
B4	The fourth disk response time boundary in milliseconds ((B(9,0)). The fourth disk response time bucket is from and including the third response time boundary up to the fourth boundary.
B5	The fifth disk response time boundary in milliseconds ((B(9,0)). The fifth disk response time bucket is from and including the fourth response time boundary up to the fifth boundary. The sixth disk response time bucket includes everything above and including the fifth response time boundary.
CD	Collection data. Possible values are: 0: This collection is consistent with files that are created by the traditional performance monitor SYS collection. 1: Collection data is not SYS. The database files that are generated from the collection might not be sufficient for applications (such as Performance Tools reports or PM for Power Systems) that depend on traditional performance monitor data.
CI	Collect internal data (Y/N).
CL	Collection library. The name of the library in which the management collection object resides.
CN	Collection name. The name of the management collection object.
CP	Partition is allowed to collect performance data across partitions flag CHAR(1). Possible values are: '0': The partition is not allowed to collect performance data across partitions. '1': The partition is allowed to collect performance data across partitions.
CT	Collection Type. Indicates the type of database file collection (how this database file collection was created). Possible values are: `'STANDARD '` - Standard collection created by the CRTPFRDTA system job `'SYSMON '` - System Monitor collection created by the CRTPFRDTA2 system job `'*USER '` - Collection created by a non-system use of CRTPFRDTA command
DB	Database consistency. Possible values are: 0: No problem detected in database files. 1: Due to the interval size selected or to inconsistent collection intervals, the database files that are generated might contain missing intervals or other inconsistencies that might cause problems for applications that depend on traditional performance monitor data.
DL	Database limit is a B(4,1) value that is the percent of the total system CPU. For example, 125 means 12.5%.
DM	On demand memory information. The total amount of on demand memory in gigabytes (GB) that exists on the machine (4-byte binary) followed by the amount of on demand memory in gigabytes (GB) still available to be allocated (4-byte binary). Memory that is activated by permanent, temporary, or metered capacity upgrades is not considered available. This record appears only on systems with on demand memory.
DP	Capacity on demand processor information. The maximum capacity on demand physical processor count (2-byte binary) followed by the capacity on demand processors available count (2-byte binary). This record appears only on systems with on demand processors. Maximum Capacity on Demand Physical Processors: The maximum number of physical processors the physical machine can have if it were fully configured. This number includes both the number of installed physical processors (see GKEY 13) and the number of processors that would still need to be physically installed. Capacity on Demand Processors Available: The number of physical processors that are available for purchase. This number includes both the number of installed physical processors (see GKEY 13) and the number of processors that would still need to be physically installed. Processors that are activated by permanent, temporary, or metered capacity upgrades are not considered available.
DT	Database threshold is a B(4,1) value that is the percent of the total system CPU. For example, 125 means 12.5%.
ED	End date. The date associated with the last interval in the collection, expressed in local system time. This date is reported as a left-aligned CHAR(7) field. It appears in the following format: CYYMMDD.
ET	End time. The time associated with the last interval in the collection, expressed in local system time. This time is reported as a left-aligned CHAR(6) field. It appears in the following format: HHMMSS. Note: The following is a description of the contents of the End date and End time fields for both active and nonactive collections. For a nonactive collection, the date and time come from the last interval that exists in the management collection object. For an *ACTIVE collection, the date and time come from the last interval that was processed by CRTPFRDTA.
F	File level (PD(2,0)). This value specifies the level of the performance database files. The value is changed each time the format of any of the performance database files change.
FC	Processor feature code (character 4).
FI	Interactive feature (character 4). This field is blank for servers that have no interactive features.
FL	System firmware level CHAR(7).
FP	Processor feature (character 4).
FT	Partition processor firmware time attribute. A 1-byte character field that indicates whether the partition accumulates processor firmware time. '0' - partition does note accumulate processor firmware time '1' - partition accumulates processor firmware time
F1	Threshold values used to control reporting of tasks and secondary threads that have short lifespans. Data format is an unsigned 4-byte binary task threshold followed by an unsigned 4-byte binary secondary thread threshold. Thresholds are reported in milliseconds. Tasks and secondary threads whose lifespan is shorter than the reporting threshold are not individually collected in the JOBMI category data. Instead one entry per resource affinity domain is accumulated for tasks that are running in that resource affinity domain and one entry per job is accumulated for secondary threads of that job. See file QAPMJOBMI field JBSLTCNT. The short lifespan thresholds that are used during data collection can be overridden by using system environment variables that specify the reporting threshold (number of milliseconds) to use. The following example causes data for all tasks and secondary threads to be individually collected: ADDENVVAR ENVVAR(QPM_TASK_SL_THRESHOLD) VALUE(0) LEVEL(SYS) ADDENVVAR ENVVAR(QPM_THREAD_SL_THRESHOLD) VALUE(0) LEVEL(*SYS)
G1	The first disk response time boundary in microseconds (B(9,0)). The first disk response time bucket is from 0 up to the first response time boundary.
G2	The second disk response time boundary in microseconds (B(9,0)). The second disk response time bucket is from and including the first response time boundary up to the second boundary.
G3	The third disk response time boundary in microseconds (B(9,0)). The third disk response time bucket is from and including the second response time boundary up to the third boundary.
G4	The fourth disk response time boundary in microseconds (B(9,0)). The fourth disk response time bucket is from and including the third response time boundary up to the fourth boundary.
G5	The fifth disk response time boundary in microseconds (B(9,0)). The fifth disk response time bucket is from and including the fourth response time boundary up to the fifth boundary.
G6	The sixth disk response time boundary in microseconds (B(9,0)). The sixth disk response time bucket is from and including the fifth response time boundary up to the sixth boundary.
G7	The seventh disk response time boundary in microseconds (B(9,0)). The seventh disk response time bucket is from and including the sixth response time boundary up to the seventh boundary.
G8	The eighth disk response time boundary in microseconds (B(9,0)). The eighth disk response time bucket is from and including the seventh response time boundary up to the eighth boundary.
G9	The ninth disk response time boundary in microseconds (B(9,0)). The ninth disk response time bucket is from and including the eighth response time boundary up to the ninth boundary.
GA	The tenth disk response time boundary in microseconds (B(9,0)). The tenth disk response time bucket is from and including the ninth response time boundary up to the tenth boundary. The eleventh disk response time bucket includes everything above and including the tenth response time boundary.
HM	Hypervisor memory. This value is the total amount of memory, in megabytes, used by the hypervisor. This memory is physical machine memory and is not associated with the partition's memory allocation. The amount of memory is determined by the number of partitions and attributes of each partition. The value is reported as an unsigned 4-byte binary.
HP	Physical processor model. The value is reported as a 2-byte binary.
HT	SMT hardware threads. The current maximum number of SMT hardware threads on this IPL. Reported as a 2-byte binary field. '0' - no maximum.
I	Interval (PD(2,0)). The time interval (in minutes) between each collection of system performance data.
IL	Interactive limit as a percent of the configured processor units (see Processor units allocated to the partition (PU)). The value is reported in two different formats: a 2-byte binary B(4,1) value followed by a 4-byte binary B(5,2) value. For example, in the second format, a value of 1250 means 12.50%. For the most accurate data, use the second value.
IS	Interval seconds (PD(4,0)). The time interval (in seconds) between each collection of system performance data.
IT	Interactive threshold as a percent of the configured processor units (see Processor units that are allocated to the partition (PU)). The value is reported in two different formats: a 2-byte binary B(4,1) value followed by a 4-byte binary B(5,2) value. For example, in the second format, a value of 1250 means 12.50%. For the most accurate data, use the second value.
LP	Logical processor model. The value is reported as a 2-byte binary.
MT	Processor multitasking. A 1-byte character field that indicates the multitasking capability for the current IPL. '0' - Processor multitasking capability is disabled. '1' - Processor multitasking capability is enabled. '2' - Processor multitasking capability is system controlled.
NF	Processor nominal frequency in MHz (4-byte binary).
OS	Output file system (character 8). This value represents the system where the database files are generated.
P1	Partition universal unique identifier (UUID). A partition UUID is a unique 128-bit identifier for the partition, generated when the partition was created. A partition's UUID remains the same even when partition mobility and remote restart functions are used. GKEY P1 reports the first 8 bytes of the partition UUID as an unsigned 8-byte binary. GKEY P2 reports the second 8 bytes of the partition UUID as an unsigned 8-byte binary.
P2	Partition universal unique identifier (UUID). A partition UUID is a unique 128-bit identifier for the partition, generated when the partition was created. A partition's UUID remains the same even when partition mobility and remote restart functions are used. GKEY P1 reports the first 8 bytes of the partition UUID as an unsigned 8-byte binary. GKEY P2 reports the second 8 bytes of the partition UUID as an unsigned 8-byte binary.
PC	Partition count. The value is reported in two different formats: a zoned (2,0) value that is capped at 99 followed by an unsigned 4-byte binary value. For the most accurate data, use the second value.
PE	Power Enterprise Pools indicator (character 4). If the system is not a member of a Power Enterprise Pool, the value '0000' is reported. If the system is a member of a Power Enterprise Pool 2.0, the value 'PEP2' is reported. This is reported correctly on FW1040 or later. If the system is a member of a Power Enterprise Pool 1.0, the value reported identifies the number of cores assigned to the system.
PF	Processor folding support. A 1-byte character field that indicates whether processor folding is supported on the IPL. '0' - Processor folding is not supported '1' - Processor folding is supported
PM	Memory size for the partition (zoned (10,0)) in MB (megabytes).
PN	Partition identifier. The value is reported in two different formats: a character 1 followed by an unsigned 4-byte binary value.
PP	Primary partition. The value is reported in two different formats: a character 1 followed by an unsigned 4-byte binary value.
PU	Processor units that are allocated to the partition. The value is reported as a 4-byte binary B(5,2). For example, 175 means 1.75 processor units.
R	Version number (PD(2,0)), followed by release number (PD(3,1)).
S	System name (character 8).
SJ	The Select job (SLTJOB) parameter value (character 10). This value can be ALL or ACTIVE. This parameter applies to the performance monitor. Collection Services does not use the SJ parameter.
SP	Shared processor pool attributes. This record contains partition attributes that are related to shared processor pools. The first item identifies if the partition uses a shared pool. The rest of the data applies if sharing is in effect: Byte 1: CHAR(1) - Processor sharing '0' = Partition does not share physical processors. '1' = Partition shares physical processors. Byte 2: CHAR(1) - capped/uncapped '0' = Partition is capped. '1' = Partition is uncapped. Byte 3: CHAR(1) - Identifies if the system supports variable processor speed ' ' = Unknown. '0' = System does not support variable processor speed. '1' = System supports variable processor speed.
S1	Value (character 1) of the QPFRADJ system value.
S2	Value (character 1) of the QDYNPTYSCD system value.
S3	Value (character 1) of the QDYNPTYADJ system value.
T	Trace type (character 5). Specifies the type of internal trace that was started with the Start Performance Monitor command (ALL or NONE). Collection Services always reports *NONE.
T1	Performance data start date, expressed in local system time. Date is reported as a CHAR(10) value with the following format: (YYYY-MM-DD).
T2	Performance data start time, expressed in local system time. Time is reported as a left-aligned CHAR(8) value with the following format: (HH.MM.SS).
T3	End date. The date associated with the last interval in the collection, expressed in local system time. This date is reported as a CHAR(10) field. It appears in the following format: (YYYY-MM-DD). Note: The following is a description of the contents of the End date and End time fields for both active and nonactive collections. For a nonactive collection, the date and time come from the last interval that exists in the management collection object. For an *ACTIVE collection, the date and time come from the last interval that was processed by CRTPFRDTA.
T4	End time. The time associated with the last interval in the collection, expressed in local system time. This time is reported as a left-aligned CHAR(8) field. It appears in the following format: (HH.MM.SS).
TC	The current number of secondary hardware threads per processor. It is reported as a 2-byte binary field.
TM	The maximum number of secondary hardware threads per processor. It is reported as a 2-byte binary field.
TY	The Coordinated Universal Time offset. The time difference between the local system time of the collection and Coordinated Universal Time (UTC). The offset is reported as a left-aligned CHAR(5) field in one of the following formats: ( 0000) or (+HHMM) or (-HHMM). The offset is subtracted from local system time to obtain UTC time.
TZ	Timezone. The name of the time zone description (system value QTIMZON) used to represent local system time of the collection (character 10). This field is set to UNKNOWN for collections where the time zone was unable to be determined, such as data from a prior release that did not support collecting the time zone information.
UP	Partition usage counts. This record is present on systems that support 5770-SS1 feature 5052 (user entitlement key). One metric is returned as a 4-byte binary value: Usage count – the number of named users that are enabled in this partition.
US	System usage counts. This record is present on systems that support 5770-SS1 feature 5052 (user entitlement key). Two metrics are returned as 4-byte binary values: Usage Limit – the number of named users allowed. This limit is system-based not partition-based. Accurate reporting depends on license key information that must be entered by the customer on the reporting partition. Usage count – the number of named users that are enabled in the system. This value is system-based not partition-based.
U1	Performance data start date, expressed in Coordinated Universal Time (UTC). Date is reported as a CHAR(10) value with the following format: (YYYY-MM-DD).
U2	Performance data start time, expressed in Coordinated Universal Time (UTC). Time is reported as a CHAR(8) value with the following format: (HH.MM.SS).
U3	End date. The date associated with the last interval in the collection, expressed in Coordinated Universal Time (UTC). This date is reported as a CHAR(10) field. It appears in the following format: (YYYY-MM-DD). Note: The following is a description of the contents of the End date and End time fields for both active and nonactive collections. For a nonactive collection, the date and time come from the last interval that exists in the management collection object. For an *ACTIVE collection, the date and time come from the last interval that was processed by CRTPFRDTA.
U4	End time. The time associated with the last interval in the collection, expressed in Coordinated Universal Time (UTC). This time is reported as a left-aligned CHAR(8) field. It appears in the following format: (HH.MM.SS).
XP	PM Agent data obtained. Indicates whether this collection was processed for PM Agent data requirements. Applies to the originating system only. This field is a 1-byte character field with a value of 1. This record is not present unless PM Agent data was obtained.
XS	Summary data created. Indicates whether summary data was created with this collection. This field is a 1-byte character field with a value of 1. This record is not present unless summary data was created.