|
Byron. COBOL copes with this, no problem. In any data definition structure, you have to be sure that the top level of your definitions have unique names. If that is true, you can name the fields within each top level with the same names. This goes for data-files, screens and WORKING-STORAGE definitions. When you refer to a field whos name occurs in several definitions, you have to QUALIFY the field, for example PGMID OF RECORDTYPE-A. The advantage of doing it like this is the possibility to use MOVE CORRESPONDING (look it up in yor manuals). This is basic knowlege for COBOL-programmers. Mvh. Geir Kildal Entra Data AS Norway beasley@alumni.aubu rn.edu To: COBOL400-L@midrange.com Sent by: cc: owner-cobol400-l@mi Subject: dspf DDS names drange.com 13.11.00 15:36 Please respond to COBOL400-L 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.