I am trying to get a handle on OI.

First, I understand that SYSPROG is the closest thing to God in AREV and OI.

Second, In AREV, we can have more than one user access a common bunch of files in the SYSPROG account(application) and this is controlled by VOC and the group .environment file. (as well as password and username).

Third, I want to maintain the integrity of the Application name and allow all users, if possible, to log in and only access and only their files(ok, tables).

Fourth, When I am testing OI I notice that only one user, or so it seems, can access a given application.

My question is: "Do I create a separate 'application' for each user and give him a common default inheritance of similar users?"

All responses will be showered with joy by the bluebird of happiness.

Dale

Dale..the only really stupid questions are the ones you don't ask .. so…

In AREV / OI, SYSPROG is the system programmer's account. Generally, user applications don't go there. From SYSPROG, you create an application with a name. Under that name, you may define allowable users of that application. However, in OI, this doesn't get deployed too well so…

Tables (files) are either owned by the Account/Application or by the special account GLOBAL, in which case they may be attached by any account/user. The problem comes when creating the table itself. In AREV, you create all tables in the account that owns them. You can use the RENAMETABLE or RENAME command to assign the table to the GLOBAL account. Do this before fiddling with indexing or you'll have to remove all indexing first. Tables that are unique to a single account will only be directly accessible from that account or via an alias (perhaps with a password). It's not really the VOC entry that controls the table, but the entities in the REVMEDIA.LK/OV table for the volume.

So, make your multi-account shared tables owned by GLOBAL. Keep your application specific tables in the named account.

Don Miller

C3 Inc.

Thanks, I appreciate your advice.

Dale

As a beginner in OI, I may be completely off the beam, but isn't inheritance an answer to this problem.

It would be possible to have all the 'multi-account' files in accounts

which are inherited, and any local application specific files in the local account.

You would the have an account 'structure' - e.g.

  SYSPROG

  Shared account

  Local account(s)

     where the local accounts would inherit from sysprog and the

shared account

View this thread on the forum...