Hi Kenneth Falling behind on HSM migration for these datasets is infrequent. So this is not the 25 hour day problem.
Unfortunately, the datasets to be migrated are created just a few seconds before the HMIG command is issued to migrate them. The dataset names have an embedded timestamp that represents the start or end of the log range. So there is no way to predict the datasetname and issue the HMIG command in advance. Even if we can predict the datasetname, I'm not sure HSM will let you queue the command if the dataset has not been catalogued yet. I was hoping there was an exit in HSM where one could code dataset patterns like IMSVS.SLDSS.*. Each time HSM goes looking for work in its input queue, the exit would be invoked to scan for a pattern match and select our IMSVS.SLDSS.* dataset activity for processing, in preference to other commands that arrived earlier, affecting other non-critical dataset movements. Gary Gary Jacek TSDOSS - TELUS 250-413-8217 -----Original Message----- From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf Of Kenneth E Tomiak Sent: Saturday, August 04, 2007 7:34 AM To: IBM-MAIN@BAMA.UA.EDU Subject: Re: HSM and offsite logging -- An HSM question 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. ---------------------------------------------------------------------- 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
