HP3000-L Archives

February 1996, Week 1

HP3000-L@RAVEN.UTC.EDU

Options: Use Monospaced Font
Show Text Part by Default
Show All Mail Headers

Message: [<< First] [< Prev] [Next >] [Last >>]
Topic: [<< First] [< Prev] [Next >] [Last >>]
Author: [<< First] [< Prev] [Next >] [Last >>]

Print Reply
Subject:
From:
Goetz Neumann <[log in to unmask]>
Reply To:
Goetz Neumann <[log in to unmask]>
Date:
Mon, 5 Feb 1996 11:17:36 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (30 lines)
Michael P. Smith wrote:
>
> I am trying to come up with a way to selectively disable MPE/iX commands from
> within programs.  The method must work on 3rd party products as well as in
house
> utilities (which may or may not have source code).  The only concession is
that
> the method only has to work for NM programs (although I might have to do it
for
> CM programs later).
>
> As far as I can tell, there are 3 ways of doing this, and they are (in order
of
> completeness):
 
$PLUG ALERT
I am unhappy to correct you, but there is a 4th way:
 
Get yourself Security Monitor/iX, B3175A. (available as of MPE/iX 5.0).
It has among nice others the feature to disable command access,
whether programmatic or general execution, configurable by command.
 
I do not know the prices in the U.S., but according to the ones here
in Germany it should be a 4-digit$ value (for unlimited # users).
 
 
Hope this helps,
 
Goetz 'who reinvented the wheel himself often enough :-)'.

ATOM RSS1 RSS2