search cancel

How to move a CA CSM file system from one volser to another?

book

Article ID: 113564

calendar_today

Updated On:

Products

Mainframe Software Manager (Chorus Software Manager)

Issue/Introduction



We are trying to install new recommended service using CA-CSM but have ran  out of space on DASD. is there a way to release and delete the old CA-CSM-data that are applied into SMP? 

Environment

Release:
Component: MSM

Resolution

 IDCAMS REPRO can be used to move a file system from one volser that is almost 100% used to another volser with more available space. 

This is an example of the LISTCAT JCL to identify the volser the file system is on and the number of cylinders being used: 
//S010 EXEC PGM=IDCAMS 
//SYSPRINT DD SYSOUT=* 
//SYSIN    DD * 
LISTCAT ENT('HLQ.CACSM.ZFS') ALL 
/* 


This JCL WILL REPRO HLQ.CACSM.ZFS to HLQ.NEWTEMP.ZFS. 
//DEFINRW EXEC PGM=IDCAMS 
//SYSPRINT DD SYSOUT=* 
//SYSUDUMP DD SYSOUT=* 
//AMSDUMP  DD SYSOUT=* 
//SYSIN    DD * 
DELETE HLQ.NEWTEMP.ZFS CLUSTER 

SET MAXCC=0 

DEFINE CLUSTER ( - 
NAME(HLQ.NEWTEMP.ZFS) - 
LINEAR CYL(200 200) - 
SHAREOPTIONS(3,3) - 

/* 
//   EXEC PGM=IDCAMS 
//SYSPRINT DD SYSOUT=* 
//INDD     DD DISP=SHR,DSN=HLQ.CACSM.ZFS 
//OUTDD    DD DISP=SHR,DSN=HLQ.NEWTEMP.ZFS 
//SYSIN    DD * 
REPRO - 
INFILE(INDD) - 
OUTFILE(OUTDD) 
/* 



Note that the original file system name must be retained. This means that you may want to REPRO the original name to a temporary name, delete the original name then re-allocate it to a volser with more space available then REPRO the temporary name back to the original name.