|
In Cobol you can always QUALIFY a field name that is used in more than one place (fieldname IN recordname or fieldname OF recordname). I use the same name in files, multi-format screens, etc. Then I use move CORRESPONDING from/to screens/files/etc. You sometimes have to check your compile listings to make sure this moves all the fields you needed and not any of the ones you didn't want to move. Hope this helps. > -----Original Message----- > From: owner-cobol400-l@midrange.com > [mailto:owner-cobol400-l@midrange.com]On Behalf Of > beasley@alumni.auburn.edu > Sent: Monday, November 13, 2000 8:37 AM > To: COBOL400-L@midrange.com > Subject: dspf DDS names > > > > The COBOL programers here say they cannot use the same field name such a > PGMID on each record format in the DDS. Certain fields are the same on > each record format. They say each use must be renamed with an alias or > COBOL will error. I have never had a problem with it using RPG. > > Is the true? Do you have examples of code showing a better way than using > an alias for the same field on mutiple formats withing the same display > file? > > Thanks > Byron Beasley > > +--- > | This is the COBOL/400 Mailing List! > | To submit a new message, send your mail to COBOL400-L@midrange.com. > | To subscribe to this list send email to COBOL400-L-SUB@midrange.com. > | To unsubscribe from this list send email to > COBOL400-L-UNSUB@midrange.com. > | Questions should be directed to the list owner/operator: > david@midrange.com > +---END > +--- | This is the COBOL/400 Mailing List! | To submit a new message, send your mail to COBOL400-L@midrange.com. | To subscribe to this list send email to COBOL400-L-SUB@midrange.com. | To unsubscribe from this list send email to COBOL400-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---END
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.