Mike: here's the output from the LIST ML2 command you suggested.
As far as I can see, there is no column explicitly headed 'Volume Status',
but I find it interesting that 'Volume Type' features 6 x 'L2-UN' and 1
'L2-AV'...
- DFSMSHSM CONTROL DATASET - MIGRATE VOLUME-MCDS--- LISTING ----- AT
13:13:11 ON 15/08/25 FOR SYSTEM=S0W1
VOLSER DEVICE VOLUME THRESH FRAG HOSTID AUTO- AUTO SDSP MIN
MIGRATED DATE---TIME SPACE-MGMT BUDEV DUMP
TYPE TYPE HI--LOW INDX MIG--BACK-DUMP RECL ELIG AGE
DS-----TRKS LAST MIGRATED TYPE/AGE CATGY CLASS
HSM200 3390 L2-UN *** *** .000 **** **** **** *** *** *** 00000
000000 00/00/00 00:00 *** *** **** ********
HSM201 3390 L2-UN *** *** .000 **** **** **** *** *** *** 00000
000000 00/00/00 00:00 *** *** **** ********
HSM202 3390 L2-UN *** *** .000 **** **** **** *** *** *** 00000
000000 00/00/00 00:00 *** *** **** ********
HSM203 3390 L2-UN *** *** .000 **** **** **** *** *** *** 00000
000000 00/00/00 00:00 *** *** **** ********
HSM204 3390 L2-UN *** *** .000 **** **** **** *** *** *** 00000
000000 00/00/00 00:00 *** *** **** ********
HSM205 3390 L2-UN *** *** .000 **** **** **** *** *** *** 00000
000000 00/00/00 00:00 *** *** **** ********
HSM206 3390 L2-AV *** *** .000 **** **** **** *** *** *** 00000
000000 00/00/00 00:00 *** *** **** ********
----- END OF - MIGRATE VOLUME - LISTING -----
John
On Tue, Aug 25, 2015 at 12:48 PM, Mike Schwab <[email protected]>
wrote:
> ML2 was designed for tape, and keeps track of which tapes are full.
> Once they are full, you have to recycle them to write on them.
> Perhaps they haven't modified this tracking for ML2 disk.
>
>
> http://www-01.ibm.com/support/knowledgecenter/SSLTBW_2.1.0/com.ibm.zos.v2r1.arcf000/s4316.htm
> Try HSEND LIST ML2 ODS('hlq.system.hsend.list.ml2')
> Not sure if that lists the volume status.
>
> On Tue, Aug 25, 2015 at 4:00 AM, John Compton <[email protected]>
> wrote:
> > Hello.
> >
> > 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.
> >
> > TIA
> > John
> >
> > ----------------------------------------------------------------------
> > 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
