RE: Recursive call and commitment control scope

- Main reason to put all the directory content in a qtemp physical file
is to be able to sort them easily.  If there is no sql keyword that can
isolate the select result, my next option would be adding a activation
group name field in the file and select records by this name.

- I could use userspace/user index to do the sorting, however, at this
point, physical seems to be the easier route.  (Note: Not able to use
Array/variable because it has size limitation).

-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx
[mailto:rpg400-l-bounces@xxxxxxxxxxxx] On Behalf Of Rory Hewitt
Sent: Monday, July 17, 2006 12:03 PM
To: RPG programming on the AS400 / iSeries
Subject: Re: Recursive call and commitment control scope

Lim,

Since QTEMP is global to the job, I'd allocate memory within each
instance of the program and use that to hold the list of
directories/files rather than QTEMP. That should do it.

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