RE: How to update a stored procedure?

Buck --

Can you call this same stored procedure twice within a single STRSQL
session?  I'm thinking that maybe when the stored procedure is ending,
the JVM is shutting down.  Sort of like if you were executing a
System.exit() call.  Then, when you go to execute it again, the JVM is
gone and STRSQL gets confused.

Of course, this would happen anytime you try to execute that java
program twice and has nothing to do with the fact that you changed the
name.  Also, I believe the JVM ends when an activation group ends so
maybe something like that is happening.  Are you calling a native
program from your java stored procedure that is causing an activation
group to end?  What level of commitment control are you using on STRSQL?
Have you tried it with *NONE?

PTF SI04186 looks like it may be a similar problem.  Is this PTF
applied?

If none of this works out, I'd open a problem with SupportLine.
Hopefully, they can have you run a trace to see why the JVM is
disappearing.

HTH,
Gary

> -----Original Message-----
> From: java400-l-admin@midrange.com
> [mailto:java400-l-admin@midrange.com] On Behalf Of Buck Calabro
> Sent: Tuesday, August 13, 2002 3:15 PM
> To: java400-l@midrange.com
> Subject: RE: How to update a stored procedure?
>
>
> >What release of OS/400 are you on?
>
> V5R1 and very current.  We've been doing a bunch of WAS
> related development so we have all of the latest group PTFs
> including Java and DB2.
>
> >What is the message ID for "Trigger program or external routine
> >detected an error."  What is the second level help?
>
> call buckProc2 ('select * from comdbtrn/actphy01' )
> CPDB520 Error 5 detected on application programming
> interface. CPDB520 Error 12 detected on application
> programming interface. SQL0443 Trigger program or external
> routine detected an error.
>
> 05- The Java Virtual Machine could not be found.  It was
> never created or has been destroyed.
>
> 12- The current thread is not attached to a Java Virtual Machine.
>
> Remember that this is happening in ISQL, not the command
> line.  buckProc2 is the name of my Java Stored Procedure.  If
> I drop it, sign off and re-create it, it works.  Any time I
> drop/re-create without signing off, I get the errors.  It is
> clearly not an issue with either the CREATE PROCEDURE nor
> with the actual Java code.  There's some odd mechanical thing
> happening here when the class is memory resident and getting changed.
>   --buck