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

Paul Nelson wrote:

> That was it! The new version of their application software has the files
> compiled with ALIAS in the DDS.
> Still sounds like an OS bug to me. I shouldn't have to find umpteen
> identical fields in the FRF for my REFFLD statements.
> Back to the future with internal definitions.
> Sigh
>
> 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 4:15 PM
> Subject: Re: V5R1 Printer File CPD5237 Problem (was: What's this all about?)
>
> > Hi Paul,
> >
> > The chances are that it is an Alias that is causing the problem. If the
> field
> > reference file was defined using SQL this will almost surely be the case.
> Do a
> > DSPFFD of OPFDTL and see if OFQNTY has an alias. Don't know if you can
> assign
> > the ALIAS keyword in a PRTF, but you can give it a try.
> >
> > HTH
> >
> > Paul Tuohy
> >
> > Paul Nelson wrote:
> >
> > > It looks like this, with apologies for my copy/paste. I just tried it
> again,
> > > and the second reference to the OFQNTY field causes the message. Goin'
> back
> > > to good ol' internal definitions.
> > >
> > >  A*================================================================
> > >  A          R DETAIL
> > >  A                                                       TEXT('DETAIL
> ACCT
> > > GROUP')
> > >  A                                                       SPACEA(001)
> > >  A            O#PONO        R              1REFFLD(OEPONO OEPOMS)
> > >  A                                                     7'-'
> > >  A            O#POSQ             7  0      8
> > >  A            O#ORQTY      R            16REFFLD(OFQNTY OFPDTL)
> > >  A            O#CHGQTY   R            29REFFLD(OFQNTY OFPDTL)
> > >  A            O#TOTQTY      11  4    42EDTCDE(3)
> > >  A            O#C8QTY         11  4    55EDTCDE(3)
> > >  A            O#UNMS        R            68REFFLD(OFUNMS OFPDTL)
> > >  A            O#ITDS           R            72REFFLD(OFITDS OFPDTL)
> > >  A            O#POD1          R  -25    98REFFLD(OEPOD1 OEPOMS)
> > >  A            O#OFSYCD       9  0   134EDTWRD('0   -   -   ')
> > >  A            O#LCDATE       8  0    146EDTWRD('  /  /    ')
> > >
> > > Paul Nelson
> > > Braxton-Reed, Inc.
> > > 877-777-2729 Office
> > > 630-327-8665 Cell
> > > 708-923-7354 Home
> > > pnelson@braxton-reed.com
> > > ----- Original Message -----
> > > From: "David & Eileen Keck" <bstars@optonline.net>
> > > To: <midrange-l@midrange.com>
> > > Sent: Sunday, January 06, 2002 2:47 PM
> > > Subject: Re: V5R1 Printer File CPD5237 Problem (was: What's this all
> about?)
> > >
> > > > Paul,  The following compiles fine on V5R1, so the field reference
> file
> > > may
> > > > not be your problem (PTF's aside).
> > > > A            @FLDA     R           1  2REFFLD(FLDA LIB/REFFIL)
> > > > A            @FLDB     R           1  2REFFLD(FLDA LIB/REFFIL)
> > > > The error message you receive indicates the same field name is
> specified
> > > in
> > > > the same record format starting in pos 19.
> > > > Can you post the record format code ?
> > > > -Dave K.
> > > >
> > >
> > > _______________________________________________
> > > 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-L-request@midrange.com
> > > Before posting, please take a moment to review the archives
> > > at http://archive.midrange.com/midrange-l.
> >
> > _______________________________________________
> > 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-L-request@midrange.com
> > Before posting, please take a moment to review the archives
> > at http://archive.midrange.com/midrange-l.
> >
> >
>
> _______________________________________________
> 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-L-request@midrange.com
> 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.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2022 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.