Mike Bayer said:
 
>We are currently in the process of consolidating an HP3000 980/400 and
>an HP3000 980/100 onto a 996/300.  This has raised a heated debate
>between the two development groups that must now share the same box.
>
>One group wants to put all applications into one account, with
>separate groups for each application's data and other accounts for
>each application's run modules (one acct per application), with
>separate groups for each language type.  The main purpose behind this
>approach is to allow all users to have a single sign-on, with each
>individual application accessible from a menu without opening security
>on the data accounts.
>
>The other group wants to have individual accounts for each
>application.  Menus would also be provided to access multiple accounts
>from a single sign-on by playing with file equations and account
>security.
>
>Each option has pros and cons and I am looking for input from anyone
>who has seen an article on this, or has gone through a similar
>exercise.
>
>Thanks ... Mike Bayer
>
Mike,
 
I would recommend separate accounts.  This will ultimately allow you to
break them up into multiple volume sets.  This will provide significant
performance advantage as well as lots of flexibility if you want to
implement something like mirrored disk, which requires user volumes.  If the
menuing system could be made to be transparent to the users, then it's a
"win/win" (do people still say that?).
 
Bill
---
Bill Lancaster         Lancaster Consulting
(541)926-1542 (phone)  (541)917-0807 (fax)
[log in to unmask]       http://www.proaxis.com/~bill