Would lowering the high threshold to as low as possible (for example 20) solve the problem. The objective is to keep the volumes as free as possible because mostly GDG (output) dsns reside on the volumes and never used as input.
________________________________ From: "Staller, Allan" <[email protected]> To: [email protected] Sent: Monday, June 10, 2013 9:47:04 AM Subject: Re: DFHSM QUESTION : Allocation/migration Threshold: High . . 95 (1-99) Low . . 80 (0-99) It is my understanding that if the volume does not exceed the high threshold, migration will not begin on that volume. Once migration begins, It will continue until the low threshold is reached (normally, oldest datasets migrated first). A specific dataset may or may not migrate as specified in the SMS MGMTCLAS, dfHSM exits, and a few miscellaneous additional rules (e.g. APF authorized DS, DSORG=PSU,...). HTH, <snip> I am referring to primary space management. When I say " dsns are not being migrated often enough' I meant to say that the dsns in the storage group are not ALL being migrated when SP is run. To fix the problem I migrate the volume - HSEND MIGRATE VOLUME(RPM105 MIGRATE(0)) - and lots of space is now available. Is the cause related to the thresholds settings? What could I do instead of having to migrate the volume? Should I lower the Allocation/Migration Threshold from 85 to 40? :>: I have a problem with primary ML0 SMS managed pool which for some reason :>: the dsns are not being migrated often enough. The setup is as follows : :>: Allocation/migration Threshold : High 85 (1-100) Low . . :>: 1 (0-99) :>: Alloc/Migr Threshold Track-Managed: High 85 (1-100) Low . . :>: 1 (0-99) :>: Guaranteed Backup Frequency . . . . . . NOLIMIT (1 to 9999 or :>: NOLIMIT) :>: BreakPointValue . . . . . . . . . . . . (0-65520 or :>: blank) :>: :>: If I lower the Allocation/migration Threshold High to 55 would that do :>: the trick when Space management runs? </snip> ---------------------------------------------------------------------- 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
