X-no-Archive:yes
Interesting question!

Doug Becker's solution to strip it of capabilities might remove some points
of trouble, such as the ones Mike Hornsby warns of.

I probably have OPERATOR.SYS and OP muddled in my thinking. Backups come to
mind; what would backups run under? Ours run under OPERATOR.SYS; without
that, I would think you would have to use MANAGER.SYS, or have account-based
backup jobs whose users have AM. I think anyone with OP can store and
restore any file, anywhere. I would expect this still to be true of an
OPERATOR.account who has OP, which seems like a bad thing, I think.

Now, OP grants some device management functions, which I guess can be
handled by whoever is at the console, and whoever is associated with a
printer in the ASOCTBL (which had worked for us for application printers).

I am curious to know what is gained by removing it.

Greg Stigers
http://www.cgiusa.com