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 [email protected] with the message: INFO IBM-MAIN
