Re: Moving HSM Migrated Data Sets to New System
I was reminded of an additional consideration when using ABARS to process MLx data. Make sure that you have audited the MCDS first, as any errors on the selected migrated entries will cause the ABACKUP to fail. A product such as Tivoli Advanced Audit for DFSMShsm makes this task much easier. -- 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
Moving HSM Migrated Data Sets to New System
I'm in the process of moving a z/OS 1.6 environment to a z/OS 1.8 enviornment. Due to configuration issues (long story, but ie, I don't have tape drives on the source system) I cannot simply dump volumes to tape and move them. In the end, not really a problem- I'm moving datasets by dumping them with DFDSS to a data set, FTPing the data set to the new system, and restoring. Not the fasted way to go, but it's working. But now, my major concern is moving all our HSM migrated data sets- both those on ML1 DASD, and those on ML2 tape. Now the ML2 tapes are going to be physical sent where the new enviornment is so data can be recalled off of them. The issue/question I have is: how can I move the catalog entries for all the migrated data sets? The entries will be scatttered across several user catalogs, which won't actually be moved. (Although I guess I could move/copy them if needed.) Now I did notice in some previous posts (although a few years old) that ABARS could possibly do this for me. The post mentioned that it would backup/restore migrated data sets without actually recalling/remigrating them. Is that true? If so, that would work for me. Thanks in advance for any responses. And if someone has an idea to talk with me about please feel free to call me- number is below. Doug Evans IT Manager Integral Systems, Inc. Phone: 616-895-2748 / 925-418-5663 Pager: 925-677-7650 / Fax: 925-522-8039 mailto:[EMAIL PROTECTED] / [EMAIL PROTECTED] -- 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
Re: Moving HSM Migrated Data Sets to New System
Doug, ABARS can help you in this case. You would run the ABACKUP command using the PROCESSONLY(MIGRATIONLEVEL2). You could also process ML1 as well; there is a separate PROCESSONLY(MIGRATIONLEVEL1). If you were to specify the MOVE parm , it would also delete the migrated entries from the source system (use with caution) On the receiving system, run the ARECOVER with the MIGRATEDDATA option. ML1 means recover all migrated data to ML1; the manual says this is the default. Specifying ML2 will recover to ML2 and MIGRATEDDATA (SOURCELEVEL) means to recover back to the original migration level. Your selection dataset would need to look something like INCLUDE(**) and then exclude any datasets if needed. All datasets (sms and non-sms) must be cataloged in order for ABARS to process them, but since these are migrated datasets this is not an issue. Chapter 3.3 of the DFSMShsm Storage Administration Guide discusses ABARS in detail. I do not think there is a compatibilty problem regarding the different z/OS DFSMS levels that you are running, but it might be worth checking into that. Hope this helps. -- 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
