Re: V5R3 and logical files

HTH
Vern

At 03:24 PM 5/9/2005, you wrote:

We just upgraded to V5R3 and we are having trouble with a couple of
queries that are using a logical file (which is a separate topic) that has
RENAMEd fields in it.  If we remove the RENAMEs from the *LF, the query
works OK.  These queries have always worked well; this is the first time
they fail.

Message . . . . :   Field ITNBR not found in file *N in *N.
Cause . . . . . :   Field ITNBR from query format @HISTIF could not be
found
  in file *N in library *N format *N join reference 0.  If the file name
is
  *N, the field was not found in either the query record format or the
queried
  file formats. If the file name is *FUNCTION, the file was user-defined
table
  function *N in library *N.

Physically, the field is ITNBR but in the logical is RENAMEd to AAA123.

Any reasons why I have this with V5R3?

TIA,

Peter Vidal
PALL Corporation / SR Programmer Analyst, IT Development Group
10540 Ridge Rd., Ste 203, New Port Richey, FL 34654-5111
http://www.pall.com

"Courage is the strength or choice to begin a change. Determination is the
persistence to continue in that change."
-- Anonymous --
--
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.