Can SQL "simulate" a multiple format logical file with a join?

Esteemed listers,

I am experimenting with a multiple format logical file:

     A          R INVOICE                   PFILE( FT320 )
     A** Key                
     A          K INVDIS    
     A          K INVSCH    
     A          K INVSTU    
     A          K INVDAT    
     A          K INVNUM    
     A**--------------------
     A*                     
     A          R PAYMENT                   PFILE( FT310 )
     A** Key                
     A          K PMTDIS    
     A          K PMTSCH    
     A          K PMTSTU    
     A          K PMTDAT    
     A          K PMTNUM    
     A**--------------------

As you may be able to surmise, the two physical files share the same key
structure, and the idea behind this type of logical is that I can just set
lower limits (RPG's SETLL) on District, School, and Student, and read by
key through the filename, and get the invoice and payment records in date
/ number order.  Defined like this, it works very well for my purposes. 
(Just so you know, beyond the key structure, the record formats for these
two physicals are very different.)

Had a loop thrown at me yesterday that essentially requires me to turn
this into a join logical file.  Each format needs to join to another file,
and use one of the joined file's fields as an additional key field, a
FamilyID, inserted before the xxxSTU key field.  Two problems - only
fields from the primary file in a join logical can be a key field, and a
join logical can have only one record format.

Because this multiple format logical is being used to populate a subfile,
I can't build a workfile.  Can SQL do this, so there is always a view /
index available without having to rebuild it each time I want to populate
a subfile?

TIA, GA


        
                
__________________________________
Do you Yahoo!?
Win a $20,000 Career Makeover at Yahoo! HotJobs  
http://hotjobs.sweepstakes.yahoo.com/careermakeover