× 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.


  1.  Home
  2. RPG400-L
  3. October 2011

Re: Referencing SQL Table Alternative Names in a RPG module

On 2011/10/7 1:19 PM, Andy Hautamaki wrote:
In an SQL Table we have descriptive alternative field names that from
what I can see from prior posts you can't refer to them in an RPG
module. (Not using embedded SQL)

In the compile listing for the externally defined file I notice it
doesn't bring them in for the record format so I get the fields not
defined compile error.

Is this just how things are and not something that is even on the radar
to change?


In V7R1, you can specify ALIAS on the D spec of an externally-described DS and then the subfields will have the alternate names instead of the short names.

You can also specify ALIAS on an F spec of any file that won't have I and O specs generated by the compiler (no I/O specs if you specify QUALIFIED, LIKEFILE, or define the file in a subprocedure). Then, if you define a data structure using LIKEREC of one of the file's formats, the subfields will get the alternate names.

As an Amazon Associate we earn from qualifying purchases.

This thread ...
Follow-Ups:
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.