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



It's not currently possible now since I-Specs don't support long names.

But it was pointed out during a presentation on RPG @ v6r1 that the new features in v6r1 are paving
the way for an i-specless program and therefore open the door to using the longer DDS/SQL Alias names
in the future.

HTH,

Charles Wilt
Software Engineer
CINTAS Corporation - IT 92B
513.701.1307

wiltc@xxxxxxxxxx


-----Original Message-----
From: rpg400-l-bounces@xxxxxxxxxxxx [mailto:rpg400-l-bounces@xxxxxxxxxxxx]
On Behalf Of RNewton@xxxxxxxxxxxx
Sent: Monday, February 25, 2008 1:42 PM
To: RPG programming on the AS400 / iSeries
Subject: Externally Described DS with SQL Column Names

Hi all,

I have this craving to use the longer SQL column names in my externally
described datastructures. It will make coding much more efficient when the
field names are self describing. Plus I use the intellisense feature in
WDSc (ctrl+space with the outline built) and this would really be handy in
combination with that tool. Then again, if the intellisense feature would
include the description of the fields this would not bug me as much. Oh,
and while I'm on it... why should we have to create the outline. That
thing
takes days to build when I have a few eds's in my program! Couldn't it run
as a background process always updating as you make changes to your
program?

So, does anyone know any tricks I can perform on my D spec to get the SQL
names rather than the 10 position ones?

Below is an example of what I am talking about:

d extFile e ds extname(myFile) qualified inz

/free
exec sql
SELECT f.myLongSQLFieldName
INTO :extFile.MYLSQLFNAM <--- this is ugly
FROM myFile as f;
/end-free

I would much rather be able to:

d extFile e ds extname(myFile) qualified inz

/free
exec sql
SELECT f.myLongSQLFieldName
INTO :extFile.myLongSQLFieldName
FROM myFile as f;
/end-free


Thanks in advance for any insight,
Robert Newton
EDPS
Electronic Data Processing Services
Software Engineer
rnewton@xxxxxxxxxxxxxxxxx

This communication is confidential and is intended to be privileged. If
there is a problem with this transmission, please contact the sender. If
the reader of this message is not the intended recipient, or the employee
or agent responsible to deliver it to the intended recipient, you are
hereby notified that any dissemination, distribution or copying of this
communication is strictly prohibited.

--
This is the RPG programming on the AS400 / iSeries (RPG400-L) mailing list
To post a message email: RPG400-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/rpg400-l
or email: RPG400-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/rpg400-l.




This e-mail transmission contains information that is intended to be confidential and privileged. If you receive this e-mail and you are not a named addressee you are hereby notified that you are not authorized to read, print, retain, copy or disseminate this communication without the consent of the sender and that doing so is prohibited and may be unlawful. Please reply to the message immediately by informing the sender that the message was misdirected. After replying, please delete and otherwise erase it and any attachments from your computer system. Your assistance in correcting this error is appreciated.

As an Amazon Associate we earn from qualifying purchases.

This thread ...

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.