Edward Jaffe wrote:
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.
SMS attributes like STORCLAS and MGMTCLAS are not changed by a simple
rename. You need to specify new values for them on the IDCAMS ALTER at
the same time you change the name. I'm skeptical about the catalog not
changing. A "legitimate" rename operation should establish the new
catalog entry as required by the alias associated with the new
high-level qualifier(s).
You don't need o be skeptical. You can check it, and be sure about it. <g>
I'm not sure what "should happen", however regular ALTER NEWNAME
*without* CAT() parameter gives different results for SMS-managed and
non-SMS-managed datasets.
Regarding SMS classes: they *can* be changed by simple rename. See
ACSENVIR RENAME.
Regards
--
Radoslaw Skorupka
Lodz, Poland
----------------------------------------------------------------------
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
