HP3000-L Archives

February 1999, Week 3

HP3000-L@RAVEN.UTC.EDU
Options: Use Monospaced Font
Show Text Part by Default
Condense Mail Headers

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

Print Reply
Mime-Version:
1.0
Sender:
HP-3000 Systems Discussion <[log in to unmask]>
Date:
Mon, 15 Feb 1999 14:42:24 -0800
Reply-To:
Jeff Vance <[log in to unmask]>
Subject:
Re: Spoolfile access
From:
Jeff Vance <[log in to unmask]>
In-Reply-To:
GREG CHAPLIN <[log in to unmask]> "Spoolfile access" (Feb 15, 4:27pm)
Content-Type:
text/plain; charset=us-ascii
Comments:
To: GREG CHAPLIN <[log in to unmask]>
Parts/Attachments:
text/plain (22 lines) 
On Feb 15,  4:27pm, GREG CHAPLIN wrote:
...
> The question is: Is there any way to allow users to see any spoolfile for the
> logon account, with no (or minimal) change to the way jobs log on?

You may be able to alter the spoolfiles and add an ACD that
grants read access to @.account.  See the ALTSEC command for
details.  BTW, this would need to be done after the spoolfile
was created.  The HPSPOOLID CI variable contains the spoolfile
ID of the $STDLIST spoolfile for the current job.  The job
could do:
   altsec !hpspoolid.out.hpspool;repacd=(r:@.!hpaccount;w,l,s,x:$owner)

Then the users shouldbe able to read the spoolfile.  I have not
tried this.

regards,
Jeff Vance, CSY


--

ATOM RSS1 RSS2