Re: Several subsystems

[Vernon Hamberg <hambergv@xxxxxxxxxxxxxx>]

Maurice

At 11:42 AM 1/28/1998 +0100, you wrote:
>We gonna give a lot of our shareholders access to our AS/400, now the
>customer made a plan to make different subsystems for each shareholder
>who wants access to the system.
>
>Can this cause problems and can someone give me the advantage and
>disadvantage of this solution.
>
>In my opinion the only thing you problem you can get, is a performance
>problem, but therefor there is a solution ;).
>
>The connection will be made through *anynet (netsoftrouter).

Don't know if you have receive any other replies.

What advantage is provided by putting the users in separate subsystems?
What concerns are the users trying to address? Are they concerned about
other customers being able to see _their_ data?

Segregation of data for customers can adequately be provide by using a key
field in tables for each customer. Then segregation is accomplished
programmatically.

If customers are nervous about that approach, then give them separate
libraries and use library lists according to some customer number. This may
give them the comfort level they need. You end up with multiple copies of
the same table, but each will be smaller. You'd probably benefit from a
change management system to control all this.

HTH

Vernon Hamberg
Systems Software Programmer
Old Republic National Title Insurance Company
400 Second Avenue South
Minneapolis, MN  55401-2499
(612) 371-1111 x480


+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---