RE: SQL Triggers and Multiple Member Database Files

["Dave Odom" <Dave.Odom@xxxxxxxxxxxx>]

Charles,

You wrote in part:

"...While the ALIAS command does know about members and ALIAS an ALIAS
can be used to allow the other SQL commands access to a particular
member, I think it's fair to say that SQL doesn't have any concept of
multiple members.  Certainly the RDBMS itself does, but SQL does not.

Interesting, in v5r3....IBM has added support for partitioned tables. 
How are these supported?  Via multi member physical files!

http://publib.boulder.ibm.com/infocenter/iseries/v5r3/ic2924/index.htm?info/dbmult/partitionedtables.htm


But SQL accesses the data as if it was all in the same member.

HTH,

Charles Wilt
iSeries Systems Administrator / Developer
Mitsubishi Electric Automotive America
ph: 513-573-4343
fax: 513-398-1121"

This is all part of what I've been saying... that the iSeries OS is not
a true RDBMS.  In real RDBMS's, such as the real DB2s and Oracle, they
don't support Multiple Member Database files.  If an application is
based on such an old file architecture(IMS is guilty here as well) the
Relational standard is to RE-ARCHITECT to Relational form.  That is,
TABLES, not files, and normalize the multiple members of the legacy
architecture to however many tables are necessary for proper relational
architecture.    Then standard SQL will work without all the work
arounds.   

The bottom line is, if you want the normal concepts, features and
functions of standard SQL and DB2 to work as they do in the other true
RDBMSs, then do as they do;  re-architect your databases and
applications in DB2/400 like the rest.  

Take care,

Dave Odom
Arizona