Have you contacted CA SAR Support for assistance?  They maybe better able to 
assist you

Lizette


> -----Original Message-----
> From: IBM Mainframe Discussion List [mailto:[email protected]] On
> Behalf Of venkat kulkarni
> Sent: Wednesday, December 13, 2017 9:04 AM
> To: [email protected]
> Subject: CA View SAR migration
> 
> Hello,
> 
> We have requirement of migrating SAR from told tape drive to new tape less
> drives. So, when we look at SAR related dataset, which are on tape
> 
> SAR.TARQLTY.SARTAPE.T0000092                                  TARQ51
> 
> 
> SAR.TARQLTY.SARTAPE.T0000098                                  TARQ51
> 
> SAR.TARQLTY.SARTAPE.T0000102                                  TARQ51
> 
> SAR.TARQLTY.SARTAPE.T0000093                                  TARQ52
> 
> SAR.TARQLTY.SARTAPE.T0000094                                  TARQ53
> 
> SAR.TARQLTY.SARTAPE.T0000099                                  TARQ53
> 
> SAR.TARQLTY.SARTAPE.T0000104                                  TARQ53
> 
> SAR.TARQLTY.SARTAPE.T0000109                                  TARQ53
> 
> SAR.TARQLTY.SARTAPE.T0000095                                  TARQ54
> 
> SAR.TARQLTY.SARTAPE.T0000105                                  TARQ54
> 
> SAR.TARQLTY.SARTAPE.T0000090                                  TARQ55
> 
> SAR.TARQLTY.SARTAPE.T0000096                                  TARQ55
> 
> SAR.TARQLTY.SARTAPE.T0000097                                  TARQ56
> 
> SAR.TARQLTY.SARTAPE.T0000101                                  TARQ56
> 
> 
> 
> 
> if you look at above datasets, we are using 6 tapes for SAR backup currently
> and
> 
> when we list content of tape  Ex TARQ51, we see  only
> 
> SAR.TARQLTY.SARTAPE.T0000102                                  TARQ51
> 
> 
> 
> dataset which has highest number of time stamp and in my case it was 102 for
> TARQ51 volume  and below dataset not found on tape.
> 
> SAR.TARQLTY.SARTAPE.T0000092                                  TARQ51
> 
> SAR.TARQLTY.SARTAPE.T0000098                                  TARQ51
> 
> And this is same of other volumes  also, like for TARQ53, i couldn't find
> only SAR.TARQLTY.SARTAPE.T0000109  dataset etc.
> So, we planned to migrate these available dataset from old tape to new tape
> less  disk sub system using below JCL and dataset gets copied.
> 
> //OP117SAQ JOB (660),SAURABH,CLASS=A,MSGLEVEL=(1,1),NOTIFY=&SYSUID
> 
> //STEP1 EXEC PGM=SARTCP,PARM='COPYASIS'
> 
> //*TEPLIB DD DSN=CAI.CVDELOAD,DISP=SHR
> 
> //SYSPRINT DD SYSOUT=*
> 
> //TAPEIN DD DSN=SAR.TARQLTY.SARTAPE.T0000093,
> 
> // DISP=OLD,UNIT=359D,LABEL=(1,BLP),VOL=SER=XARQ52
> 
> //TAPEOUT DD DSN=SAR.TARQLTY.SARTAPE.T0000093,
> 
> // DISP=(NEW,KEEP),UNIT=359D,LABEL=EXPDT=99000,VOL=SER=TARQ52
> 
> //SYSIN DD DUMMY
> 
> 
> 
>  Then, we updated SAR parmlib member to use new Esoteric for tape less device
> and run update Job.
> 
> 
> 
> But when we run SAR again, it was not able to use new tape less device while
> archiving reports.
> 
> 
> 
> Please correct me, if we are following right way of migration.
> 
> 
> 
> Thanks & Regards
> 
> Venkat
> 
> ----------------------------------------------------------------------
> For IBM-MAIN subscribe / signoff / archive access instructions, send email to
> [email protected] with the message: INFO IBM-MAIN

----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO IBM-MAIN

Reply via email to