RE: Recursive call and commitment control scope

Hello Lim, 

You could put the subfile records into a data queue, maybe. I haven't ever 
defined them so big, but the command doc says you can create it with *MAX2GB, 
to let it grow to 2 gigabytes. 

I would probably rather put the records into a data queue in QTEMP rather than 
a physical file.. Once you got the subroutines or subprocedures set up 
initially, it could work as easily as, or better than, a physical file. 
Certainly it would run faster, if it makes much difference with the latest 
high-powered machines... 

I use data queues anyway for subfile processing, since I saw Kevin Vandever's 
(name?) tricks. 

                (Lim wrote: - 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.