On 07/06/06, Perryman, Brian <[EMAIL PROTECTED]> wrote:
Some people in our apps support department create test files under their own
TSO userid HLQ, which get SMS-placed onto the 'user' storage pool, but then
later they manually rename these files to have a production dataset prefix, I
have no idea why - so they can test some production jobs, perhaps. Anyway,
these production HLQs would normally go in their own catalog and SMS storage
pool but, because the files were renamed, they're staying in the original
catalog and storage pool.
It's playing havoc with my storage policies and DR planning.
Any ideas if there's a quick and easy way (preferably something in RACF?) I can
stop them doing this?
Remove their ability to create, rename, copy or alter anything with a
production HLQ. They are applications support - they should have no
access to production datasets other than (perhaps) to read them. If
they want to put data into production, it gets copied in via a batch
job which runs under and audited and controlled batch userid.
Your data is important - no-one should have the right to fiddle about with it.
--
Steve
Despair - It's always darkest just before it goes pitch black...
----------------------------------------------------------------------
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
