RE: Securing JobQs

["Kahn, David [JNJFR]" <DKahn1@xxxxxxxxxxxxx>]

I've only just re-subscribed to midrange-l so I haven't seen the entire
thread, but it seems a possible solution would be to add a validity checker
to the CHGJOB command. You could allow most of the parameters through but
spit out the ones that are open to abuse such as JOBQ, JOBPTY and RUNPTY,
except for the profiles that perform these functions legitimately.

Adding a validity checker to an IBM command is not trivial but can certainly
be done. A drawback is that you would also have to re-visit it after every
OS upgrade in case new parameters have been added.

There's at least one home page on the web that has an example of this.
Unfortunately I don't have a record of the URL and I can't search for it at
the moment as I don't currently have web access at work. I think I found it
originally by surfing on from Pete Hall's pages.

Dave Kahn

-----Message d'origine-----
De: Buck Calabro [mailto:mcalabro@commsoft.net]
Date: 06 July 1999 14:29
À: 'MIDRANGE-L@midrange.com'
Objet: RE: Securing JobQs


This solution may not work for every shop.  If you revoke authority to
CHGJOB, your users won't be able to run CL programs with the following
commands:CHGJOB SWS(xxxxxxxx); CHGJOB OUTQ(xxxxxxxxxx).  Legacy code strikes
again!

Buck Calabro

+---
| This is the Midrange System Mailing List!
| To submit a new message, send your mail to MIDRANGE-L@midrange.com.
| To subscribe to this list send email to MIDRANGE-L-SUB@midrange.com.
| To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com.
| Questions should be directed to the list owner/operator: david@midrange.com
+---