On Jun 7, 2006, at 6:38 AM, Perryman, Brian wrote:
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,
A long time ago (10+ years) we tried to get IBM (via GUIDE req) to
redrive the ACS routines when a rename occurred. It was rejected,
IIRC not even a comment was given.
We (IIRC) sent it back and asked for a reason. I think IBM never did
respond . I think after all is said and done IBM won't budge on this
and I sort of see their point (to a point). IBM just didn't want to
write an application that would do it . I think IBM's hidden message
was it was up to the installation to fire off a dfdss job once a day
to mov e stuff back to the "proper" pool.
ED
----------------------------------------------------------------------
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
