Re: Passing data structure to batch job -- RPG400-L

Good News Everybody!

The new search engine is LIVE!

Please report any problems to david (at) midrange.com.

Subject: Re: Passing data structure to batch job
From: Booth Martin <booth@xxxxxxxxxxxx>
Date: Thu, 24 May 2012 10:51:10 -0500
List-archive: <http://archive.midrange.com/rpg400-l>
List-help: <mailto:rpg400-l-request@midrange.com?subject=help>
List-id: RPG programming on the IBM i / System i <rpg400-l.midrange.com>
List-post: <mailto:rpg400-l@midrange.com>
List-subscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=subscribe>
List-unsubscribe: <http://lists.midrange.com/mailman/listinfo/rpg400-l>, <mailto:rpg400-l-request@midrange.com?subject=unsubscribe>

Sure. You can even uniquely name them and keep them hanging around from day to day. (It could keep "last invoice number used" for instance.)

http://publib.boulder.ibm.com/infocenter/iseries/v5r4/index.jsp?topic=/books/c092508602.htm

On 5/24/2012 10:47 AM, Dave wrote:

I'm not following this interesting thread! The LDA of the second job cannot
use the LDA of the first job. Can it?

2012/5/24 David Gibbs<david@xxxxxxxxxxxx>

On 5/24/2012 9:56 AM, Jonathan Ball wrote:

That was my first thought as well. An alternative would be to pass the
data structure as a single large parameter. The submitted job can
redefine the parameter as an internal data structure with multiple

elements.

The LDA approach strikes me as a little easier.

There could be issues passing a large parameter to a program ...
especially if it's going to be submitted.
http://wiki.midrange.com/index.php/Parameter_passing

Using the LDA is the safest approach, I think.

david

As an Amazon Associate we earn from qualifying purchases.

Follow-Ups:

RE: Passing data structure to batch job , Jerry C. Adams
RE: Passing data structure to batch job , Koester, Michael

This mailing list archive is Copyright 1997-2026 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.