Add a step to each migration to compress the appropriate target datasets. That way the "user" will never need to compress.
HTH, <snip>> >Hi, > >We using RACF on a z/os 1.10. > >I trying to find a way to permit a user to run a compress job on a data > >sets while is access on the data set is READ. > >any idea on how can I limit the user to a READ access and still able them > to > >compress the data sets when needed? > > > >note - I don't want them to run the job using a powrful user using the > USER > >statement . > > > Would PDSE avoid the problem? Does Endevor suffer the stale handle > problem? Is PDSE ever a solution? > > -- gil > the migration will be much more complicate . </snip> ---------------------------------------------------------------------- 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
