Have IT management "risk accept" they way you need. Then tell the auditors that. Auditors do not have any authority beyond what management gives them. This assumes management has tener cojones. On Jun 4, 2013 5:49 PM, "gsg" <[email protected]> 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
