I have not gone through this process. However a few thoughts. 1) I would make sure that you do not need the HSM backups for SEC/HIPPA, or other long term retention requirements. 2) If I were to do this, I would build a REXX/CLIST that would list all datasets under a specific HLQ and RENAME all the online files, then it would do the HRECALL, RENAME, HMIG process for those things in ML1/ML2 3) Verify if you have any tape datasets that need to be copied to the new names. Some users will put data on Tape under their HLQ. You will need to look at a utility like CA TAPECOPY or some other process that will keep the current information of the tape and not reset the EXPIRE or other details. 4) Check your management classes. Make sure the RENAMES still have the same timeframe of expiration/retention. The Last Reference Date will probably change when you do the RECALL process. 5) Before I would start, I would definitely do a dump of all files being renamed prior to starting. That way if there is an issue, you can recover the original file.
Depending on your time frame for the conversion, you may or may not have sufficient time to protect everything. You also need to consider how long each HLQ will take for conversion, 1 hour - 2hours- ?? Get a best guess. Sometimes if there is a recall it make take a while depending on when it was migrated/last used on dasd. You also need to consider the type of files, all PS, mix of VSAM,PS, PDSE? Different techniques are needed to rename them. Lizette -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of Michael Bieganski Sent: Sunday, April 21, 2013 11:52 AM To: [email protected] Subject: Rename of hsm migrated files due to userid change Hi...in the coming months, our company plans to completely change the format of our mainframe userids. For example, current mainframe userid a#xyz123 will change to mainframe userid e123456. We have literally tens of thousands of mainframe userids and tens of thousands of hsm migrated datasets that belong to userids under the old format. I envision this would entail hrecalling the old-format-userid datasets, renaming each of them to the new appropriate userid-hlq, and I imagine even deleting all the hsm backups of the old-format-userid datasets at some point (or let the 'retain days' take its course) It seems like quite a daunting manual, labor intensive process......has anyone out there any experience with mass change of mainframe userids and having to account for all their datasets vis-a-vis HSM? Any experiences regarding how to streamline this would be appreciated. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
