MIDRANGE dot COM Mailing List Archive



Home » JAVA400-L » October 2009

RE: Retrieving integer parameter after JT400 ProgramCall?



fixed

Ok. That is one way to do it. Though that leaves you with some dummy
files. Not much of a problem. Only an organizational thing which has to
be handled.

It would be nice if I could have an RFML xml streamfile on the i which I
could use to fill a space (variable, userspace, u name it ... ). I would
fill some kind of map and pass it with an RFML file and a pointer to the
space to a procedure which fills me the space according to the RFML
file.

The RFML could be put into a SVN repository which can be checkout out
from the Java and RPG side.

Sounds like a nice project ... =)

Just some ideas ...

Regards

Mihael

-----Original Message-----
From: java400-l-bounces@xxxxxxxxxxxx
[mailto:java400-l-bounces@xxxxxxxxxxxx] On Behalf Of David Gibbs
Sent: Thursday, October 29, 2009 12:47 PM
To: Java Programming on and around the iSeries / AS400
Subject: Re: Retrieving integer parameter after JT400 ProgramCall?

Schmidt, Mihael wrote:
Do you mean by that that you are using the RPG xml file in your RPG
code
to fill/create an entry in the data queue (or userspace or whatever)?
That would be really great so one could use the exact same file in RPG
and Java.

No.

What I'm doing is using an external data structure (physical file) in an
RPG program to format the data sent in the data queue ... and then that
same physical file is used to define the structure of the RFML or
RecordFormat object in java.

I construct a AS400FileRecordDescription object
(http://javadoc.midrange.com/jtopen_6_2/com/ibm/as400/access/AS400FileRe
cordDescription.html) and retrieve the first RecordFormat from it. From
that I can either create a Record or build a RecordFormatDocument.

david







Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2014 by MIDRANGE dot 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 here. If you have questions about this, please contact