NB if the underlying volumes are thin provisioned, then the unused space is not
using any capacity.
Worth considering if it makes your migration simpler.
Ron Hawkins
Director, Ipsicsopt Pty Ltd (ACN: 627 705 971)
m: +61 400029610 | h: +61 387399252 | f: +1 4087912585 | email:
ron.hawk...@ipsicsopt.com
-----Original Message-----
From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of
VinothM
Sent: Wednesday, 13 March 2019 22:20
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [IBM-MAIN] spool volume migration
Hi All,
i am planning to migrate the spool volumes using $MSPL command and i have
already completed spool migration on other plexes.
But here the scenario is different, we have 6 Mod-54 volumes and all the
volumes are not fully allocated and only 50% allocated, so i am planning to
migrate and make it to 3 MOD-54 volumes with full cylinders allocated.
Volume . : SPJES1
Command ===>
Unit . . : 3390
Volume Data VTOC Data Free Space Tracks Cyls
Tracks . : 982,800 Tracks . : 14 Size
. . : 491,400 32,760
%Used . : 50 %Used . . : 1
Largest . : 491,400 32,760
Trks/Cyls: 15 Free DSCBS: 696 Free
Extents . : 1
All the volumes are active and used and only 20% used on an average.
Below is command to migrate with MAX space
$MSPL(spool1),target=spool2,space=max
Please suggest me that whether this command will make the target spool volume
to get 100% allocated and migrated successfully.
Thanks,
Vinoth M
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions, send email to
lists...@listserv.ua.edu with the message: INFO IBM-MAIN
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
