|
I understand the concept, and this is what I wanted to do, I am just not sure how to implement it. My file definitions for my DDS will have the various record layouts externally described. Then I can use this DDS, my concern is, how do I get the buffer I have just written to single field for the actual physical file itself? For example, my header record has 7 fields, UCACCT, UCBRCH, UCCCNT, UCDATE, UCAMNT, UCFILL and UCCODE. My physical file will have one field, maybe I'll call it UBBUFF. I can't say MOVEL UBCntrol01 UBBUFF can I? UBCntrol01 being my record format name for the header DDS. Do I have to create a Data structure listing all my fields in my program? If so, it would be just as easy to internally describe the file then. I don't want to have to list the fields in my program. Regards, Jim Langston Billy Rowe wrote: > boothm@earth.goddard.edu wrote: > > > > I wonder if it would work to have two externally described data > > structures, one for each record type. Then have the physical file itself > > have one field only, which is long enough for the longer data structure. > > > > At the moment before writing the record you could then Movel the data > > structure to the record's long field? (Am I correct in saying MOVEL? Eval > > won't do a move left will it?) > > Yes this will work and also you can write your data structure to the > file by > placing the name of the data structure in your write statement(look at > the write > op code). > > I do this for clients that require multiple record types in files I send > to > them(i.e. Headers,details,trailers) > > Billy +--- | 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 +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.