Performance information is not displayed as text on message CPF1164. Because the message is in the QHST log, users can write application programs to retrieve this data.
The performance information is passed as a variable length replacement text value. This means that the data is in a structure within the first entry being the length of the data. The size of the length field is not included in the length.
Time and Date: The first data fields in the structure are the times and dates that the job entered the system and when the first routing step for the job was started. The times are in the format 'hh:mm:ss'. The time separators in this example are colons. This separator is determined by the value specified in the Date and time (QTIMSEP) system value. The dates are in the format defined in the Date and time (QDATFMT) system value and the separators are in the Date and time (QDATSEP) system value. The time and date the job entered the system precede the job start time and date in the structure. The time and date the job entered the system are when the system becomes aware of a job to be initiated (a job structure is set aside for the job). For an interactive job, the job entry time is the time the password is recognized by the system. For a batch job, it is the time the Batch Job (BCHJOB) or Submit Job (SBMJOB) command is processed. For a monitor job, reader or writer, it is the time the corresponding start command is processed, and for autostart jobs it is during the start of the subsystem.
Total Response Time and Number of Transactions: Following the times and dates are the total response time and the number of transactions. The total response time is in seconds and contains the accumulated value of all the intervals the job was processing between pressing the Enter key at the workstation and when the next display is shown. This information is similar to that shown on the Work with Active Job (WRKACTJOB) display. This field is only meaningful for interactive jobs.
It is also possible in the case of a system failure or abnormal job end that the last transaction will not be included in the total. The job end code in this case would be a 40 or greater. The transaction count is also only meaningful for interactive jobs other than the console job and is the number of response time intervals counted by the system during the job.
If the job ends with an end code of 70, this value may not contain the count for the final routing step. Additionally, if a job exists across an IPL (using a Transfer Batch Job (TFRBCHJOB) command) it is ended before becoming active following an IPL, the value is 0.