HP 3000 Manuals HP 3000 Manuals
Allowing Session and Job Names
HP SRC allows administrators to add users to an environment that includes
the session or job name. Session names are significant only if they are
defined in the SRC environment. If user.account and session,user.account
are both added to an environment, users accessing the environment without
different session names will have the capability of user.account, and
users accessing the environment with the added session names will have
the capability specified when the names were added. Therefore, once an
administrator has added all the users with session names, the
user.account without a session name should be removed.
Unless a system has been implemented to ensure that people do not logon
with a session name other than their own, a recommended practice is to
give all session names for the same user.account the same security class.
This is recommended because MPE XL allows users to adopt someone else's
session name.
You can specify a session name in the USER parameter for the ADDUSER,
CHGOWNER, CHGUSER, and DELUSER commands, or in the AUTHOR parameter for
the LISTREV command. If you specify a session name, your parameter must
be enclosed in quotes. This is because the UDC mechanism sees, for
instance, KEITH,MGR.HPSRC as two parameters, but sees "KEITH,MGR.HPSRC"
as one parameter.
Below is an example of how you can add a user with a session name and
change a user without one. (In the first line, you could use either
double or single quotation marks.)
ADDUSER "KEITH,MGR.HPSRC", LIBRARIAN
CHGUSER MGR.HPSRC, READER