|
>Date: Fri, 02 Jun 2000 14:38:56 +0200 >From: Anton Gombkötö <Gombkoetoe@ASsoft.com> > ... >3.2 Chapter 13. Control Specifications > ... there are three different ways in which this information > can be provided to the compiler and the compiler searches > for this information in the following order: >1. A control specification included in your source >2. A data area named RPGLEHSPEC in *LIBL >3. A data area named DFTLEHSPEC in QRPGLE > ... The data areas seem like a good way to get H spec keywords in every program, but I strongly recommend against using the data areas. The reason is that if you have one program that needs some special option (like ALTSEQ), you have to code the H spec, and the data area won't get picked up. Now that the H spec can be on several lines, I recommend putting general keywords in one /COPY file that is copied into every program. It's a pain to get the /COPY into all the source, but you only have to do it once. Barbara Morris +--- | 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.