We never allowed *ANY* commands to come through a reader (of any type).
The programmers had a field day with this until I put the rules in
place.
Got a few gripes from programmers but nothing to management.
My management (and the auditors) were strictly against commands from
readers. There were just too many issues.
Ed
On Jun 4, 2013, at 5:49 PM, gsg wrote:
We have been told by auditors that all of our JES2 JOBCLASSes
should have COMMAND=VERIFY. This would protect from someone coding
an unauthorized command in a JCL that could go undetected. Has
anyone else ran into this type of problem and if so, how did you
protect against it vs. coding COMMAND=VERIFY. Coding
COMMAND=VERIFY could potentially elongate our batch window and
overwhelm our operators with replies. Anyone got a solution?
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
