You can remove this user if you have no batch jobs that sign on as
operator.sys HOWEVER,
1. You may want to add a start up user to sysstart, otherwise the system
will attempt to logon as operator.sys and generate an error.
startsess 20;console,user.acct;nowait ;hipri
2. Down the road, if you ever do a restore you will have to use the CREATE
option, and it will be deja user all over again. IMHO, this is a bug that
needs serious attention
3. The next software update or patch may reincarnate this user and others.

It used to be that you could count on a logon UDC with a bye command to
disable a user. (This always had the exception of parm=-1 but you could
simply remove sm from that user). Now days with FTP the best alternative is
to change the user password frequently.

Their are security packages for the HP3000 that address some of these
issues, you may want to seriously look into these as a solution.

TGIF

Mike Hornsby
Co-founder/Chief Technical Officer
Beechglen Development Inc. (www.beechglen.com)
5576 Glenway Ave.
Cincinnati, Ohio 45238

Voice (513) 922-0509

----- Original Message -----
From: "Ted Ashton" <[log in to unmask]>
To: <[log in to unmask]>
Sent: Thursday, January 18, 2001 10:01 PM
Subject: [HP3000-L] Is OPERATOR.SYS necessary?


> Greetings,
>   Can anyone enlighten me as to the necessity of OPERATOR.SYS?  If I
remove it
> from my system, are evil things going to happen?
>
> Ted
> --
> Ted Ashton ([log in to unmask]), Info Sys, Southern Adventist University
>           ==========================================================
> I have hardly ever known a mathematician who was capable of reasoning.
>                         -- Plato (ca 429-347 BC)
>           ==========================================================
>          Deep thoughts to be found at http://www.southern.edu/~ashted