Hi, We are looking at tightening control over MVS command authorization. We are a JES3 shop running Flasher, Omegamon, Solve etc. with ACF2. Of course we have batch production jobs streams, operators, MVS sysprogs all issuing MVS commands at different times and in different situations.
Our management would like two keys areas addressed, firstly how to best control who can issue commands MVS commands and secondly once the command is issued how to best track and note that the command has been issued. I assume control of MVS command issuing is a fairly common requirement so I was hoping people could pass on the benefit their wisdom and knowledge and how they have seen this done. Thanks for your help. Regards Peter Phillips ANZ Melbourne Australia "This e-mail and any attachments to it (the "Communication") is, unless otherwise stated, confidential, may contain copyright material and is for the use only of the intended recipient. If you receive the Communication in error, please notify the sender immediately by return e-mail, delete the Communication and the return e-mail, and do not read, copy, retransmit or otherwise deal with it. Any views expressed in the Communication are those of the individual sender only, unless expressly stated to be those of Australia and New Zealand Banking Group Limited ABN 11 005 357 522, or any of its related entities including ANZ National Bank Limited (together "ANZ"). ANZ does not accept liability in connection with the integrity of or errors in the Communication, computer virus, data corruption, interference or delay arising from or in respect of the Communication." ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
