Author: TS70363
Subject: COBOL DB2 - CALL statement - high CPU consumption
Posted: Sun Sep 11, 2016 6:07 am (GMT 5.5)
Hi..
Thru my Cobol application program, I am calling a native stored procedure using a host variable. It has various other SQLs as well.
1. I have to find out the schema/qualifier name and prefix it to the stored procedure before executing the CALL statement. Can I avoid doing so? If yes, what are the changes required?
2. It is a batch process. The stored procedure CALL statement is consuming a very high CPU. We have IBM APA tool to monitor the batches. I noticed , the CALL takes 35-40 % of the overall CPU of the batch. Also BMC Apptune (DB2 performance monitoring tool) suggests there are equivalent number of intermediate binds as the number of records processed. The STP has 35 input parameters and 3 output parameters.
Can anyone suggest the reason behind this behaviour?
Is it because the call is thru a host variable prefixed with qualifier?
Is it due to a high number of inout parameters?
Where is the intermediate bind occuring?
_________________
TS70363
Subject: COBOL DB2 - CALL statement - high CPU consumption
Posted: Sun Sep 11, 2016 6:07 am (GMT 5.5)
Hi..
Thru my Cobol application program, I am calling a native stored procedure using a host variable. It has various other SQLs as well.
| Code: |
| EXEC SQL CALL :HV-PROC-NAME END-EXEC |
1. I have to find out the schema/qualifier name and prefix it to the stored procedure before executing the CALL statement. Can I avoid doing so? If yes, what are the changes required?
2. It is a batch process. The stored procedure CALL statement is consuming a very high CPU. We have IBM APA tool to monitor the batches. I noticed , the CALL takes 35-40 % of the overall CPU of the batch. Also BMC Apptune (DB2 performance monitoring tool) suggests there are equivalent number of intermediate binds as the number of records processed. The STP has 35 input parameters and 3 output parameters.
Can anyone suggest the reason behind this behaviour?
Is it because the call is thru a host variable prefixed with qualifier?
Is it due to a high number of inout parameters?
Where is the intermediate bind occuring?
_________________
TS70363