Collection Services data files: QAPMUSRTNS
This database file contains performance data for the user-defined and Application Response Measurement (ARM) transactions.
One record is created for each type of transaction that occurs for a given job during the interval.
| Field Name | Description | Attribute |
|---|---|---|
| INTNUM | Interval number: The nth sample database interval based on the start time specified in the Create Performance Data (CRTPFRDTA) command. | PD (5,0) |
| DTETIM | Interval date (yymmdd) and time (hhmmss): The date and time of the sample interval. | C (12) |
| INTSEC | Elapsed interval seconds: The number of seconds since the last sample interval. | PD (7,0) |
| DTECEN | Century digit: where 0 indicates 19XX and 1 indicates 20XX. | C (1) |
| UTNAM | Job name. | C (10) |
| UTUSR | Job user. | C (10) |
| UTNUM | Job number. | C (6) |
| UTTYP | Transaction type. The type of user-defined transaction reported
in this record for this job. The transaction type has the same value
as the application identifier parameter passed to the Start
Transaction API and End Transaction API.
If Collection Services encounters more than 15 transaction types for
this job, it will combine the transaction data for any additional
transaction types into the transaction type of *OTHER. When Application
Response Measurement (ARM) transaction data is reported in the QAPMUSRTNS
file, this field contains an ARM transaction type name. Names of ARM
transaction types start with the prefix |
C (20) |
| UTTIM | Total time in microseconds used by all transactions of this type for this job. | B (18,0) |
| UTNUMT | Total number of transactions of this type for this job. This represents the number of calls to the End Transaction API. | B (9,0) |
| UTSTR | Number of calls to the Start Transaction API for this transaction
type and job. For ARM transaction types, this field is 0, because ARM APIs do not go through the Start Transaction API. |
B (9,0) |
| UTBAD | Number of calls to the End Transaction API for this transaction type and job which passed a bad transaction start time. This can occur for various reasons including: The start time is zero. The start time is after the end time. The start time is before the job start time. | B (9,0) |
| UTNUMC | Number (N) of user-provided counters associated with this transaction type and job. These counters are reported in the first N UTCTn fields. This field is zero if there are no user-provided counters. | B (9,0) |
| UTCT1 | User-provided counter 1. For ARM transaction types, this field contains the total ARM transaction queuing time in milliseconds. |
B (18,0) |
| UTCT2 | User-provided counter 2. | B (18,0) |
| UTCT3 | User-provided counter 3. | B (18,0) |
| UTCT4 | User-provided counter 4. | B (18,0) |
| UTCT5 | User-provided counter 5. | B (18,0) |
| UTCT6 | User-provided counter 6. | B (18,0) |
| UTCT7 | User-provided counter 7. | B (18,0) |
| UTCT8 | User-provided counter 8. | B (18,0) |
| UTCT9 | User-provided counter 9. | B (18,0) |
| UTCT10 | User-provided counter 10. | B (18,0) |
| UTCT11 | User-provided counter 11. | B (18,0) |
| UTCT12 | User-provided counter 12. | B (18,0) |
| UTCT13 | User-provided counter 13. | B (18,0) |
| UTCT14 | User-provided counter 14. | B (18,0) |
| UTCT15 | User-provided counter 15. | B (18,0) |
| UTCT16 | User-provided counter 16. | B (18,0) |
Note: ARM transaction
data is reported only for applications which call the ARM API implementation
that is shipped with the operating system.
|
||