|
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?) _______________________ Booth Martin boothm@earth.goddard.edu http://www.spy.net/~booth _______________________ Jim Langston <jlangston@conexfreight.com> Sent by: owner-rpg400-l@midrange.com 01/05/2000 06:05 PM Please respond to RPG400-L To: "RPG400-L@midrange.com" <RPG400-L@midrange.com> cc: Subject: Dual Format Our bank wants us to send them a file with all our check information. Their file layout is a dual file layout, with a control record and a detail record (their program that reads this is obviously a COBOL program since they describe the length and such as PICTURE like 9(08)V99). I am trying to decide the best way to do this. I was hoping to be able to get away with creating two files, one for the header and one for the detail, then just copy them to one file before I transmitted it, but now I see I am going to have to create many header records. I don't like the thought of back stepping and doing it S36 style with file described files either. I was thinking about a multi-format logical, but there are not unique fields in the files to be able to key them on. I think I am going to have to open up the 2 files I created with DDS just for the record layouts, then do some type of overlay to get the record layout into the fixed length field of the un-DDSed file (the one I will be writing too). Can anyone think of a better way? If not, could someone give me an example of how to do what I am trying to do? That is, over lay the 40 bytes of my DDS to another field. The DDS is externally described, so is not in my program itself. I am dealing with a small number of fields, 7 in each of the header and details. Regards, Jim Langston +--- | 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 +---
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 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.