RE: SQL create a new table by joining two existing PFs - how can I keep attributes of 2nd join file?

Not that I am discouraging you from nulls because I do recommend embracing
them, but you could look at IFNULL or COALESCE. I ONLY mention that
because OPNQRYF doesn't have that leg up on SQL.

http://publib.boulder.ibm.com/infocenter/iseries/v7r1m0/topic/db2/rbafzscacoales.htm
http://publib.boulder.ibm.com/infocenter/iseries/v7r1m0/topic/db2/rbafzscaifnull.htm

We have an (ageist reference removed) gentleman in our department who
would rather split a huge program into two source members and then put
them back again just so he could load it into SEU (too big) than use RDP.
But when he saw how quickly embracing nulls made CPYTOIMPF work better for
a customer who insisted that they not see
...," ",...
but instead see
...,,...
in their comma separated variable file he had no trouble learning how to
use null indicators in RPG. Shot off like a rocket on that ride.

sidenote: It was a vendor written program and it's not our duty to
modularize their code, especially since we plan on staying somewhat
current. Does ORD500 sound familar to some?

Rob Berendt