RE: Securing JobQs

[Evan Harris <spanner@xxxxxxxxxx>]

I've been mulling this one over for a while, it seems this is one of those
evergreens that love to haunt shops.

I kinda had a think about your problem and possible solutions and then it
occurred to me that the answer I had nearly always come up with was twofold:

1. Remove any access to the work with job options for users that must not
be allowed to change their jobs. i.e. Menu security, no command line,
dspsbmjob instead of wrksbmjob etc etc.

2. Trust and monitor those users that have the privilege but have been
asked not to exercise it. Revoke this ability if necessary due to abuse.
Theres nothing like a few days without WRKSBMJOB or WRKJOB to convince a
programmer that doing the right thing may be far easier than going without
the tools that help him/her do their job.

hth

Cheers
Evan Harris
+---
| 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
+---