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 [email protected] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
