PSM should expire eligible datasets, regardless of volume residency levels.
Have a look at the bottom few paragraphs here, specifically: "Pass 1 of automatic primary space management <https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.arcf000/pass1a.htm?view=kc#pass1a> (non-data-movement function in primary space management) and extent reduction are performed for all volumes in storage groups defined with AM=Y and AM=I (SG1, SG2, and SG3). Pass 2 of automatic primary space management <https://www.ibm.com/support/knowledgecenter/SSLTBW_2.2.0/com.ibm.zos.v2r2.arcf000/pass2a.htm?view=kc#pass2a> (migration) is performed only for those volumes that are above the low threshold after pass 1 and extent reduction have completed." https://www.ibm.com/support/knowledgecenter/en/SSLTBW_2.2.0/com.ibm.zos.v2r2.arcf000/stgbmgd.htm Have a look at the HSM log messages being produced for the datasets which you expect to be expired. They should indicate why they are not being expired. On 5 March 2018 at 18:26, Mike Schwab <[email protected]> wrote: > Set one volume to Quiesce,New and migrate the volume. Whatever is > left try to manually migrate and note error. Return to spare if you > don't need the space, or Enable to return to active use. Proceed with > next volume. Or just reduce high threshold so it will process all > volumes, return after cleanup. > > On Mon, Mar 5, 2018 at 10:37 AM, willie bunter > <[email protected]> wrote: > > I verified the MC and DSORGs. No problem found. No patches either > which would impede the PSM. I remember reading or being told that once the > SM conditions had been met, HSM stops looking at the volume(s). > > > > From: Graham Harris <[email protected]> > > To: [email protected] > > Sent: Friday, March 2, 2018 6:05 PM > > Subject: Re: SMS/HSM QUESTION > > > > Primary space management should normally process all volumes in a storage > > group. And PSM should normally look to reduce utilisation of a volume > down > > to the low threshold (caveat - various PATCHes can alter DFHSM standard > > behaviour). > > Have you checked the messages for space management actions for these > > datasets? > > It could be that they need to be backed-up before being expired, and > > auto-backup may not be running against that SG (as an example of a > > condition that could potentially give rise to what you are seeing). > > Or another possibility is that they cant be backed up, because, for > > example, they may have a null DSORG. If they cant be backed-up, and the > > management class says they must be backed up, then DFHSM will not expire > > them until they are backed up. > > > > The above may not precisely match what you are experiencing, but it may > > perhaps point you in a better direction. > > > > On 1 March 2018 at 16:18, Willie Bunter < > > [email protected]> wrote: > > > >> Thanks for the info., however it doesn't answer my question as to which > >> threshold I should modify. > >> > >> ---------------------------------------------------------------------- > >> For IBM-MAIN subscribe / signoff / archive access instructions, > >> send email to [email protected] with the message: INFO IBM-MAIN > >> > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to [email protected] with the message: INFO IBM-MAIN > > > > > > > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, > > send email to [email protected] with the message: INFO IBM-MAIN > > > > -- > Mike A Schwab, Springfield IL USA > Where do Forest Rangers go to get away from it all? > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
