HP3000-L Archives

January 1996, Week 2

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:
Reply To:
Date:
Tue, 9 Jan 1996 15:43:06 -0800
Content-Type:
text/plain
Parts/Attachments:
text/plain (20 lines)
Jon said:
> One refinement I would suggest is that security *should* be there, but it
> should be done with ACD's, e.g. :ALTSEC MYJOBQ,STREAMQ;NEWACD=...
 
Yes, I was going to suggest that if they do want to do security, that the
ACD mechanism (as Jon suggests) is exactly the mechanism to do this.  They
could either create a new class of thing called a 'job queue' that you
could add ACDs to, or it might be worth doing something simple like:
 
In order for QUEUE security to be in effect, you have to create an MPE GROUP
named QUEUE.SYS.  When a QUEUE name is referenced in :STREAM, it would only
be valid if there exists a file queuename.QUEUE.SYS, which is writeable by
the user doing the :STREAM (or should it be by the job being streamed. It's
not obvious which it should be, either from their way of doing it or mine).
You simply put ACDs on the dummy files in the QUEUE.SYS group to control
who has access to which QUEUEs.  Obviously this is a bit of a kludge, but
it sure would be easier to implement if cost is a sinificant issue.
 
G.

ATOM RSS1 RSS2