Re: Item with last transaction date

If you specify a logical in the SQL statement and the SQL engine chooses
a different logical, it will still apply the select/omit from the
original logical specified in the SQL statement.

HOWEVER - there is never a good reason to specify a logical in a SQL
statement ! This should ALWAYS be avoided.

There is no need to specify logicals when you need to access the same
file more than once.

Just use...

Select * from CMF CA, CMF CS Where...



-----Original Message-----
From: bpcs-l-bounces+sean.mcgovern=covidien.com@xxxxxxxxxxxx
[mailto:bpcs-l-bounces+sean.mcgovern=covidien.com@xxxxxxxxxxxx] On
Behalf Of Al
Sent: 21 October 2010 22:10
To: 'BPCS ERP System'
Subject: Re: [BPCS-L] Item with last transaction date

IBM OS subtleties include if you specify one logical view, and the OS
finds
ANOTHER logical that it thinks might do the job faster, it will
substitute,
not using the one you specified, so you have to be darn careful that
your
selection criteria is specific, not relying on what's in the logical
view
you chose.

Good reason for specifying logical views is if you need to access more
than
one copy of same file. For example, I might access CMF (cost master)
matching actual and standard costs, one logical for each, naming CA
(actual)
and CS (standard) prefixes, to help my selection criteria keep things
straight.

-
Al Mac