That's my experience also. I started migrating DB2 tables in development environments back in 1997 and never had a problem, except dumbass operators that kept assigning all the tape drives to production LPARS. Even then only the thread requesting the migrated dataset was impacted. The rest of DB2 ran fine.
________________________________ From: Cathy Taddei <cathy.tad...@yahoo.com> To: IBM-MAIN@listserv.ua.edu Sent: Tue, June 19, 2012 6:03:01 PM Subject: Re: [IBM-MAIN] Migrate DB2 datasets? Just the thread accessing the migrated tablespace waits. There is a zparm specifying how long the thread will wait for HSM recall before abending. Cathy Taddei Sent from my iPhone On Jun 19, 2012, at 10:38 AM, "O'Brien, David W. (NIH/CIT) [C]" <obrie...@mail.nih.gov> wrote: I noticed that some of my DB2 databases have not been accessed since the turn of the century. These are SMS managed and have a Management class which calls for migration to Level 1 after 365 days of non-use. After another year of non-use they are eligible for ML2. Naturally the Storage Group has auto migrate set to No. Hence my question(s) - If a DB2 table space is migrated, does the entire DB2 environment wait for the recall or just the DB2 user/process which invoked the recall? Does anyone else out there migrate DB2 data? Thank You, Dave O'Brien NIH Contractor ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
