I was recently discussing how to get more frequent migration for some datasets and heard the answer is to run another HSM task. Alternatively, consider writing a job that issues the migration command for those special datasets before the normal migration time. That gets them earlier in the queue. If there is a way for normal migration to ocur on the hour for everything and a way to get some datasets migrated every 15 minutes, I would be interested in hearing about it.
Maybe that is part of your more than an hour problem. Or are you really migrating datasets for an entire hour and falling behind. Like the 25 hour daily job. On Fri, 3 Aug 2007 14:57:41 -0700, Gary Jacek <[EMAIL PROTECTED]> wrote: >Hello list > >We used to write our IMS SLDS logs, DB2 and MQ Series archive logs directly to tape. > >In order to get better tape utilization, we have converted these logs to disk datasets, which are subsequently migrated to ML2(tape) by HSM. > >Somewhat infrequently, we have found that HSM is so busy with other work that the ML2 migration of our logs takes longer than an hour. This triggers some automated alerting, so that we can look into the problem. > >Is there any way to tell HSM that HMIG commands for specific dataset patterns (eg. IMSVS.SLDSS.*) should be handled as soon as possible, rather than just placing them in a FIFO queue of work to be done? > > > >Gary Jacek >TSDOSS - TELUS >250-413-8217 > >---------------------------------------------------------------------- >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 ---------------------------------------------------------------------- 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
