Dan Hollis ([log in to unmask]) wrote:
<< included PM access to MPE freeze, unfreeze snipped >>
: Any non-priv modes? If not, any reason why?
 
One common reason for requiring PM to access interfaces is that,
if misused, they can have a negative impact on either system
integrity or system performance (or both).  MPE in general is
much more conservative in the capabilities granted to a
"average" (non-"superuser") user (really programmer) than
HP-UX is.
 
In particular, freezing a program into memory will improve
the performance of that program at the cost of degrading
the overall performance of the rest of the system.  (To
everyone else, you're now running on a system with less
memory, and memory is a critical component of MPE performance).
You are already aware of this, and are willing to make the
tradeoff.  The PM requirement provides some protection that
programmers who don't understand this tradeoff are less
likely to shoot themselves in the foot.
 
: -Dan
--
-----------------------------------------------------------------
Mike Yawn                            email       [log in to unmask]
Hewlett-Packard                      HPDesk   Mike YAWN/HP6650/21
Commercial Systems Division          Voice         (408) 447-4367
19447 Pruneridge Ave M/S 44UP        Fax           (408) 447-0312
Cupertino, CA  95014
-----------------------------------------------------------------