We are migrating a whole bunch of stored procedures written in C & COBOL to DB2 LUW as External stored procedures. The current practice is, for every change to a procedure, there is a need to restart the DB2 Instance for the change to properly reflect.

My question is, is there a way to avoid this ?

Regards
Vijay

------------------------------
Vijay Shankar
------------------------------

#Db2

Hello Vijay,

I have never encountered the need for restarting the instance when changing a stored procedure.
Just perform every step that you performed the first time you created it.
You can set up a make file to perform these steps.

What error messages do you get when you do not restart the instance after a procedure change ?

------------------------------
Yves-Antoine Emmanuelli
------------------------------

Hi

Thank you for your response.

What DB2 does is hold on to a copy of the older load module, even after we move the new one. Results in a -818 timestamp mismatch failure as the executing load and the package are different.

I figured that this behaviour could be due to the KEEPFENCED=YES  dbm parameter, which lets the db2 fenced mode process to be reused for subsequent calls and eventually holds on to the first loaded module even if it has changed in the disk. This gets released only when the instance is bounced. I updated this to a NO to get my issue fixed. But I guess this is not recommended in high volume production due to the overheads associated with creating a db2fmp for each call.

Do correct me if my understanding is incorrect

Regards

Vijay

------------------------------
Vijay Shankar Arunachalam
------------------------------

Original Message:
Sent: Thu August 27, 2020 04:17 AM
From: Yves-Antoine Emmanuelli
Subject: DB2 LUW - External procedure and Instance Restart

Hello Vijay,

I have never encountered the need for restarting the instance when changing a stored procedure.
Just perform every step that you performed the first time you created it.
You can set up a make file to perform these steps.

What error messages do you get when you do not restart the instance after a procedure change ?

------------------------------
Yves-Antoine Emmanuelli
------------------------------