I guess that is why I cannot use my logic with DFHSM. To me if the parm is set to NOAUTOMIGRATION, then it should not do it until I change it.
I get so confused sometimes with SMS. ;-D Lizette > > Thanks Brian, I missed the Automigrate=I in Lizette's original post. > Lizette, Here's the quote from the manual: > > I specifies that data sets are eligible for primary space > management and specifies that DFSMShsm is to perform automatic > interval migration independent of the DFSMShsm Setsys > Intervalmigration option. I also causes DFSMShsm to perform the > same functions as if Y had been specified. Interval migration is > performed on only those volumes whose occupancy is at or above > their high threshold. The most frequent DFSMShsm can do interval > migration is hourly. If you select I with a low threshold value > of 0, DFSMShsm migrates all the eligible data sets in the > selected storage group. I is most useful for storage groups used > with tape mount management. > > Brian's right, you want Automigrate=Y > > > Interval migration depends on the value specified AUTO MIGRATE Value for the > storage group. > > If AUTOMIGRATE=I then interval migration will run even if SETSYS > NOINTERVALMIGRATION and INTERVALMIGRATIONTASKS(0) is in place. > > If you want/need these parameters to be used then you need to use > AUTOMIGRATE=Y. > > Brian > > On Sat, Apr 18, 2009 at 10:00 PM, Lizette Koehler > <stars...@mindspring.com>wrote: > > > Dave, > > I am going to open an issue with HSM. They do not have anything specific > > to > > intervalmigration since 1997. But they may have something else that > > affects > > it under a different name. > > > > I will let you know what happens. > > > > Lizette > > > > > > > > > > We are also at 1.9 and Nointervalmigration means no intervalmigration > > here. Our > > > maintenance is most likely not on a par with yours. I'd have to ask. > > > Like you we have multiple Lpars and share SMS and HSM control datasets. > > > > > > > > > z/os 1.9 at rsu 0901 and z/os v1.9 at rsu 0808. We share everything! > > > > > > These versions all use the same SCDS/ACDS files and > > BCDS/MCDS/OCDS/Journal > > > files > > > > > > Lizette > > > > > > > > > > > Lizzette, > > > > > > > > I would take this up with IBM. If Q Setsys shows Nointervalmigration > > > > but Q Autoprogress (or HSM Joblog) shows Interval Migration then > > > something is > > > > wrong. > > > > What software level are you running? > > > > > > > > Dave O'Brien > > > > NIH Contractor > > > > ________________________________________ > > > > > > > > I had 3 storage groups that had INTERVALMIGRATION indicated. However, > > in > > > > the DFHSM parms I have NOINTERVALMIGRATION specified. And yet, I had > > IM > > > > running like it was indicated on these 3 storage groups. > > > > > > > > I thought only if I had INTERVALMIGRATION turned on in the ARCCMDxx > > member > > > > would it run. That if a Q SETSYS showed NOINTERVALMIGRATION then even > > if > > > it > > > > was specified, it would not commence. > > > > > > > > I did not issue any F DFHSM, commands to turn on INTERVALMIGRATION. So > > I > > > do > > > > not think it should have been running to start with. > > > > > > > > > > > > What am I missing here? > > > ---------------------------------------------------------------------- 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
