Re: Accessing files In QTEMP and the utility of multi-memberfile s

Yup - that's my point.  why take 3 externally described files and
convert them to program described for a multi member.  It would work & I
could put the files back to externally described with another cpyf but
it's not as clean as separate objects.

I'm not totally against multi-member files I just think there are better
ways of doing things.

John Hall

"James W. Kilgore" wrote:
> 
> John,
> 
> You can accomplish what you want.  Try this:
> 
> 1) Create a library called, let's say, TRANSMISSON
> 2) Create a file for each date, let's day, D20001019.  Create it without DDS 
>and
> have the record length as long as your longest transmission file.  Make it 
>multi
> member
> 3) Create three members in this file, one for each transmission.
> 4) CPYF with *NOCHK the appropriate transmission to the appropriate member.
> 
> John Hall wrote:
> 
> > <<snip>>
> >
> > Sure I use multi member files for some things - Archiving data
> > transmissions by date.  But I have 3 separate transmissions (diff
> > Format) so three files with a member for each date.  The more logical
> > grouping of this would be a separate sub directory for each date with
> > the three files in it.
> >
> 
> +---
> | This is the RPG/400 Mailing List!
> | To submit a new message, send your mail to RPG400-L@midrange.com.
> | To subscribe to this list send email to RPG400-L-SUB@midrange.com.
> | To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
> | Questions should be directed to the list owner/operator: david@midrange.com
> +---
+---
| This is the RPG/400 Mailing List!
| To submit a new message, send your mail to RPG400-L@midrange.com.
| To subscribe to this list send email to RPG400-L-SUB@midrange.com.
| To unsubscribe from this list send email to RPG400-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---