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:
Richard Gambrell <[log in to unmask]>
Reply To:
Richard Gambrell <[log in to unmask]>
Date:
Sat, 13 Jan 1996 17:11:50 CST
Content-Type:
text/plain
Parts/Attachments:
text/plain (34 lines)
>
> At 12:29 PM 1/9/96 -0800, [log in to unmask] wrote:
> >What I want is the ability to have different jobs
> >from the same user submitted to different queues.
>
> Mohan:
>
> Gavin completely beat me to the punch on this, I was getting ready to say
> almost exactly the same thing.  This and all his other comments are right on
> target.
>
> 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=...  This
> would be consistent with the way security is done now on files, devices,
> classes, etc.  (didn't you guys learn from the :ASSOCIATE command what a bad
> idea it is to have security config files like ASOCDATA.PUB.SYS and
> table-building programs like ASOCTBL.PUB.SYS just laying around loose where
> they can be misplaced/forgotten/trashed? :> )
>
 
I agree!
Let me add my $.002 worth to this. I agree, security is necessary and the
ACD method is the right one. Users/Jobs needs access to multiple queues, but
this access must be limited by some type of security arrangement.
 
I would prefer if the ACD refered to the full jobname,user.account of the Job
card, with wildcard support.
 
--
-- - - - Speaking for myself and not necessarily anybody else - - - - - -
Richard Gambrell        | Internet: [log in to unmask]
Mgr. Tech. Services     | POT:      504-483-7454     FAX: 504-482-1561
Xavier University of LA | Smail:    7325 Palmetto, New Orleans, LA 70125

ATOM RSS1 RSS2