If the database is accessed via the web / z/OS Unix, the date accessed filed is NOT updated. We don't migrate for this reason. We had DB2 storage groups fill up, having problems, no one would authorize more space, so I manually migrated datasets not accessed in 1 year. The users then had to get the dabases recalled before their applications would work.
The issueing TSO id would only be tied up if you issued a migrate with the wait option, default is nowait and you get control back immediately. On Tue, Jun 19, 2012 at 12:38 PM, O'Brien, David W. (NIH/CIT) [C] <[email protected]> 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 -- Mike A Schwab, Springfield IL USA Where do Forest Rangers go to get away from it all? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
