Subject: | |
From: | |
Reply To: | Stigers, Greg [And] |
Date: | Mon, 9 Oct 2000 11:16:56 -0400 |
Content-Type: | text/plain |
Parts/Attachments: |
|
|
X-no-Archive:yes
Won't ASSOCIATE, and the ASOCTBL to make this permanent (see help
associate), allow the system manager or operator to grant permission to a
user name to manage a spooled device? And won't that include StartSpool? Or
is my memory throwing parity errors again?
Of course, you might want to consider limiting who is associated, and who
can sign on as that user. Or, give said Super User enough rope to hang
themselves, earning the ire of all other users who depend on said spooled
device(s).
Greg Stigers
http://www.cgiusa.com
-----Original Message-----
From: Chana, Harpreet TCS1C [mailto:[log in to unmask]]
Sent: Monday, October 09, 2000 3:37 AM
To: [log in to unmask]
Subject: use of allow command
Hi all,
My Some Super Users they need the facility of StartSpool Command.
and the command is
allow user.account;command1; command2............command nnn
will it be permanent or for the time being.
I wish to allow them permanent.
I have to put this command in their startup login ID's ??
Regards
Harpreet
|
|
|