DB2 LUW v8.2 FP 14  RHAS 2.1

Sorry if these are newbie questions.  Optimizer stuff is black magic
to me.  For both of these, assume stats are current and an even
distribution of data.
-------------------------
Lets say I have a table FOO1 that has, among other columns, a column
named A.  There is a non-unique index on A that has medium selectivity.
Lets also say I have a table FOO2 that has, among other columns, a
column named B.  There is a non-unique index on B that has medium
selectivity.

Now I create a view thusly:

create view c (col1,col2,col3,etc..) as
select A,another col,another col,another col,...
from FOO1
union
select B,another col,another col,another col,...
from FOO2

If I then query this view like:
select * from c where col1 = 'SOME VALUE'

Is the DB2 optimizer smart enough to query FOO1 using the index,
then query FOO2 using the index, then "glue" the results together?
Or does it have to select /all/ rows in FOO1 and FOO2, create a
temp table of sorts, then do a table scan (or build an index itself)?
---------
Another one:  Lets say I have a table FOO1 that has, among other
columns, a column named A and a column B.  There is a medium selectivity
non-unique index on A and a /separate/ non-unique medium selectivity
index on B.

If I then query FOO1 like:
select * from foo1 where a = 'SOME VALUE' and b = 'ANOTHER VALUE'

Is the DB2 optimizer smart enough to query FOO1 using the A index,
then separately query FOO1 using the B index, then do an "intersection"
of the results?   Or must I have a /single/ non-unique composite index
based on A and B together?

TIA

aj