RE: The passing of user selections

["John Brandt Sr." <pgmr@xxxxxxxxxxxxxxx>]

For parameters larger than 32K, I regularly create user space and pass the
user space name and size as a parameter to the called process. The called
process destroys the user space after the user space is no longer needed.
The only problem this causes is that once a day, I have a job that runs to
delete any user spaces that were created for a job that did not complete or
was otherwise cancelled by the user.

John Brandt
iStudio400.com


-----Original Message-----
From: CarollaT@xxxxxxxxxxxxxx [mailto:CarollaT@xxxxxxxxxxxxxx]
Sent: Friday, December 26, 2003 3:17 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.
_______________________________________________
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.

---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.550 / Virus Database: 342 - Release Date: 12/9/03
 

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.555 / Virus Database: 347 - Release Date: 12/23/03