DB2 would allow you to do this in a single or multiple
regions. OS/390 will allow you to do this in a single
or multiple LPARs.
A major factor to consider are the service level
agreements and chargeback you have with the other
companies, as well as the relationship between the
companies' staffs (friendly or adversarial). As long
as you're only dealing with a couple of outside
companies, I'd recommend a separate region for each
company. Especially test regions. You're company
probably isn't going to want to take an outage on its
region, because you have to bounce DB2 for the other
company. When it's time to upgrade, how hard will it
be to get both company's to support the upgrade on the
same date? What if the other company's apps fail
after an upgrade and it has to be rolled back?
Do both companies use the same quality assurance
procedures? What if one company has an app that runs
a long time without commits? Will it effect any
system wide utilities needed by the other?
Yes, these are the same issues you deal with now
between different departments, but there is usually
ONE person somewhere up the management chain who can
make a decision. With multiple companies, you'll be
dealing with several bosses.
Due to mostly political factors, and assuming they
aren't sharing any data between apps,
I'd go with multiple regions. Except for weekend
upgrades, I've found it a lot easier to put each
political organization in their own region. I spent
WAY too much time trying to coordinate different
companies scheduling needs, than actually doing the
extra support required by having extra regions. I'd
even stick them in their own LPAR if I had the
--- "Philip, Sibimon" <[login to unmask email]> wrote:
> With happy new year to everyone, let me start my
> first question this year.
> We are trying to support multiple companies data in
> our OS/390 and DB2. I am
> sure that somebody in this list might be doing this
> already. My questions is
> 1. How do you separate one companies data from
> 2. Do you use separated subsystem of for each
> company or multiple table with
> same name but with different schema/owner.
> 3. How do you manage the programs, since there is
> some customization
> required for some company.
> I just started thinking about this, so any
> additional information on this
> will be helpful.
> To change your subscription options or to cancel
> your subscription visit the DB2-L webpage at
owners of the list
Do You Yahoo!?
Send FREE video emails in Yahoo! Mail!