Depending on what commands you want them to have, some ideration of ALLOW
would probably be able to accomplish what they need. ALLOWing their own
personal accounts and/or logons.

James

-----Original Message-----
From: HP-3000 Systems Discussion [mailto:[log in to unmask]]On
Behalf Of Tom Hula
Sent: Monday, October 11, 1999 9:31 AM
To: [log in to unmask]
Subject: Limiting Operator Access


Our shop basically doesn't have an operator, per se.  Everyone goes in
and out of the computer room to get reports, print forms.  Occasionally,
I have a problem with the nightly backup where the tape drive burps and
won't load a tape properly or perhaps someone will accidentally unload
the backup tape or (most rarely) the person loading the tape may have
the read/write tab set the wrong way.  The net affect is that people
begin to arrive in the morning and they can log on but they can't do
anything because store has all the files locked up waiting for a tape.

Now, this would not be a huge problem if they would just call me
immediately to have me take care of the problem.  Unfortunately, a
few of them know just enough MPE to get them into trouble, like the
LIMIT command, for instance.  Their attempts to "fix" the problem
just end up creating more problems for me.  And anyway, I don't want
end user type people taking it upon themselves to fool around with
system parameters like that.

Now, most people can't even get to the MPE prompt, since I use
Vesoft security and menus.  The problem is really the operator
console.  They need access to it to print forms, so I would like
to limit access to certain commands that I know are a problem.

I know I could set up a system-wide udc command to dummy out the
commands I want to limit access to.  It seems like there was then a
simple way to get around this so I can have access but I don't recall
what it was.  Could someone please remind me?
        Tom Hula
        Victor S. Barnes Company