HP3000-L Archives

February 1999, Week 3

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:
GREG CHAPLIN <[log in to unmask]>
Reply To:
GREG CHAPLIN <[log in to unmask]>
Date:
Tue, 16 Feb 1999 17:35:46 +1000
Content-Type:
text/plain
Parts/Attachments:
text/plain (35 lines)
I asked:
> ...
> > 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?
>
Then Jeff Vance replied (thanks, Jeff):
> 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.

Yep, that did the trick (except that the access mode "s" should be "a"). Next
problem is that LISTSPF does not show the spoolfiles for other users in the
account, even though I have altered the ACDs for them (I can read the
spoolfiles, but I can't see them in LISTSPF). I've tried looking in the manuals &
online doco, but haven't found anything. Any ideas?

Thanks again.

----------------------------------------------------------
Greg Chaplin
UniSuper
Level 28, 367 Collins St,
Melbourne  VIC  3000,
Australia.
Email: [log in to unmask]
Phone: +61 3 9648 4145
Fax:   +61 3 9648 4141

ATOM RSS1 RSS2