Interesting approach - If the poster is actually trying to get an application PIT (point in time) backup of his application using HSM, the only way I could get that to work here would be to flashcopy the whole thing to new names & then run HSM backups against those new names. Then it would no longer matter that HSM single-threads everything and it would also take the entire backup process outside the critical path.
Now I've only been watching this thread with 1 eye, So if I missed something already posted, I apologize. ddk ////////////////////////////////////// Glenn I think he wants to run wide on the migrates. So if he submits 10 migrates, he wants them to run concurrently. But the OP states it only mounts one tape and then all 10 requests are serialized to the one tape. And if I understand his requirement - he is using HSM as an application backup process in-case of issues during the batch run. So like doing an Imagecopy before batch job runs, then restoring from the imagecopy after batch if there is an issue, is what I think he is trying to do. I would probably suggest increasing the number of BACKUP versions of the file since HSM does quite well at doing a backup when the data changes. What I do not know is the environment. How many tape drives does he have in his shop. How many can he allocate to DFSMShsm migration. What his overall need is for this type of process. Just my thoughts Lizette ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
