Date sent:              Tue, 16 Feb 1999 12:12:00 -0800
Send reply to:          Jeff Vance <[log in to unmask]>
From:                   Jeff Vance <[log in to unmask]>
Subject:                Re: Spoolfile access
To:                     [log in to unmask]

> On Feb 16,  5:35pm, GREG CHAPLIN wrote:
> ...
> > Then Jeff Vance replied:
> > > 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)
> >
> > 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?
>
> I hate to say this but you may want to use the old SHOWOUT command.
> Security is lower for this command for compatibility reasons.  LISTSPF
> requires you to be: a) on the console, b) have SM or OP, c) have AM and
> the creator of the spoolfile is in your account, d) be the creator of the
> spoolfile.  In your situation none of these conditions apply.
>
> Jeff Vance, CSY
>
> --

Jeff-

It sure would be handy to be able to ALLOW on LISTSPF,
PRINTSPF, etc.

Gary

Gary Jackson
Nevada County Supt. of Schools
(530) 478-6400 x 215