F DFHSM,QUERY ACTIVE is another good command to use when you are trying to figure out what is happening with DFHSM. If this command would have been entered, it would have shown the MIGRATION function being in hold. It is also good for showing just what DFHSM is busy doing if it ever seems to slow down. Sorry I was late to the discussion. Hope this command helps in the future.
David From: John Compton <[email protected]> To: [email protected] Date: 08/25/2015 07:42 AM Subject: Re: DFSMSHSM help request Sent by: IBM Mainframe Discussion List <[email protected]> Alan - Thank you!. Things appear to be again running as expected. John On Tue, Aug 25, 2015 at 1:35 PM, Staller, Allan <[email protected]> wrote: > F DFHSM,RELEASE MIGRATION > > This is normal behavior if there is a lack of *some resource*. The > particular function is placed on hold. > > <snip> > > </snip> > I'm taking my first faltering steps with DFSMSHSM, and have hit a > situation that I don't understand. > (I've checked around but have been unable to locate an HSM-specific > mailing list, so I'm putting my query here in the hope that someone can > provide some guidance.) > > The situation is that migration to ML2 has stopped working. > I've got 8x3390 disks in use for L1, and a further 7 for L2 (as opposed to > tape). > Using 'On demand' migration, I have been able to migrate files from L0 to > L1 and then on to L2, and also from L0 directly to L2. In order to > understand how to handle ML1 and ML2 space shortages, I deliberately forced > files to ML2 such that all 7 volumes became full. I then successfully > recalled the files back to L0. The ML2 disks are now all currently 100% > free (save for space used by VTOC, etc.) > > Now, when I try to send anything to L2, I see msg ARC0560E MIGRATION > LIMITED: NO MIGRATION LEVEL 2 DASD VOLUME AVAILABLE. Any requests I make > that are directed at L2 simply get queued. > > I've tried using DELVOL and ADDVOL commands for the disks, but that has > not shifted the problem. > I've looked at using the RECYCLE command, but it doesn't make sense to me > (I can see why you'd use RECYCLE with tape-based ML2, but not with disks...) > > It is almost certain I've got one or more of the SETSYS parameter values > in conflict with others, but I've been plugging away at this situation for > some four days now with no progress. Thankfully, I'm using a test system, > so 'bouncing' HSM is not a problem. However I do try to avoid that - it > shouldn't be necessary in my view. > > Can anybody help, please? I'm looking for advice on what commands I might > use to make ML2 space available again, and for some sort of explanation > regarding the root cause of this problem. > </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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
