RE: FW: IBM's RPG Strategy (was: Long Procedure Names)

The JNI calls were what I was referring to when I said, "looks like there's a 
procedure to call to check for them."

What I was trying to say was that the JNI calls needed to be used, you couldn't 
for instance use MONITOR/ENDMON around a call to a Java function and expect it 
to catch a Java error.

In other words, Java Exceptions <> OS/400 or RPG exception messages.

Charles


> -----Original Message-----
> From: rpg400-l-bounces@xxxxxxxxxxxx
> [mailto:rpg400-l-bounces@xxxxxxxxxxxx]On Behalf Of Paul Morgan
> Sent: Thursday, March 24, 2005 2:59 PM
> To: rpg400-l@xxxxxxxxxxxx
> Subject: Re: FW: IBM's RPG Strategy (was: Long Procedure Names)
> 
> 
> Charles,
> 
> The JNI interface provides for exception handling
> (http://java.sun.com/j2se/1.4.2/docs/guide/jni/spec/design.htm
> l#wp770).  JNI
> will allow a native method (an RPG program) to throw a Java 
> exception or
> allow a native method to handle a Java exception.
> 
> Paul
> 
> -- 
> Paul Morgan
> Senior Programmer Analyst - Retail
> J. Jill Group
> 100 Birch Pond Drive, PO Box 2009
> Tilton, NH 03276-2009
> Phone: (603) 266-2117
> Fax:   (603) 266-2333
> 
> "Wilt, Charles" wrote
> 
> > Not sure about Java exceptions, looks like there's a 
> procedure to call to
> check for them.  I don't believe they throw OS/400 exception 
> messages that
> RPG can catch.
> 
> 
>