RE: Field names in SQL-generated files

We are using Aldon 7.5A. I don't know if that is the most current version or not.

It handles SQL tables pretty well. When we have issues it is with a developer not following the rules for adding the table to the CMS.

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-
bounces@xxxxxxxxxxxx] On Behalf Of mgarrison@xxxxxxxxxx
Sent: Thursday, August 23, 2012 9:00 AM
To: Midrange Systems Technical Discussion
Subject: RE: Field names in SQL-generated files

Rick,

Would you mind sharing what change management system you are using?
Do you feel that it handles SQL DDL well?

We will be switching from DDS to DDL table creation soon and have not yet
tackled how our CMS deals with DDL created table definitions.

Thanks,
Mike Garrison

Rick Chevalier wrote on 08/23/2012 08:23:19 AM:

From: <Rick.Chevalier@xxxxxxxxxxxxxxx>
To: <midrange-l@xxxxxxxxxxxx>,
Date: 08/23/2012 08:35 AM
Subject: RE: Field names in SQL-generated files Sent by:
midrange-l-bounces@xxxxxxxxxxxx

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

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