The answer on number of concurrent sessions was addressed
and this information points to the number of users that
can be created.
It appears to be the limit of UID kept in the database of
HPUID/HPUIDNX files. On the test box running MPE/iX 6.0
the file existed with 10000 entries available. Perhaps
the file could have a larger file limit placed upon it,
but a quick check revealed no obvious sources to the answer.
Since UID's cannot be shared among different users (see
example below CIERR808), it stands to reason that this file
does define the system limit for users on an HP3000.
The related files HPGID/HPGIDNX also have a default of
10000 on this system. I cannot imagine exceeding the limits
of GID before UID would be exhausted. (more than one account(?)
without an associated user(?)(logic says no since you must
specify the account manager user on an account) or a user
assigned to more than one group). There are 42 accounts
defined on this system on the MPEXL_SYSTEM_VOLUME_SET and
42 entries in the HPGID file.
To exercise the point with a brief script, after the creation of
9888 users in a TEST Account, MPE/iX returned from a NEWUSER
command:
:newuser mytester
User database (HPUID.PUB.SYS) internal error. (CIERR 818)
:newuser mytester;uid=10000
Duplicate UID in User database (HPUID.PUB.SYS). (CIERR 808)
:pxutil
MPE/iX PXUTIL A.00.02 Copyright (C) Hewlett-Packard 1991. All Rights
Reserved.
PXUTIL> version
UID DATABASE:
HPUID.PUB.SYS Version: A.01.00
HPUIDNX.PUB.SYS Version: A.01.00
Valid Records: 10000
Uid Counter: 10162
GID DATABASE:
HPGID.PUB.SYS Version: A.01.00
HPGIDNX.PUB.SYS Version: A.01.00
Valid Records: 42
Gid Counter: 163
PXUTIL> exit
:listf [log in to unmask],2
ACCOUNT= SYS GROUP= PUB
FILENAME CODE ------------LOGICAL RECORD----------- ----SPACE----
SIZE TYP EOF LIMIT R/B SECTORS #X MX
HPUID * PRIV 1242W FB 10000 10000 1 97040 51 *
HPUIDNX * PRIV 2W FB 10000 10000 1 160 2 *
:purgeacct gmstest
ACCOUNT GMSTEST TO BE PURGED? (YES/NO)yes
:listf [log in to unmask],2
ACCOUNT= SYS GROUP= PUB
FILENAME CODE ------------LOGICAL RECORD----------- ----SPACE----
SIZE TYP EOF LIMIT R/B SECTORS #X MX
HPGID * PRIV 42W FB 42 10000 1 256 1 *
HPGIDNX * PRIV 2W FB 42 10000 1 144 1 *
HPUID * PRIV 1242W FB 10000 10000 1 97040 51 *
HPUIDNX * PRIV 2W FB 10000 10000 1 160 2 *
:newuser mytester;uid=10000
:purgeuser mytester.
USER MYTESTER TO BE PURGED? (YES/NO)yes
:listf [log in to unmask],2
ACCOUNT= SYS GROUP= PUB
FILENAME CODE ------------LOGICAL RECORD----------- ----SPACE----
SIZE TYP EOF LIMIT R/B SECTORS #X MX
HPGID * PRIV 42W FB 42 10000 1 256 1 *
HPGIDNX * PRIV 2W FB 42 10000 1 144 1 *
HPUID * PRIV 1242W FB 10000 10000 1 97040 51 *
HPUIDNX * PRIV 2W FB 10000 10000 1 160 2 *
:pxutil
MPE/iX PXUTIL A.00.02 Copyright (C) Hewlett-Packard 1991. All Rights
Reserved.
PXUTIL> version
UID DATABASE:
HPUID.PUB.SYS Version: A.01.00
HPUIDNX.PUB.SYS Version: A.01.00
Valid Records: 111
Uid Counter: 10162
GID DATABASE:
HPGID.PUB.SYS Version: A.01.00
HPGIDNX.PUB.SYS Version: A.01.00
Valid Records: 41
Gid Counter: 163
PXUTIL> exit
:
HPGID/HPUID entries do not seem to get removed on PURGEUSER/PURGEACCT
commands. The UID/GID counters do not get reset either.
The following excerpt from www.hpdocs.com:
New Features of MPE/iX: Using the Hierarchical File System
Managing Accounts, Groups, and Users
Setting Up Group and User Databases
The UID and GID databases are a required part of any operating system that
implements POSIX standards. These databases contain user identities to
authorize user and system interaction.
User ID database (UID) in HPUID.PUB.SYS and HPUIDNX.PUB.SYS
Group ID database (GID) in HPGID.PUB.SYS and HPGIDNX.PUB.SYS
The databases are automatically created when you install or update to MPE/iX
Release 4.5 or later. The databases are privileged files whose contents are
not visible. As system manager, you need to be aware of their existence.
MPE/iX requires that all processes have an associated UID and GID. Each user
is assigned a unique user ID (UID) which the system maintains. When a user
logs on, MPE/iX uses the authenticated user.account logon string to query
the databases for the UID and GID. The IDs are stored in a run-time process
table.
If no entry is found in the UID database, MPE/iX checks whether the user has
SM capability. If the user does not have a UID and does not have SM
capability, the user cannot log on to the system.
(end of excerpt)
Hopefully that information is useful.
Greg Skvorak
Beechglen Development, Inc.
----- Original Message -----
From: "Paveza, Gary" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Tuesday, March 13, 2001 12:18 PM
Subject: Re: Number of MPE Users on a System.
> On my 6.0 system (unlimited user license), the se(ssion) parameter in
SYSGEN
> can be configured to 3010. Of course, this does not take into
consideration
> any practical limits based upon application performance.
> -------------------------------------------------------------
> Gary L. Paveza, Jr.
> Production Support Analyst - Lead
> (302) 761-3173 - voice
> (877) 720-2970 - pager
>
> -----Original Message-----
> From: Mark Landin [SMTP:[log in to unmask]]
> Sent: Tuesday, March 13, 2001 12:02 PM
> To: [log in to unmask]
> Subject: Re: [HP3000-L] Number of MPE Users on a System.
>
> On Tue, 13 Mar 2001 09:00:42 -0600 (Central Standard Time),
> "Reynolds,
> James" <[log in to unmask]> wrote:
>
> >Greetings folks.
> >
> >This tired old mind has forgot.. How many Users can you configure
> on a
> >system. Just to make it clear, I am talking about MPE Users..
like
> >Operator.Sys...
> >
>
> James,
>
> Why don't you just create a dummy account, and then write a job
that
> creates random users inside it until it fails? Then you would
know.
> :)
|
