Program (PSB) Processing report description

The following table describes the Program (PSB) Processing report elements.

The reference numbers (with the <n> format) match the elements in the report example pages to the elements described in the table.

Program-Processing-report

Ref.	Description
1	CURRENT DATE Date this report was generated, in mm/dd/yyyy format
2	Subtitle Report subtitle, which can be user-specified (see Report-control-statements-for-PRSPSBRP-and-PRSPSB20) or a default subtitle (40 characters maximum) The default subtitle is determined by the control statement report code. One report is created for each control statement. Multiple reports are printed in descending sequence by report code. If report code 01 is selected, however, it is always printed first. Report code 01 produces an alphabetic listing.
3	REPORT NUMBER xx Report code specified by the variable xx in the report control statement
4	REPORT WILL HAVE FIRST nnnn PROGRAMS LISTED Defines the print limit request specified for this report
5	REPORTING RANGE REQUESTED Time range requested for this program usage analysis This range is the same as the range specified in the parameter input data. If the time range selection was not specified, this range is set to equal the ACTUAL REPORTING RANGE FOUND. The range is expressed as the lowest date (yyyy.ddd) and time (hh:mm) requested through the highest date (yyyy.ddd) and time (hh:mm) requested.
6	ACTUAL REPORTING RANGE FOUND Time range encountered for this program usage analysis This range is expressed as the lowest date (yyyy.ddd) and time (hh:mm) found in the data selected for reporting through the highest date (yyyy.ddd) and time (hh:mm) found in the data selected.
7	Heading row of the report The fields in the heading row correspond to the information for each entry in the report.
8	PROGRAM Name of the program being reported
8	TYPE Type of program being reported. The following codes are used: BMP; batch message processing program DBT; DBCTL CICS threads FPU; Fast Path utility program JBP; Java batch message processing program JMP; Java message processing program IFP; IMS Fast Path program MPP; message processing program MPC; message processing conversational MDP; Fast Path message-driven program NDP; Fast Path non-message-driven program ODB; DBCTL ODBA thread TPI; CPI-C driven programs
8	TRANS/EXEC Average number of transactions processed per scheduling of this program
8	LAST TRANS Name of the last transaction processed by this program during the analysis period If the response option is in effect, WITH RESPONSE OPTION appears after the report title in the second line.
8	RESPONSE TIME Average response time for the transactions processed by this program The time is in seconds and is derived by finding the difference between the time the transaction arrived in the queue and the time the transaction was completed and messages were ready to send back. Normally, this value is defined as the sum of INPUT QUEUE TIME plus ELAPSED TIME. For DBCTL threads and TPI, only the elapsed time is reported. If the response option is in effect, it is defined as transaction arrival time (of the original transaction in the case of message switches) to the first attempt to transmit an output message to the originating terminal (log record type 31). If no response is made for a transaction, this time is zero. Important If the response option is in effect, the response time is zero for DBCTL threads and TPI. If a transaction type generally has a response, but not always, the average reported here is artificially low. In the response reports (described in Transaction-Response-report) the averages are accurate even in this case.
8	NO. EXECS Number of times this program was scheduled during this reporting period
8	QUEUE TIME Average queue wait time for the transactions processed by this program The time is in seconds and is derived by finding the difference between the time the transaction arrived in the queue and the time that the transaction was started by the message processing program. Normally, queue time is defined from the arrival time of the originating transaction. If the response option is in effect, however, queue time is defined from the arrival time of the actual transaction. This definition differs from the normal definition only in the case of message switches. If the response option is in effect, the response time is zero for DBCTL threads and TPI.
8	(AVERAGES) Used in conjunction with the titles above this field
9	ELAPSED TIME Program residency time TOTAL HRS (time on the left) is the total elapsed program residency time for all program executions. The value is a sum of all the program’s elapsed times for the current reporting period. The value is expressed in hours. AVG SECS (time on the right) is the average elapsed program residency time per execution. The value is derived by dividing the ELAPSED TIME by the NO. EXECS. The value is expressed in seconds.
9	MSG REG CPU TIME Amount of CPU time TOTAL HRS (time on the left) is the cumulative amount of CPU time this program has consumed The value is the sum of all of the message region CPU time used in transaction processing for the current reporting period. The value is expressed in hours (the least significant digit represents 360 ms). AVG SECS (time on the right) is the average amount of CPU time this program consumes per execution The value is derived by dividing the MSG REG CPU TIME - TOTAL HOURS by the NO. EXECS. The value is expressed in microseconds. For more information, see .
9	DL/I CPU TIME Amount of DL/I CPU time this program has consumed TOTAL HRS (time on the left) is the cumulative amount of DL/I CPU time this program has consumed The value is the sum of all the DL/I CPU time used in transaction processing for this reporting period. The value is expressed in hours. AVG SECS (time on the right) is the average amount of DL/I CPU time this program has consumed The value is the sum of all the DL/I CPU time used in transaction processing for this reporting period. The value is expressed in microseconds. For more information, see and .
9	DB2 CPU TIME Amount of Db2 CPU time this program has consumed TOTAL HRS (time on the left) is the cumulative amount of Db2 CPU time this program has consumed The value is the sum of all the Db2 CPU time used in transaction processing for this reporting period. The value is expressed in hours. AVG SECS (time on the right) is the average amount of Db2 CPU time this program has consumed The value is the sum of all of the Db2 CPU TIME used in transaction processing for this reporting period. The value is expressed in microseconds. For DBCTL threads, this field is zero. For more information, see .
9	TOTAL HRS and AVG(SECS) Used in conjunction with the titles above this field
10	CORE Beginning of the ALOC and USED fields below it
10	ALOC Amount of free storage available in the dependent region after IMS initialization and program preloading (if used) For DBCTL threads, this field is zero.
10	USED Link-edited length of the program
10	ABEND% Percentage of time this program has abended, based on the number of abends divided by NO. EXECS
11	POOL Beginning of the PSB and DMB fields below it
11	PSB Highest amount of AMB pool space required in a single execution This element shows zero if the program issues no database calls.
11	DMB Highest amount of DMB pool space required in a single execution This element shows zero if the program issues no database calls.
11	SFAIL % Percentage of transactions that resulted in a nonzero Fast Path sync point return code The value equals the number of nonzero sync point return codes divided by the total number of transactions processed.
12	PROG SCHED Total amount of CPU time used by IMS to schedule this program The value is expressed in microseconds. For more information, see .
12	BUF HANDLE Total amount of CPU time used by the IMS buffer handler in processing the program during the current reporting period The value is expressed in microseconds. For more information, see and .
12	OPEN/CLOSE Total amount of CPU time used by the program to process the opens and closes of required databases during the current reporting period The value is expressed in microseconds. For more information, see and .
12	(SECONDS) Used in conjunction with the titles above it
13	MESSAGE GET UNIQUES Statistics for the MESSAGE GET UNIQUE calls issued by this program TOTAL Total number of calls issued HIGH Highest number of calls issued in a single execution If summarized IRUFs are used, this value is the average of the observed values. AVG Average number of calls issued in a single execution, calculated as total MESSAGE GET UNIQUE calls divided by NO. EXECS LOW Lowest (excluding zero values) number of calls issued in a single execution If summarized IRUFs are used, this value is the average of the observed values.
13	MESSAGE INSERTS Statistics for the MESSAGE INSERT calls issued by this program: TOTAL Total number of calls issued For IMS, MESSAGE PURGE calls are included. HIGH Highest number of calls issued in a single execution For IMS, MESSAGE PURGE calls are included. If summarized IRUFs are used, this value is the average of the observed values. AVG Average number of calls issued in a single execution, calculated as total MESSAGE INSERT calls divided by NO. EXECS LOW Lowest (excluding zero values) number of MESSAGE INSERT calls and PURGE calls issued in a single execution If summarized IRUFs are used, this value is the average of the observed values.
13	MESSAGE GET NEXTS Statistics for the MESSAGE GET NEXT calls issued by this program: TOTAL Total number of calls issued HIGH Highest number of calls issued in a single execution If summarized IRUFs are used, this value is the average of the observed values. AVG Average number of calls issued in a single execution, calculated as total GET NEXT calls divided by NO. EXECS LOW Lowest (excluding zero values) number of calls issued in a single execution If summarized IRUFs are used, this value is the average of the observed values.
13	TOTAL HIGH AVG LOW Used in conjunction with the titles above
14	DL/I REQUESTS Total number of DL/I requests made in transaction processing during the reporting period The DL/I request count is a total of all GET UNIQUE, GET NEXT, INSERT, REPLACE, and DELETE calls that have been issued.
14	ACTUAL I/O Total number of actual I/O requests made in transaction processing during the reporting period The actual I/O request count is a total of all key data set reads and writes, and all non-key data set reads and writes that have been issued. For more information, see Database-I-O-data.
14	NO I/O Count of the number of times during the reporting period that an I/O requirement was satisfied by finding the required record already contained in a buffer For more information, see Database-I-O-data.
14	DB2 REQUESTS Total number of Db2 requests made in transaction processing during the reporting period The Db2 request count is a total of all SQL calls that have been issued. For DBCTL threads, this field is zero.
14	MQ REQUESTS Total number of MQ requests made in transaction processing during the reporting period The MQ request count is a total of all MQ calls that have been issued. For DBCTL threads, this field is zero.

Program (PSB) Processing report description

On this page