RE: Hooray!!! DB2 for i adds remote & local support in a single SQL statement!

Sorry, a little too much, I suppose. I have really strong feelings against multi-member files, due to several notable "lessons learned".

My apologies,
-Eric DeLong

-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of rob@xxxxxxxxx
Sent: Friday, July 13, 2012 1:12 PM
To: Midrange Systems Technical Discussion
Subject: RE: Hooray!!! DB2 for i adds remote & local support in a single SQL statement!

Eric,

Personally I love to pontificate also. And, other than source files, I
try to avoid multi member files. However, some software applications have
them. I was just showing how to access them.

But DB2 Multisystem likes to automate partitions. Ok, you may not use
your member name also in a column, or something from which a member name
could be derived. Let's say you have a column name called
Transaction_Date. With DB2 Multisystem installed you could
CREATE TABLE MYTABLE (
Transaction_Date date,
Transaction_Amount decimal(7,2),
Transaction_id integer as Identity)
Constraint MYTABLE.Transaction_id Primary Key
PARTITION BY RANGE(Transaction_Date)
(Starting('2001-01-01') Ending('2099-01-01') EVERY(1 YEAR))
Each partition would be a member.

No OVRDBF needed to access a particular member. DB2 could figure it out.


Rob Berendt