Jorge Garcia wrote: >The job that define and delete the dataset, is submited by control-m. The control-m user is operations and we have create a surrogat entries called T99MIHP.SUBMIT.
You will need to place NONE or READ for BOTH ids (T99MIHP and T99CTM) in the access list of that dataset. Or clear out all accesses, place the dataset in WARNING and test again. I would REALLY advise you to REMOVE Operations from Control-M to avoid just this type of unrealistic high accesses. >T99CTM group and T99MIHP group are differents Did you just said ids earlier? >Could be the problem the T99CTM operations attribute?. We couldn't remove it (it's not recommendable). Hmmm, what is the Started Task OWNER name of the Control-M? The same as T99CTM? What is the eventual group access of Control-M? Does T99CTM belongs to more than ONE group(s)? Also, what is the TRUSTED and PRIVILEGED status of the STC's segment in RACF? Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- 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
