Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ihnp4!inuxc!iuvax!pur-ee!uiucdcs!uxc.cso.uiuc.edu!uicsrd!kai
From: kai@uicsrd.UUCP
Newsgroups: comp.os.vms
Subject: Re: Captive VMS command procedure wante
Message-ID: <6300001@uicsrd>
Date: Mon, 6-Jul-87 21:15:00 EDT
Article-I.D.: uicsrd.6300001
Posted: Mon Jul  6 21:15:00 1987
Date-Received: Sat, 11-Jul-87 10:46:44 EDT
References: <1682@uwmacc.UUCP>
Lines: 18
Nf-ID: #R:uwmacc.UUCP:1682:uicsrd:6300001:000:668
Nf-From: uicsrd.CSRD.UIUC.EDU!kai    Jul  6 20:15:00 1987


/* Written  1:53 pm  Jul  5, 1987 by heisterb@uiucuxe.cso.uiuc.edu in uicsrd:comp.os.vms */

[ love to eat them mousies, mousies what I love to eat... ]

Depending on how restricted an access you want to give the captive users
you could generate a new command table by removing the "forbidden"
commands from dcltables.exe.  Of course you need to prohibit access to
the original dcltables... (I know a funny story about that!).

Otherwise, just have the captive account command procedure read
command lines, check that the command is "ok" and then execute it.

Does that sound workable for you?

heisterb@uiucuxe.cso.uiuc.edu

/* End of text from uicsrd:comp.os.vms */