> Every time I change my stored procedures I have to STOP and RESTART the
> database before my code change takes effect.  It's like I run REPLACE_JAR
> but it doesn't take effect.  I can even see the physical file being
updated
> in the DB2 JAR folder.  I assume the actual JAR file being used is in
memory
> and that's why stopping and restarting works.  ...What should I do?  This
is
> really slowing me down. :|  Is there any way to get my new JAR to kick in
> without stopping and restarting?

> I just read what Michael Bhola wrote... "keepdari = no in the dbm cfg
might
> help"  I'll post again if that solves my problem.

> > Every time I change my stored procedures I have to STOP and RESTART the
> > database before my code change takes effect.  It's like I run
REPLACE_JAR
> > but it doesn't take effect.  I can even see the physical file being
> updated
> > in the DB2 JAR folder.  I assume the actual JAR file being used is in
> memory
> > and that's why stopping and restarting works.  ...What should I do?
This
> is
> > really slowing me down. :|  Is there any way to get my new JAR to kick
in
> > without stopping and restarting?

> SCORE!  Thanks Michael.  That was my problem.

> > I just read what Michael Bhola wrote... "keepdari = no in the dbm cfg
> might
> > help"  I'll post again if that solves my problem.

> > > Every time I change my stored procedures I have to STOP and RESTART
the
> > > database before my code change takes effect.  It's like I run
> REPLACE_JAR
> > > but it doesn't take effect.  I can even see the physical file being
> > updated
> > > in the DB2 JAR folder.  I assume the actual JAR file being used is in
> > memory
> > > and that's why stopping and restarting works.  ...What should I do?
> This
> > is
> > > really slowing me down. :|  Is there any way to get my new JAR to kick
> in
> > > without stopping and restarting?

> Brian,

> Note that keepdari=no will slow down your sp execution a lot...another
> option is to use:

> "call sqlj.refresh_classes()"

> > SCORE!  Thanks Michael.  That was my problem.

> > > I just read what Michael Bhola wrote... "keepdari = no in the dbm cfg
> > might
> > > help"  I'll post again if that solves my problem.

> > > > Every time I change my stored procedures I have to STOP and RESTART
> the
> > > > database before my code change takes effect.  It's like I run
> > REPLACE_JAR
> > > > but it doesn't take effect.  I can even see the physical file being
> > > updated
> > > > in the DB2 JAR folder.  I assume the actual JAR file being used is
in
> > > memory
> > > > and that's why stopping and restarting works.  ...What should I do?
> > This
> > > is
> > > > really slowing me down. :|  Is there any way to get my new JAR to
kick
> > in
> > > > without stopping and restarting?

> Brian,

> Note that keepdari=no will slow down your sp execution a lot...another
> option is to use:

> "call sqlj.refresh_classes()"

> > SCORE!  Thanks Michael.  That was my problem.

> > > I just read what Michael Bhola wrote... "keepdari = no in the dbm cfg
> > might
> > > help"  I'll post again if that solves my problem.

> > > > Every time I change my stored procedures I have to STOP and RESTART
> the
> > > > database before my code change takes effect.  It's like I run
> > REPLACE_JAR
> > > > but it doesn't take effect.  I can even see the physical file being
> > > updated
> > > > in the DB2 JAR folder.  I assume the actual JAR file being used is
in
> > > memory
> > > > and that's why stopping and restarting works.  ...What should I do?
> > This
> > > is
> > > > really slowing me down. :|  Is there any way to get my new JAR to
kick
> > in
> > > > without stopping and restarting?