You should stop all tape processing, (RMM or CA-1, or whatever you have),
because while the VOLCAT is not available no changes will work correctly.
Actually IBM says:
Quiesce tape library management with console command V
SMS,LIBRARY(libname),ALL,OFFLINE for each library sharing the volume catalog to
be moved.
Even if your volcat is really-really big, it should take no longer than a
minute or two.
Don't skip steps in the example.
For a site that volsers all start with "V" you will probably have to do both.
If you have multiple Volser ranges you might have more.
SYS1.VOLCAT.VGENERAL
SYS1.VOLCAT.VV (this is called a specific volcat, hlq.VOLCAT.Vx ('x'
being first character of a volser))
Library records reside in the general VOLCAT
Volume records may reside in either the general or specific VOLCAT – specific
VOLCAT searched first.
If one is created with imbed and replicate, the other will likely be as well.
You can run the diagnose and examine ahead of time and get them out of the way
(and to make sure you don't have anything to fix).
When you export the catalog(s), do it twice as in the suggestion within step 3
because you can never have too many backups. Don't worry about the info apars
for making it faster, because unless you have millions of volumes the time
saved will not really be measurable
You will need to skip step 4 because you are changing the attributes of your
new catalog.
There are some special directions if you have multiple master catalogs that you
can skip if you have just one master catalog.
Incidentally if you ever want to just move the volcat and not change anything,
IBM has another page at
https://www.ibm.com/support/pages/how-move-volcat-new-volume that covers it.
Let me know if you need help building the JCL, It seems like a lot of work,
but it's actually quite straightforward if you read the directions.
Brian
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN
