ADSM-L

Export/import

1997-05-01 16:22:52
Subject: Export/import
From: Julie Phinney <julphinn AT EMPHESYS.E-MAIL DOT COM>
Date: Thu, 1 May 1997 16:22:52 EDT
I am getting ready to move (via export/import) the clients from one
MVS system to another.  I was wondering if any of you who've done it
could share your known "things to watch out for" list.  I plan to
1. Create a new devclass on each ADSM server, with a new HLQ that is
   defined to the RACF on the one MVS system, and ACF2 on the other
   MVS system. This devclass would have EXP=99365
2. Run the export node filed=al devclass=newclass scratch=yes
3. Run an eject job to get the tapes out of the silos
4. Have the tapes carried over to the silos for the other MVS system
5. Run the import node filed=all devclass=newclass vol=xxxxxx,xxxxxx
6. Run another eject, have them carried back.
How can I return those tapes to scratch status?  Should I specify an
expiration date on the devclass, and have to change it every day
(assuming this export/import will be daily and go on for a long time).
When you ran the import, did you do it via TSO in batch?  If so,
assuming you had a long list of vols to specify, how did you continue
to the next line?  Just type them all in and not worry about a
continuation character in col 72?
Am I missing anything here.. any way to make my life easier?
Thanks for any advice!
Julie Phinney
JULPHINN @ EMPHESYS.E-MAIL.COM
<Prev in Thread] Current Thread [Next in Thread>