Re: CA View SAR migration

2017-12-17 Thread Lizette Koehler
I would contact CA for assistance.  You will get answers, but will they be 
right for  your situation would need to be determined by you.

 

An old manager of mine use to say:

 

We pay a lot of money to the vendor for their product. Use their support team.  
Otherwise why have the product if we do not need their support.

 

 

 

Lizette

 

 

From: venkat kulkarni [mailto:venkatkulkarn...@gmail.com] 
Sent: Sunday, December 17, 2017 4:17 AM
To: IBM Mainframe Discussion List <IBM-MAIN@listserv.ua.edu>; Lizette Koehler 
<stars...@mindspring.com>
Subject: Re: CA View SAR migration

 

Thanks for reply. 

 

No, I have not contacted CA yet. I wanted to do my self. So, i tried reading CA 
View reference guide and with different utility. I made some progress but not 
fully. If any body can throw some light on this will be great help. 

 

I used SARPAC utility to find report about SYSOUT reports and SARTSLIST etc to 
find individual report on each database. 

 

I referred  <https://communities.ca.com/thread/241736589> 
https://communities.ca.com/thread/241736589 for this purpose.

 

My query is, using below JCL how are we going to migrate SAR database from old 
tape drive to new VTL 

 

 

Where and how do we specify that my report should copy from old tape drive to 
new VTL and now  SAR should use new VTL library for archive purpose. 

 

/SARPAC   EXEC PGM=SARPAC,PARM='SARD.OPR,'

//* STEPLIB DD DSN=CAI.CVDELOAD,DISP=SHR 

//SYSPRINT DD  SYSOUT=* *

//SARDRLST DD  SYSOUT=* *

//SYSOUT   DD  SYSOUT=*  

//SORTLIB  DD  DSN=SYS1.SORTLIB,DISP=SHR 

//SORTWK01 DD  UNIT=SYSDA,SPACE=(CYL,(10),,CONTIG)

//SORTWK02 DD  UNIT=SYSDA,SPACE=(CYL,(10),,CONTIG)

//SORTWK03 DD  UNIT=SYSDA,SPACE=(CYL,(10),,CONTIG)

//SYSINDD  * 

