Miklos, Do you really want to be without a HSM Backup for these datasets?
You could either add a HBACKDS 'dataset' WAIT before the HMIG in Mark's suggestion or assign a Management class of Primary days = 0 and ML1 days = 0. HSM will migrate directly to ML2 after the Incremental is taken. Not immediately but at the next Interval or Primary Space Mgmt. window. Dave O'Brien NIH Contractor ________________________________________ From: IBM Mainframe Discussion List [ibm-m...@bama.ua.edu] On Behalf Of Mark Jacobs [mark.jac...@custserv.com] Sent: Wednesday, May 20, 2009 8:05 AM To: IBM-MAIN@bama.ua.edu Subject: Re: Migrate at close Miklos Szigetvari wrote: > Hi > > In some cases , it would be nice to migrate a dataset to ML2, as > soon as it has been writen and closed. > Can I achive this ? How about adding a step to the end of the job to issue the HMIG commands? //HMIG EXEC PGM=IKJEFT01 //SYSTSPRT DD SYSOUT=* //SYSTSIN DD * HMIG 'DATASET' ML2 /* -- Mark Jacobs Time Customer Service Tampa, FL ---- In theory there is no difference between theory and practice. In practice there is. - Yogi Berra ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu 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 lists...@bama.ua.edu with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
