Re: Debugging strategies for a Java UDTF

Ron_H_Java@xxxxxxxxxx wrote:

I'm in the same boat, these are tough to debug.

This Redbook has a discussion on how to debug external UDTF's: 
http://www.redbooks.ibm.com/redbooks/pdfs/sg246503.pdf
(Stored Procedures, Triggers and User Defined Functions on DB2 Universal 
Database for iSeries)

Good Luck
Ron

Thanks for the reply Ron.  Yes, they can be tough to debug but they are
getting easier!

I got the manual you suggested and can get debugging going through the
point where I issue the STRDBG CLASS(myClass) point.  I continue to get
"Class not found errors", in spite of trying every permutation of my
class file name, from CaMeL CaSe to all lower case, from myClass to
myClass.class, and from the class name only to a fully qualified name:
/qibm/.../myClass.  In all cases, no dice.

I called the gurus at IBM an they, too, are baffled why this isn't
working.  I'm expecting a call back.

I did find out that the mojo necessary to get the stdout/stderr & stdin
put to a file is referred to on page 144 of the "iSeries: IBM Developer
Kit for Java".  You need to add the environment variable:
QIBM_USE_DESCRIPTOR_STDIO=Y.  Unless you override the file name path in
SystemDefault.preferences (os400.std??=file:/path/here/to/name) you'll
find the results in the IFS:

/tmp/qsqjavastp.std{err|out|in}

Best regards,

Barry