ca.portal.admin

DB Segmentation

Discussion created by ca.portal.admin on Feb 10, 2006
Once again I would like to tap into the vast knowledge pool that is
IDMS-L.

We are considering a major modification to an existing IDMS database.
Due to the growth of the data within IDMS, we are considering splitting
this database into several smaller entities. Example: all customers
whose accounts start with ""1"" go into DB1, accounts that start with ""2""
go into DB2, etc. Some mechanism would be used (system exit or
programmatically) to determine which database is accessed and stored.

Are there any other IDMS shops out there doing something like this?
Would you be willing to discuss this topic with me and let us know the
benefits and pitfalls you are aware of?

Thanks in advance.

Dan Hall
GE
Capital Solutions
Danbury, CT

T 513.217.5060
E dan.hall@ge.com
http://www.ge.com/capitalsolutions/

"
IDMS Public Discussion Forum
IDMS-L@LISTSERV.IUASSN.COM
SMTP
IDMS-L@LISTSERV.IUASSN.COM
IDMS-L@LISTSERV.IUASSN.COM
SMTP








Normal

Normal
Re: DB Segmentation
"Dan,

This is a good example of how the dbname table can be used to
distinguish between physical dbs. The smaller entities would be
segments, and each segment would be referenced by a different dbname,
each segment would be accessed by an execution of the correct mapless
dialog/called program (ADS) or a called program (batch) which uses the
correct dbname, and the driver/main program would just have to know
which program/dialog to call to access the correct segment.

Been there. Done that.

John Wheeler

Outcomes