Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP Path: utzoo!mnetor!seismo!gatech!bloom-beacon!mit-eddie!ll-xn!ames!ptsfa!ihnp4!inuxc!iuvax!pur-ee!uiucdcs!uxc.cso.uiuc.edu!uiucuxe!heisterb From: heisterb@uiucuxe.cso.uiuc.edu Newsgroups: comp.os.vms Subject: Re: Captive VMS command procedure wante Message-ID: <62500002@uiucuxe> Date: Sun, 5-Jul-87 14:53:00 EDT Article-I.D.: uiucuxe.62500002 Posted: Sun Jul 5 14:53:00 1987 Date-Received: Tue, 7-Jul-87 06:50:50 EDT References: <1682@uwmacc.UUCP> Lines: 15 Nf-ID: #R:uwmacc.UUCP:1682:uiucuxe:62500002:000:534 Nf-From: uiucuxe.cso.uiuc.edu!heisterb Jul 5 13:53:00 1987 [ 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