× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



What release of OS/400 are you on? 

> -----Original Message-----
> From: java400-l-bounces@xxxxxxxxxxxx 
> [mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of Chris Wolcott
> Sent: Thursday, December 16, 2004 7:21 AM
> To: java400-l@xxxxxxxxxxxx
> Subject: Calling *SRVPGMs from JAVA - How to DEBUG?
> 
> Our biggest issue is debugging the *SRVPGM procedures.  How 
> do we do that?  I can't figure out where the *SRVPGM is 
> running.  The JAVA program prints the job info it gets, but I 
> can't always find that job and even if I do there is nothing 
> useful there.  If I have the C use
> printf()  I can't find the output.  Anyone know where the 
> output goes and how to debug this?
>  
> We have a JAVA program that needs to call a *SRVPGM that 
> contains *MODULEs written in C, CL and RPG.  Calling the C is 
> not too bad, except we seem to have issues passing char 
> variables.  We've got around it so far by just passing them 
> as char * instead, but we have to write wrappers for the 
> procedures that expect plain char parameters.
>  
> We also seem to have found that whatever job the *SRVPGM is 
> running in on the iSeries does not seem to have a *LIBL.  We 
> had to write a procedure that calls an existing CL that sets 
> the appropriate *LIBL.
> This is mainly an issue with the RPG, since the C can specify 
> the library as a variable at run time.  
>  
> 


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.