I am at SHARE right now, so I don't have this in front of me, so I may be a bit
off (if so, someone should be able to correct me), but you should not have to
change your ACS routines at all. All you need to do is remove the old VTS from
your STORGRP and add the new VTS. All new allocations will then go to the new
VTS, while allocations for existing volumes will be allocated to the library
that contains the volume that is required to satisfy the request.
>>> Sebastian Welton <sebast...@welton.de> 03/18/10 9:03 AM >>>
Many thanks for all the replies, they've been very helpful. I'll admit I'm
pretty rusty in this area but got roped in to doing it as I've done similar
(but not this type of migration) in the past so forgive my seemingly 'dumb'
questions. I've now found some material to read through (changing Google
search terms seems to have helped!) but just want to clarify a couple of things:
John McKown said:
---
Aren't the VTSes managed by SMS? If so, then the UNIT= is not very
important. You have two separate libraries. Make a new Storage Group for the
new library. Now, in the STORGRUP ACS routine, assign the new STORGRUP where
you current assign the old STORGRUP value. Presto! Everything that went to
the old VTS, now goes to the new VTS. This does __NOT__ affect access to
existing tape data in the old VTS as it is still in the old STORGRUP, which
is assigned to the old VTS library.
---
The current, old, one is and the new one will be however the above has
confused me a bit. In my JCL I say UNIT=VTS which automatically points me to
a drive in the library. Now in my storage group I have:
WHEN (&STORCLAS = 'VTS')
DO
SET &STORGRP = 'VTS'
EXIT
END
and in my sroage class I have:
WHEN (&UNIT = &VALID_TAPELIB)
DO
SET &STORCLAS = 'VTS'
EXIT
END
and in my data class I have:
FILTLIST VALID_TAPE INCLUDE('CASS','3490')
FILTLIST VALID_TLIB1 INCLUDE('3590','VTS')
I would take I just need to add entries to point to the new VTS, i.e.
WHEN (&STORCLAS = 'VTS1')
DO
SET &STORGRP = 'VTS'
EXIT
END
Yet what I don't understand, is how does it know to use the new VTS? By this
I mean the old VTS has a range of addresses unique to it along with the new
one. The dataset HLQs are the same, the JCL hasn't changed so in my eyes its
going to pick any available addrss in either VTS to mount the tape. Or am I
having a brain drain?
Next up...
Darth Keller said:
---
Have you considered how you're moving your old data over to the new
library? I've used OpenTec's TapeCopy product for the last 2 moves and
plan on using it for the next move too. It works great - keeps all the
CA1 information in-sync - multi-volume, stacked, cataloged/uncataloged -
it handled it all. I'm sure others can say the same about other products.
Moving the new allocations over to the new library is pretty
straight-forward - moving the old data over can be a bit more tricky and
you'll need to do some careful planning to get it done.
---
Thats what I'm working on at this moment. No money for 3rd party products
and as you say, new allocations (if I get the above working!) should be no
problem. I need to mainly move HSM ML2 data, some SMS backed up data and
some other 'random' data over. I'm currently creating the reports to see
what there is and how much needs to be moved and then work out a way of
doing it. Its a pity, at least I can't find one, similar to DFSMSdss MOVE
for a dataset which would be very nice...
Thanks, Seb
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
CONFIDENTIALITY/EMAIL NOTICE: The material in this transmission contains
confidential and privileged information intended only for the addressee. If
you are not the intended recipient, please be advised that you have received
this material in error and that any forwarding, copying, printing,
distribution, use or disclosure of the material is strictly prohibited. If you
have received this material in error, please (i) do not read it, (ii) reply to
the sender that you received the message in error, and (iii) erase or destroy
the material. Emails are not secure and can be intercepted, amended, lost or
destroyed, or contain viruses. You are deemed to have accepted these risks if
you communicate with us by email. Thank you.
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@bama.ua.edu with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
