Hi folks
 
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?
 
Cheers
 
Brian
 
-
This e-mail message is for the sole use of the intended recipient(s)and may 
contain confidential and privileged information of Transaction NetworkServices. 
 
Any unauthorized review, use, disclosure or distribution isprohibited.  If you 
are not the intended recipient, please contact thesender by reply e-mail and 
destroy all copies of the original message.

----------------------------------------------------------------------
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

Reply via email to