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
pnelson@braxton-reed.com
----- Original Message -----
From: "Paul Tuohy" <tuohyp@attglobal.net>
To: <midrange-l@midrange.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