Performance data files: QAPMSYSTEMINTNUMInterval number: The nth sample database interval based on the start time specified in the Create Performance Data (CRTPFRDTA) command.PD (5,0)DTETIMInterval date (yymmdd) and time (hhmmss): The date and time of the sample interval.C (12)INTSECElapsed interval seconds: The number of seconds since the last sample interval.PD (7,0)DTECENCentury digit.C (1)SYDPGFDirectory page faults: Number of times a page of the auxiliary storage directory was transferred to main storage for a look-up or an allocation operation.PD (11,0)SYAPGFAccess group member page faults: Number of times a page of an object contained in an access group was transferred to main storage independently of the access group. This transfer occurs when the containing access group was purged, or because portions of the containing access group are displaced from main storage.PD (11,0)SYMPGFMicrocode page faults: Number of times a page of microcode was transferred to main storage.PD (11,0)SYMCTRMicrotask read operations: Number of transfers of one or more pages of data from auxiliary storage because of a microtask rather than a process.PD (11,0)SYMCTWMicrotask write operations: Number of transfers of one or more pages of data from main storage to auxiliary storage because of a microtask rather than a process.PD (11,0)SYSASPSystem auxiliary storage pool space available: Number of bytes of space on auxiliary storage available for allocation in the system ASP that is not currently assigned to machine interface (MI) objects or internal machine functions.PD (15,0)SYPRMWPermanent data transferred from main storage: Number of 512-byte blocks of permanent data transferred from main storage to the system ASP in auxiliary storage since the last sample.PD (11,0)SYSIZCSize count: Total number of size exceptions.PD (11,0)SYDECDDecimal data count: Total number of decimal data exceptions.PD (11,0)SYSEZCSeize count: Total number of seize wait exceptions.PD (11,0)SYSZWTSeize/wait time in milliseconds.PD (11,0)SYSYNLSynchronous lock conflict count.PD (11,0)SYASYLAsynchronous lock conflict count.PD (11,0)SYVFYCVerify count.PD (11,0)SYAUTHObject authority checks. The number of times that authority was checked for objects. An authority check for one object can result in zero, one, or more than one user authority lookups that can be cached or noncached (see SYNUAL field description).PD (11,0)SYEXPNTotal number of exceptions.PD (11,0)SYLRT1Transactions in first response time monitor bracket: Total number of local workstation transactions with response time less than the value of boundary 1 specified on the Advanced Local Response Time Options dialog from the Collection Services properties page within the iSeries™ Navigator interface.PD (9,0)SYLRT2Transactions in second response time monitor bracket: Total number of local workstation transactions with response time less than the value of boundary 2 and greater than the value of boundary 1 specified on the Advanced Local Response Time Options dialog from the Collection Services properties page within the iSeries Navigator interface.PD (9,0)SYLRT3Transactions in third response time monitor bracket: Total number of local workstation transactions with response time less than the value of boundary 3 and greater than the value of boundary 2 specified on the Advanced Local Response Time Options dialog from the Collection Services properties page within the iSeries Navigator interface.PD (9,0)SYLRT4Transactions in fourth response time monitor bracket: Total number of local workstation transactions with response time less than the value of boundary 4 and greater than the value of boundary 3 specified on the Advanced Local Response Time Options dialog from the Collection Services properties page within the iSeries Navigator interface.PD (9,0)SYLRT5Transactions in fifth response time monitor bracket: Total number of local workstation transactions with response time greater than the value of boundary 4 specified on the Advanced Local Response Time Options dialog from the Collection Services properties page within the iSeries Navigator interface.PD (9,0)SHCPUTotal processing unit time (in milliseconds) used by microcode/system jobs.PD (11,0)SMPLPMachine pool paging: Number of pages transferred in and out of machine pool.PD (11,0)SMUPLHighest user pool paging: Highest number of pages transferred in and out of any user pool.PD (11,0)SUPLIPool with highest paging: Pool number with highest number of pages transferred in and out.C (2)SMXDUMaximum disk utilization. The largest utilization of all single path disk units and all paths of multipath disk units.PD (11,0)SMXDUIActuator with maximum utilization.C (4)SMMMTTime (in seconds) spent at MRTMAX by all MRT requests.PD (11,0)SMMENumber of requesters that routed to an MRT.PD (11,0)SYFOPNNumber of full opens system wide.PD (11,0)SYIXRBNumber of index rebuilds system wide.PD (11,0)SYJOXRStart journal operations initiated by user.PD (11,0)SYJOXPStop journal operations initiated by user.PD (11,0)SYJOIRStart journal operations initiated by system.PD (11,0)SYJOIPStop journal operations initiated by system.PD (11,0)SYJOXDJournal deposits resulting from user-journaled objects.PD (11,0)SYJOIDJournal deposits resulting from system-journaled objects.PD (11,0)SYJOJPJournal deposits resulting from system-journaled objects to user-created journals.PD (11,0)SYJOBJBundle writes to user-created journals.PD (11,0)SYJOBDBundle writes to internal system journals.PD (11,0)SYJOJYExposed access paths currently being journaled by the system.PD (11,0)SYJOJNExposed access paths currently not being journaled.PD (11,0)SYJOSESystem-estimated access path recovery time exposure in milliseconds.PD (11,0)SYJORTSystem-managed access path tuning adjustments.PD (11,0)SYJONDSystem-estimated access path recovery time exposure in milliseconds if no access paths were being journaled by the system.PD (11,0)SYHEAONumber of tolerated crossings of a 16 MB boundary within any teraspace. Also called teraspace EAO exceptions.PD (11,0)SYHFTSNumber of space address computations (not addressing teraspace) that required extra processing. This may occur when a subtraction or addition of a signed value causes a result that is within the first page of a space object or associated space for which the machine did not choose alignment. Also called false traps.PD (11,0)SYHFTHNumber of teraspace address computations that required extra processing. This occurs when a subtraction or addition of a signed value causes a result that is within the first page after any 16 MB boundary in teraspace. Also called false traps.PD (11,0)SYSDBCDatabase CPU time. The amount of CPU time (in milliseconds) used for database processing.PD (9,0)SYSSWCSecondary workload CPU time. The aggregate CPU time (in milliseconds) of all jobs performing workloads that cannot fully exploit dedicated server resources.
Note: This metric measures non-Domino CPU usage on Domino® servers. On non-Domino servers, this metric is not supported, so the reported value is 0.
PD (9,0)SYJOERNumber of SMAPP evaluations requested. This count reveals how many times implicitly journaled objects were examined for potential SMAPP eligibility alterations. The evaluation can result in one of three outcomes: 1 - no action; 2 - start protecting this index via SMAPP; 3 - cease protecting this index via SMAPP.PD (11,0)SYJOESNumber of SMAPP evaluations serviced. This is a count of evaluations which led to a decision to change the protection state for a related index.PD (11,0)SYJOIBNumber of SMAPP index build time estimations. The number of times background SLIC tasks have been asked to look at database keyed logical files or SQL indexes in order to estimate how long it will take to rebuild the index from scratch. Indexes whose estimated rebuild times are large will be SMAPPed. A large count here suggests that applications are frequently opening and closing files.PD (11,0)SYJOS1First journal entry type. This field reports the most frequently occurring among the various journal entry types that have caused the SLIC layer of journal code to empty the journal cache prematurely. The number of bundles forced by this entry type is reported in the field SYJOC1.C (2)SYJOC1Number of journal bundles forced prematurely by the journal entry type reported in the field SYJOS1.PD (15,0)SYJOS2Second journal entry type. This field reports the second most frequently occurring among the various journal entry types that have caused the SLIC layer of journal code to empty the journal cache prematurely. The number of bundles forced by this entry type is reported in the field SYJOC2.C (2)SYJOC2Number of journal bundles forced prematurely by the journal entry type reported in the field SYJOS2.PD (15,0)SYJOS3Third journal entry type. This field reports the third most frequently occurring among the various journal entry types that have caused the SLIC layer of journal code to empty the journal cache prematurely. The number of bundles forced by this entry type is reported in the field SYJOC3.C (2)SYJOC3Number of journal bundles forced prematurely by the journal entry type reported in the field SYJOS3.PD (15,0)SYSDNFEThe number of stream files which have been written to, but not forced to permanent storage. This count includes files in the Root, QOpenSys, QDLS, QOPT (when the files are on a volume that is not formatted in Universal Disk Format (UDS)) and user-defined file systems.PD (11,0)SYSDNFOThe number of stream files currently exposed that have exceeded the target exposure time. This count includes files in the Root, QOpenSys, QDLS, QOPT (when the files are on a volume that is not formatted in Universal Disk Format (UDS)) and user-defined file systems.PD (11,0)SYSDTETExposure time (in milliseconds). The number of milliseconds between the time a stream file is written to and the time the file is forced to permanent storage. This time is a total for all files that were exposed during the interval. This count includes files in the Root, QOpenSys, QDLS, QOPT (when the files are on a volume that is not formatted in Universal Disk Format (UDS)) and user-defined file systems.PD (15,0)SYSDNSTThe number of tasks running that are forcing stream files to permanent storage. This count includes files in the Root, QOpenSys, QDLS, QOPT (when the files are on a volume that is not formatted in Universal Disk Format (UDS)) and user-defined file systems.PD (5,0)SYSDFALThe number of stream files that have been exposed and needed to be forced. This count includes files in the Root, QOpenSys, QDLS, QOPT (when the files are on a volume that is not formatted in Universal Disk Format (UDS)) and user-defined file systems.PD (11,0)SYSDFRLThe total number of stream files that have been asynchronously forced to permanent storage. This count includes files in the Root, QOpenSys, QDLS, QOPT (when the files are on a volume that is not formatted in Universal Disk Format (UDS)) and user-defined file systems.PD (11,0)SYSDPFDThe number of stream file pages that have been asynchronously forced to permanent storage. This count does not include pages forced by an fsync operation. This count includes files in the Root, QOpenSys, QDLS, QOPT (when the files are on a volume that is not formatted in Universal Disk Format (UDS)) and user-defined file systems.PD (15,0)SYSDPFFThe number of stream file pages explicitly forced to permanent storage as a result of an fsync operation. This count includes files in the Root, QOpenSys, QDLS, QOPT (when the files are on a volume that is not formatted in Universal Disk Format (UDS)) and user-defined file systems.PD (15,0)SYBTACThe number of asynchronous clear operations performed. This count includes files in the Root, QOpenSys, QDLS, QOPT (when the files are on a volume that is not formatted in Universal Disk Format (UDS)) and user-defined file systems.PD (11,0)SYBTAPThe number of asynchronous prebring operations performed. This count includes files in the Root, QOpenSys, QDLS, QOPT (when the files are on a volume that is not formatted in Universal Disk Format (UDS)) and user-defined file systems.PD (11,0)SYBTAPPThe number of parallel prebring operations performed. This count includes files in the Root, QOpenSys, QDLS, QOPT (when the files are on a volume that is not formatted in Universal Disk Format (UDS)) and user-defined file systems.PD (11,0)SYBTAPCThe number of asynchronous create operations performed. This count includes files in the Root, QOpenSys, QDLS, QOPT (when the files are on a volume that is not formatted in Universal Disk Format (UDS)) and user-defined file systems.PD (11,0)SYBTAPDThe number of asynchronous delete operations performed. This count includes files in the Root, QOpenSys, QDLS, QOPT (when the files are on a volume that is not formatted in Universal Disk Format (UDS)) and user-defined file systems.PD (11,0)SYLPTBLPAR time base. This field provides a way to determine the difference between the system clocks on different partitions of a single system. This field has no meaning when looked at on a stand-alone basis. However, when this value is established on two (or more) partitions of a system, the difference between these values is the time difference (in seconds) between the two partitions.B (11,0)SYNUALNoncached user authority lookups. The number of times that a noncached user authority lookup was performed. An authority check for one object can result in zero, one, or more than one user authority lookups. A user authority lookup can occur for the user, the user's groups, or an adopted user and can be cached or noncached.PD (15,0)SYIFUSInteractive CPU time used. Total interactive CPU used (in milliseconds).PD (9,0)SYIFTEInteractive CPU time used over threshold. Interactive CPU used (in milliseconds) when exceeding interactive CPU threshold.PD (9,0)SYIFTAInteractive CPU time available. The amount of interactive CPU time that was available for use within the partition. This is the interactive capacity configured for use within the partition (also represented as interactive threshold).PD (11,0)SYSPTUCPU time used. Total processing time (in milliseconds) used by the partitionPD (11,0)SYSCTATotal CPU time configured for the partition. Total processing time (in milliseconds) that was configured or guaranteed for this partition. This is the system processing capacity as determined by processor unit allocations during the interval. Note: For uncapped partitions, the actual CPU used can exceed this value.PD (11,0)SYSUTACPU time that could have been used by this partition. Total processing time (in milliseconds) that could have been used by this partition (adjusted for configuration changes over time). It includes both the guaranteed configured capacity as well as the shared pool time that was not used by other partitions. For capped and dedicated partitions, or if shared pool data is not available, this is the same as Uncapped CPU time configured.PD (11,0)SYSUTCUncapped CPU time configured. The maximum amount of CPU time that this partition is configured (allowed) to use within the shared pool (adjusted for configuration changes over time). This field defines the Minimum of the virtual processors configured and the configured shared pool processors. For capped and dedicated partitions, this is the same as total CPU time configured for the partition.PD (11,0)SYSPLUShared pool CPU time used. Total amount of CPU used within the shared pool by all partitions that share the pool. Set to zero if a shared pool is not used or the data is not available.PD (11,0)SYSPLAShared pool CPU time available. Total amount of CPU available within the shared pool. This value is determined based on the number of physical processors that are allocated to the pool. Set to zero if a shared pool is not used or the data is not available.PD (11,0)SYVCPUVirtual processor time configured. The processing time capacity (in milliseconds) visible to the operating system based on the number of virtual processors configured and adjusted for configuration changes over time. This field is similar to SYSUTC except it is not affected by the shared pool configuration or the capped/uncapped state of the partition. The formula SYVCPU/(INTSEC*1000) will yield the average number of virtual processors configured in the interval. Note: Will be zero for data obtained prior to V5R4PD (11,0)SYDPCHTotal Dispatch Time. The amount of time (in milliseconds) that the operating system has dispatched a job, task, or thread to a processor. This is not the same as CPU time used due to the effects of processor virtualization. Note: this field will contain data only if file QAPMJOBWT data is availablePD (11,0)SYSHRFShared processor flag. Indicates if the partition uses shared processors:

‘ ‘ = unknown

'0'= Partition does not share physical processors.

'1' = Partition shares physical processors.

C (1)SYSIULReserved.PD (5,0)SYSCIUReserved.PD (7,0)SYJDUMReserved.PD (1,0)SYJDDMReserved.C (3)SYJCA4Reserved.C (3)SYJPASReserved.C (3)SYJMRTReserved.C (3)SYJS6EReserved.C (3)SYJCMEReserved.C (3)SYJAUTReserved.C (3)SYJBCHReserved.C (3)SYJINTReserved.C (3)SYJSPLReserved.C (3)
Field Name Description Attribute