SQLZ_DISCONNECT_PROC in V8 FP4 Stored Procedure

[Craig Wahlmeier]

I was cloning a store procedure that I wrote years ago and noticed
that I have to stop and start DB2 for Windows in order to replace the
dll. However, I have return(SQLZ_DISCONNECT_PROC) coded in my stored
procedure. So, I searched all the V8, V7, V6, V5 manuals for
SQLZ_DISCONNECT_PROC. Never found it! I see it is still defined in
the SQL.H include file. What gives? Is there a new way to do this?
Does the create procedure command have a parameter that I have missed?

TIA,

Craig Wahlmeier
Senior Technical Administrator
Data-Tronics Corp.

[Craig Wahlmeier]

Ok, found the answer in a redbook. Didn't know about KEEPFENCED=YES
in the dbm config. Wish I could control this at the program level,
not the dbm level.

Craig Wahlmeier

[Mike]

cw********@data-tronics.com (Craig Wahlmeier) wrote in message news:<ac**************************@posting.google. com>...

I was cloning a store procedure that I wrote years ago and noticed
that I have to stop and start DB2 for Windows in order to replace the
dll. However, I have return(SQLZ_DISCONNECT_PROC) coded in my stored
procedure. So, I searched all the V8, V7, V6, V5 manuals for
SQLZ_DISCONNECT_PROC. Never found it! I see it is still defined in
the SQL.H include file. What gives? Is there a new way to do this?
Does the create procedure command have a parameter that I have missed?

Check the setting of the KEEPFENCED instance parameter.
Try it with value NO and retstart the instance.

[Sean McKeough]

SQLZ_DISCONNECT_PROC should still be getting handled for C stored
procs...you should contact service, and open a PMR.

Craig Wahlmeier wrote:

Ok, found the answer in a redbook. Didn't know about KEEPFENCED=YES
in the dbm config. Wish I could control this at the program level,
not the dbm level.

Craig Wahlmeier