/*

 

I remember, there is UNITSPEC parameter where we can put ESOTERIC for current 
tape drive but i dont find any single document giving clear picture on this 
migration.

 

Kindly suggest.

 

 

On Wed, Dec 13, 2017 at 8:50 PM, Lizette Koehler <stars...@mindspring.com 
<mailto:stars...@mindspring.com> > wrote:

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

Lizette



> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU 
> <mailto:IBM-MAIN@LISTSERV.UA.EDU> ] On
> Behalf Of venkat kulkarni
> Sent: Wednesday, December 13, 2017 9:04 AM
> To: IBM-MAIN@LISTSERV.UA.EDU <mailto:IBM-MAIN@LISTSERV.UA.EDU> 
> 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.T092  TARQ51
>
>
> SAR.TARQLTY.SARTAPE.T098  TARQ51
>
> SAR.TARQLTY.SARTAPE.T102  TARQ51
>
> SAR.TARQLTY.SARTAPE.T093  TARQ52
>
> SAR.TARQLTY.SARTAPE.T094  TARQ53
>
> SAR.TARQLTY.SARTAPE.T099  TARQ53
>
> SAR.TARQLTY.SARTAPE.T104  TARQ53
>
> SAR.TARQLTY.SARTAPE.T109  TARQ53
>
> SAR.TARQLTY.SARTAPE.T095  TARQ54
>
> SAR.TARQLTY.SARTAPE.T105  TARQ54
>
> SAR.TARQLTY.SARTAPE.T090  TARQ55
>
> SAR.TARQLTY.SARTAPE.T096  TARQ55
>
> SAR.TARQLTY.SARTAPE.T097  TARQ56
>
> SAR.TARQLTY.SARTAPE.T101  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.T102  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.T092  TARQ51
>
> SAR.TARQLTY.SARTAPE.T098  TARQ51
>
> And this is same of other volumes  also, like for TARQ53, i couldn't find
> only SAR.TARQLTY.SARTAPE.T109  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=
>
> //STEP1 EXEC PGM=SARTCP,PARM='COPYASIS'
>
> //*TEPLIB DD DSN=CAI.CVDELOAD,DI

Re: CA View SAR migration

2017-12-17 Thread venkat kulkarni
Thanks for reply.

No, I have not contacted CA yet. I wanted to do my self. So, i tried
reading CA View reference guide and with different utility. I made some
progress but not fully. If any body can throw some light on this will be
great help.

I used SARPAC utility to find report about SYSOUT reports and SARTSLIST etc
to find individual report on each database.

I referred https://communities.ca.com/thread/241736589 for this purpose.

My query is, using below JCL how are we going to migrate SAR database from
old tape drive to new VTL


Where and how do we specify that my report should copy from old tape drive
to new VTL and now  SAR should use new VTL library for archive purpose.

/SARPAC   EXEC PGM=SARPAC,PARM='SARD.OPR,'

//* STEPLIB DD DSN=CAI.CVDELOAD,DISP=SHR

//SYSPRINT DD  SYSOUT=* *

//SARDRLST DD  SYSOUT=* *

//SYSOUT   DD  SYSOUT=*

//SORTLIB  DD  DSN=SYS1.SORTLIB,DISP=SHR

//SORTWK01 DD  UNIT=SYSDA,SPACE=(CYL,(10),,CONTIG)

//SORTWK02 DD  UNIT=SYSDA,SPACE=(CYL,(10),,CONTIG)

//SORTWK03 DD  UNIT=SYSDA,SPACE=(CYL,(10),,CONTIG)

//SYSINDD  *

/*

I remember, there is UNITSPEC parameter where we can put ESOTERIC for
current tape drive but i dont find any single document giving clear picture
on this migration.

Kindly suggest.


On Wed, Dec 13, 2017 at 8:50 PM, Lizette Koehler <stars...@mindspring.com>
wrote:

> Have you contacted CA SAR Support for assistance?  They maybe better able
> to assist you
>
> Lizette
>
>
> > -Original Message-
> > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> > Behalf Of venkat kulkarni
> > Sent: Wednesday, December 13, 2017 9:04 AM
> > To: IBM-MAIN@LISTSERV.UA.EDU
> > 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.T092  TARQ51
> >
> >
> > SAR.TARQLTY.SARTAPE.T098  TARQ51
> >
> > SAR.TARQLTY.SARTAPE.T102  TARQ51
> >
> > SAR.TARQLTY.SARTAPE.T093  TARQ52
> >
> > SAR.TARQLTY.SARTAPE.T094  TARQ53
> >
> > SAR.TARQLTY.SARTAPE.T099  TARQ53
> >
> > SAR.TARQLTY.SARTAPE.T104  TARQ53
> >
> > SAR.TARQLTY.SARTAPE.T109  TARQ53
> >
> > SAR.TARQLTY.SARTAPE.T095  TARQ54
> >
> > SAR.TARQLTY.SARTAPE.T105  TARQ54
> >
> > SAR.TARQLTY.SARTAPE.T090  TARQ55
> >
> > SAR.TARQLTY.SARTAPE.T096  TARQ55
> >
> > SAR.TARQLTY.SARTAPE.T097  TARQ56
> >
> > SAR.TARQLTY.SARTAPE.T101  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.T102  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.T092  TARQ51
> >
> > SAR.TARQLTY.SARTAPE.T098  TARQ51
> >
> > And this is same of other volumes  also, like for TARQ53, i couldn't find
> > only SAR.TARQLTY.SARTAPE.T109  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=
> >
> > //STEP1 EXEC PGM=SARTCP,PARM='COPYASIS'
> >
> > //*TEPLIB DD DSN=CAI.CVDELOAD,DISP=SHR
> >
> > //SYSPRINT DD SYSOUT=*
> >
> > //TAPEIN DD DSN=SAR.TARQLTY.SARTAPE.T093,
> >
> > // DISP=OLD,UNIT=359D,LABEL=(1,BLP),VOL=SER=XARQ52
> >
> > //TAPEOUT DD DSN=SAR.TARQLTY.SARTAPE.T093,
> >
> > // 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.
> >
> &g

Re: CA View SAR migration

2017-12-13 Thread Lizette Koehler
Have you contacted CA SAR Support for assistance?  They maybe better able to 
assist you

Lizette


> -Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of venkat kulkarni
> Sent: Wednesday, December 13, 2017 9:04 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> 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.T092  TARQ51
> 
> 
> SAR.TARQLTY.SARTAPE.T098  TARQ51
> 
> SAR.TARQLTY.SARTAPE.T102  TARQ51
> 
> SAR.TARQLTY.SARTAPE.T093  TARQ52
> 
> SAR.TARQLTY.SARTAPE.T094  TARQ53
> 
> SAR.TARQLTY.SARTAPE.T099  TARQ53
> 
> SAR.TARQLTY.SARTAPE.T104  TARQ53
> 
> SAR.TARQLTY.SARTAPE.T109  TARQ53
> 
> SAR.TARQLTY.SARTAPE.T095  TARQ54
> 
> SAR.TARQLTY.SARTAPE.T105  TARQ54
> 
> SAR.TARQLTY.SARTAPE.T090  TARQ55
> 
> SAR.TARQLTY.SARTAPE.T096  TARQ55
> 
> SAR.TARQLTY.SARTAPE.T097  TARQ56
> 
> SAR.TARQLTY.SARTAPE.T101  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.T102  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.T092  TARQ51
> 
> SAR.TARQLTY.SARTAPE.T098  TARQ51
> 
> And this is same of other volumes  also, like for TARQ53, i couldn't find
> only SAR.TARQLTY.SARTAPE.T109  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=
> 
> //STEP1 EXEC PGM=SARTCP,PARM='COPYASIS'
> 
> //*TEPLIB DD DSN=CAI.CVDELOAD,DISP=SHR
> 
> //SYSPRINT DD SYSOUT=*
> 
> //TAPEIN DD DSN=SAR.TARQLTY.SARTAPE.T093,
> 
> // DISP=OLD,UNIT=359D,LABEL=(1,BLP),VOL=SER=XARQ52
> 
> //TAPEOUT DD DSN=SAR.TARQLTY.SARTAPE.T093,
> 
> // 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
> lists...@listserv.ua.edu with the message: INFO IBM-MAIN

--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN


CA View SAR migration

2017-12-13 Thread venkat kulkarni
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.T092  TARQ51


SAR.TARQLTY.SARTAPE.T098  TARQ51

SAR.TARQLTY.SARTAPE.T102  TARQ51

SAR.TARQLTY.SARTAPE.T093  TARQ52

SAR.TARQLTY.SARTAPE.T094  TARQ53

SAR.TARQLTY.SARTAPE.T099  TARQ53

SAR.TARQLTY.SARTAPE.T104  TARQ53

SAR.TARQLTY.SARTAPE.T109  TARQ53

SAR.TARQLTY.SARTAPE.T095  TARQ54

SAR.TARQLTY.SARTAPE.T105  TARQ54

SAR.TARQLTY.SARTAPE.T090  TARQ55

SAR.TARQLTY.SARTAPE.T096  TARQ55

SAR.TARQLTY.SARTAPE.T097  TARQ56

SAR.TARQLTY.SARTAPE.T101  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.T102  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.T092  TARQ51

SAR.TARQLTY.SARTAPE.T098  TARQ51

And this is same of other volumes  also, like for TARQ53, i couldn't find
only SAR.TARQLTY.SARTAPE.T109  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=

//STEP1 EXEC PGM=SARTCP,PARM='COPYASIS'

//*TEPLIB DD DSN=CAI.CVDELOAD,DISP=SHR

//SYSPRINT DD SYSOUT=*

//TAPEIN DD DSN=SAR.TARQLTY.SARTAPE.T093,

// DISP=OLD,UNIT=359D,LABEL=(1,BLP),VOL=SER=XARQ52

//TAPEOUT DD DSN=SAR.TARQLTY.SARTAPE.T093,

// 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 lists...@listserv.ua.edu with the message: INFO IBM-MAIN