Allan, Thanks for spotting my error. I posted the wrong threshold stats of the storage group. Here is the correct (I promise) High Allocation/Migration Threshold: To ALTER Storage Group, Specify: Allocation/migration Threshold : High . . 55 (1-99) Low . . 1 (0-99) Alloc/Migr Threshold Track-Managed: High . . 85 (1-99) Low . . 1 (0-99) Guaranteed Backup Frequency . . . . . . NOLIMIT (1 to 9999 or NOLIMIT) BreakPointValue . . . . . . . . . . . . (0-65520 or blank) To answer your question about the type of migration being performed we do not run INTERVAL migration. Secondary Space management is run instead. The reason why the High/Low value is set is because of several space problems were encountered in the past. The customer did not want extra DASD allocated in this pool so a decision was taken to have the dsns in this particular pool migrated at a faster pace. I am not sure if this was the right decision, however it could be a co-incidence that ever since the threshold was adjusted (2 1/2 years ago) no more space problems were encountered. Do you see any problems besides the warning messages we could encounter because of the High/Low threshold? Thaks.
________________________________ From: "Staller, Allan" <allan.stal...@kbmg.com> To: IBM-MAIN@bama.ua.edu Sent: Tuesday, 7 February 2012 8:43 AM Subject: Re: IGD17380I - WARNING MESSAGE The extract shown does not match the thresholds shown in the message. Based on the message in this case, you should consider raising the High Allocation/Migration Threshold. The exact threshold to be chosen is a function of allocation failure (how many can you stand) and migration threshold (set in the SG) and honored by dfHSM and other storage management products. Are you performing dfHSM interval migration? <snip> I noticed the following informational message posted on some of the batch jobs. The jobs terminate successfully. Is it because of the threshold which has been set for the SMS managed storage group? IGD17380I STORAGE GROUP (PRIMSG01) IS ESTIMATED AT 56% OF CAP WHICH EXCEEDS ITS HIGH ALLOCATION THRESHOLD OF 55% Here is the threshold setup of the storage group: Allocation/migration Threshold : High . . 50 (1-99) Low . . 1 (0-99) Alloc/Migr Threshold Track-Managed: High . . 85 (1-99) Low . . 1 (0-99) Should the problem be because of the threshold setup, what values should I use? </snip> ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@bama.ua.edu with the message: INFO IBM-MAIN
