Interesting that they added the ALIAS to facilitate query tools. Surely the TEXT keyword would have been far more useful. Not on my iSeries right now, but know for sure that it is the TEXT that displays in QUERY, and not sure for SQL. ----- Original Message ----- From: "Paul Nelson" <email@example.com> To: <firstname.lastname@example.org> Sent: Sunday, January 06, 2002 6:20 PM Subject: Re: V5R1 Printer File CPD5237 Problem (was: What's this all about?) > I understand what you're saying, but this file was not created with SQL. It > was created with DDS and compiled. The alias keywords were added to > facilitate use with query tools. The irritating thing is that I was just > trying to recompile a printer file, for crying out loud. > > I guess I'll stick to the systems management stuff and leave the programming > (and all the extra keying) to you youngsters who can type faster than those > of us who are "digitally challenged". :-))) > > Paul Nelson > Braxton-Reed, Inc. > 877-777-2729 Office > 630-327-8665 Cell > 708-923-7354 Home > email@example.com > ----- Original Message ----- > From: "Paul Tuohy" <firstname.lastname@example.org> > To: <email@example.com> > Sent: Sunday, January 06, 2002 5:20 PM > Subject: Re: V5R1 Printer File CPD5237 Problem (was: What's this all about?) > > > > Paul, > > > > Please, don't go back to internal definitions. As Robin said, you should > be able > > to override the ALIAS in the print file. > > Also, as Robin said, this is the way it has always worked. But in the > past, we > > never bothered defining an ALIAS for a field unless our application was > using > > Cobol (since RPG only allowed six character field names it wasn't even > using the > > full ten allowed in DDS, so why bother with ALIAS). > > > > The difference now is SQL. When you create a file with SQL the Column Name > is > > the Alias and the Internal Field Name is the Field name we would define in > DDS. > > > > SQL is getting there but it still has a little way to go - maybe with V5R2 > :-) > > > > Paul Tuohy > > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@midrange.com > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l > or email: MIDRANGE-Lfirstname.lastname@example.org > Before posting, please take a moment to review the archives > at http://archive.midrange.com/midrange-l. >
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.