× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.




On 28/09/2009, at 6:18 PM, David FOXWELL wrote:


Although, I realise the limitations of this. I can't use EVAL-CORR while I have this kind of prefix.

You can use PREFIX creatively on both the file definition and the data structure definition to remove the first character from the field name. Used in conjunction with QUALIFIED data structures you should be able to use EVAL-CORR quite happily.


What kind of field naming standards are you using in DDS?


I generally use a 2-character file prefix with up to 8 characters for the field identifier itself. I also specify a meaningful ALIAS for SQL access. Six character field names (as in your convention) are no longer needed with RPG IV.

The only reason for the prefix is RPG's insistence that each field name refers to a single storage location. Languages that support qualification (e.g., COBOL and C) don't need this sort of work around.

If I only used SQL for data access I would drop the prefix. If I only had to code for VRM540 and above I would probably drop the prefix and use PREFIX to map file field names to qualified data structures.

Regards,
Simon Coulter.
--------------------------------------------------------------------
FlyByNight Software OS/400, i5/OS Technical Specialists

http://www.flybynight.com.au/
Phone: +61 2 6657 8251 Mobile: +61 0411 091 400 /"\
Fax: +61 2 6657 8251 \ /
X
ASCII Ribbon campaign against HTML E-Mail / \
--------------------------------------------------------------------




As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.