RE: .NET Managed Provider and Multi-member Files

["Fisher, Don" <dfisher@xxxxxxxxxxxxx>]

Scott suggested using ALIAS and I'm experimenting with that now. 

I know which member because I pass the member name as a parameter to the Visual 
Basic program.  The member is created and populated by an RPGIV program.  The 
Visual Basic program retrieves the records and places them into a spreadsheet 
for transmission via e-mail.

That PARTITION keyword seems interesting.  I'll have to read up on it.

Thanks.

Don


-----Original Message-----
From: midrange-l-bounces@xxxxxxxxxxxx
[mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of rob@xxxxxxxxx
Sent: Tuesday, September 19, 2006 2:12 PM
To: Midrange Systems Technical Discussion
Subject: Re: .NET Managed Provider and Multi-member Files


Alias is one option.

How do you make the decision as to which member holds which data?  For 
example if the decision is based on the year of a date field then you can 
recreate the multimember file in sql like the following:
CREATE TABLE ROB/RUMINATE (MYDATE DATE NOT NULL WITH DEFAULT, 
MYSTUFF CHAR (5 ) NOT NULL WITH DEFAULT) 
PARTITION BY RANGE(MYDATE) 
 (STARTING ('2004-01-01') ENDING('2009-01-01') EVERY(1 YEARS))

Each partition is a different member.

Now, I am having an issue with this.  It is thinking I need DB2 Multisystem.  
However since I am not partitioning across node groups I don't see why.

Rob Berendt
<clip>