Re: The passing of user selections

["Booth Martin" <Booth@xxxxxxxxxxxx>]

A monstrous Data Structure is the easiest and cleanest.   Externally define
the data structure with all of the filters&fields you need.

The nicest part of this solution is that you can redefine the data stucture
without having to rewrite your program.

So far as it being resource intensive...  I would test that issue before I
said one way or the other, but I've used some pretty large data structures
without noticeble performance implications.
 
 
 
---------------------------------------------------------
Booth Martin   http://www.MartinVT.com
Booth@xxxxxxxxxxxx
---------------------------------------------------------
 
-------Original Message-------
 
From: RPG programming on the AS400 / iSeries
Date: 12/26/2003 3:15:38 PM
To: rpg400-l@xxxxxxxxxxxx
Subject: The passing of user selections
 
I trust everyone had a Merry Christmas, a Feliz Navidad, and all that good
stuff.  If not, I wish you one (albeit belated...)
 
I am building an RPGIV program to replace an NGS Query.
 
The user is allowed to make several selections that involve lists of values
(sites, contract IDs, etc.), and then the report is to be submitted to
batch.  The added requirement is that the job might be submitted multiple
times while the batch component is in the job queue from other runs.
 
I am trying to determine the best way to pass the selections to the batch
submission.  Should I use a USER SPACE, or a DATA QUEUE, or a uniquely named
file with the selections (different field sizes, types)?
 
I have pondered a monstrous, structured parameter string, but I have heard
such things are resource intensive.
 
How would you do it?
--------------------------------------
Tony Carolla
MedAmerica Billing Services, Inc.