|
View previous topic :: View next topic
|
| Author |
Message |
jdlowndes
New User
Joined: 19 Jan 2013
Posts: 1
Location: USA
|
|
|
|
Good afternoon ladies and gents,
I an issue that I greatly need some assistance with, here is the issue:
I need to move approximately 150 or so VSAM files from some old MOD3 volumes to new MOD27 volumes. Both the old and new volumes are SMS controlled. The volumes are also both in the same storage group but the MOD3s have been DISNEW'ed for a couple of months now.
Does anyone have any suggestions on how to go about completing this task. I greatly appreciate your assistance in advance!!!!
(This is a duplicate post from the JCL forum, because I was "Blind" and didn't see the VSAM forum first!!) |
|
| Back to top |
|
 |
dick scherrer
Moderator Emeritus
Joined: 23 Nov 2006
Posts: 19244
Location: Inside the Matrix
|
|
|
|
Hello and welcome to the forum,
Suggest you work with your storage management people.
They may already have a recommend/standard process for doing this.
Better to use the existing method rather than create a new one. |
|
| Back to top |
|
|
jan.sehlbach
New User
Joined: 28 Mar 2014
Posts: 3
Location: Germany
|
|
|
|
DFSMSdss (ADRDSSU) is your friend
i work with this parameter to empty a volume, but this will only works if datasets are not in-use.
| Code: |
//S1 EXEC PGM=ADRDSSU,PARM='UTILMSG=YES'
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
COPY -
DS( -
INC( -
** -
) -
EXC(SYS1.**) -
) -
LIDY( -
(VPU004,3390) , -
(VPU005,3390) , -
) -
VOLCOUNT(*) -
DEL -
ADMIN -
PURGE -
RECAT(*) -
ALLD(*) -
ALLX SELECTMULTI(ANY)
/* |
if you will only move your specific VSAM you must edit the inc parm, and maybe you don't need the parm ADMIN if you have the rights.
And "LIDY" you must change to your DISNEW Volser.
For the other parameter check the DFSMSdss Storage Administration Guide. |
|
| Back to top |
|
|
|
|
