Author: TS70363
Posted: Sun Sep 11, 2016 9:27 pm (GMT 5.5)
Hi Rohit,
I understand your point.
I am ready to make a change. Please confirm - you are asking me to move the SQLs within the Stored procedure to my COBOL program and test the performance.
I have 12 such stored procedures, the names of which are being picked up from a lookup DB2 table (kind of reference data tables) based on the key passed from the COBOL code. The SP name is then prefixed with the Schema name and used in the Call statement. Each SP has at least 3 SQLs.
Moving all the 36+ SQLs to program will require significant amount of time. I will have to justify the amount of time I take to move all the SQLs to the COBOL sub-program. Hence I am looking for the answers which I can then take it to my DBAs and Project Manager.
I can confirm the results after I have made the change but I will be really happy and grateful if you could give me the information I am looking for.
_________________
TS70363
Posted: Sun Sep 11, 2016 9:27 pm (GMT 5.5)
Hi Rohit,
I understand your point.
| Quote: |
| Why do you not convert it to a batch sub module? |
I have 12 such stored procedures, the names of which are being picked up from a lookup DB2 table (kind of reference data tables) based on the key passed from the COBOL code. The SP name is then prefixed with the Schema name and used in the Call statement. Each SP has at least 3 SQLs.
Moving all the 36+ SQLs to program will require significant amount of time. I will have to justify the amount of time I take to move all the SQLs to the COBOL sub-program. Hence I am looking for the answers which I can then take it to my DBAs and Project Manager.
I can confirm the results after I have made the change but I will be really happy and grateful if you could give me the information I am looking for.
_________________
TS70363