RE: Field names in SQL-generated files

James,

It looks like most of the posts have pointed you to iSeries Navigator. In our shop we have to have the source code for our table in a change management system. Because of that, and for consistency, we created a shell create table source member that we can use to get us started. It addresses the long/short name issue for both the columns and the table itself. There are examples of check and referential constraints in case those are needed and a primary key constraint. Our CMS doesn't seem to like the RCDFMT keyword so we handle that a little differently.

I have posted the code at http://code.midrange.com/6bf5865470.html . Maybe it will help.

Rick

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of James Lampert
Sent: Wednesday, August 22, 2012 7:33 PM
To: Midrange Systems Technical Discussion
Subject: Field names in SQL-generated files

We've got an SQL jock with little or no AS/400 experience developing an
entirely SQL-generated database for us (and in fact, that script that was
giving us trouble recently was part of it -- I passed along the answers, and he
was able to get the script working; thanks!).

At any rate, we're getting (not unexpectedly) SQL field names coming up as
column headings, looking at the file in QuestView. and generated
AS/400 native field names appearing wherever the SQL field names exceed
10 characters.

Is there a way to specify both the AS/400-native and SQL-native field names
when creating the file? And what about specifying an AS/400-native filename
when the SQL-native filename exceeds 10 characters?

I know about "LABEL ON" for column headings; I've used it in my own SQL
scripts

--
JHHL
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe,
unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
a moment to review the archives at http://archive.midrange.com/midrange-
l.

Privileged and Confidential. This e-mail, and any attachments there to, is intended only for use by the addressee(s) named herein and may contain privileged or confidential information. If you have received this e-mail in error, please notify me immediately by a return e-mail and delete this e-mail. You are hereby notified that any dissemination, distribution or copying of this e-mail and/or any attachments thereto, is strictly prohibited.