RE: IFS and CL

You can redirect the output of QShell commands to physical files. 

First you create a physical file.

crtpf vern/ls255 rcdlen(255)

Then run this command to get the contents of /home/vern into that physical file.

qsh cmd('ls -l /home/vern > /qsys.lib/vern.lib/ls255.file/ls255.mbr')

Then do the usual RCVF loop to read it. First position has a 'd' if you have a 
directory - other letters are possible. Positions 2-10 have the permission 
flags, file names start in 62.

Make the PF record longer if need be.

HTH
Vern
-------------- Original message -------------- 
From: "Carl Galgano" <cgalgano2@xxxxxxxxxxxxxxxxx> 

> James, go to our website (www.ediconsulting.com) and click on downloads. 
> There is a DIR command that will list the contents of an IFS directory to an 
> outfile. The in your CL, read the outfile in a loop and do what you need to 
> do. 
> 
> Carl 
> EDI Consulting Services, Inc. 
> 
> -----Original Message----- 
> From: midrange-l-bounces@xxxxxxxxxxxx 
> [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of James H H Lampert 
> Sent: Monday, January 30, 2006 2:14 PM 
> To: midrange-l@xxxxxxxxxxxx 
> Subject: IFS and CL 
> 
> Is there an easy way to make a CL program step through the objects in an IFS 
> directory? 
> 
> -- 
> JHHL 
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list 
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, 
> or change list options, 
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l 
> or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a 
> moment to review the archives at http://archive.midrange.com/midrange-l. 
> 
> 
> -- 
> This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list 
> To post a message email: MIDRANGE-L@xxxxxxxxxxxx 
> To subscribe, unsubscribe, or change list options, 
> visit: http://lists.midrange.com/mailman/listinfo/midrange-l 
> or email: MIDRANGE-L-request@xxxxxxxxxxxx 
> Before posting, please take a moment to review the archives 
> at http://archive.midrange.com/midrange-l. 
>