× 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.




Sorry it took me too long to respond to David's post, I had a stupid problem in my program. I set the value to argv [1] incorrectly.

Yes! David was right. It's working now!
The Parameters should be separated in the PCML file.

Thanks to David and all others


-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx [mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of Barbara Morris
Sent: Tuesday, January 03, 2012 9:30 PM
To: java400-l@xxxxxxxxxxxx
Subject: Re: FW: Using PCML from Java to Call C/400 Program

On 2011/12/28 9:28 AM, David Gibbs wrote:

Although I'm not an expert in C, shouldn't each element of argv be
specified as a separate parameter in the PCML?

So it would be something like ...

<pcml version="1.0"> <program name="myCProg"
path="/QSYS.LIB/MyLib.LIB/MyC_Porg.PGM"> <data name="argv1"
type="char" length="100" usage="inputoutput"/> <data name="argv2"
type="char" length="100" usage="inputoutput"/> <data name="argv3"
type="char" length="100" usage="inputoutput"/> </program> </pcml>


David is correct that you have to define the parameters separately to
PCML. It is just a C convention that program parameters are coded as an
array of pointers. When you actually call a C program, you pass separate
parameters.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
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.