RCVJRN after Hardwarechange

[Former Member]

Hello,

we use the strrcvjrn from the R3TOOLS Libary. Now we have a new Tapelibary and we need to change this for the rcvjrn Job. We cant find the parameter to change. Change of DTAARA "DEV" in the R3TOOLS didn't help.

Our BRMS Jobs are all running fine after chenging the policys to the new Tapelibary.

Regards

Ralf

[Former Member]

We find the solution. In the R3TOOLS Libary there is the file SAPSID. We have to change the parameter for the TAPMLBXX . Now it works.

Regards

Ralf

[christoph_ostrop]

yes, you are right.

we too, have in table SAPSID a column with TAPMLBnn entries,

but in our R3TOOLS implementation, these values in that column are not used by any pgm.

so the R3TOOLS library is different in several customer installations.

but, by the way, you could avoid changing the mentioned steps and entries

by renaming the name of the TAPMLBnn (not rename the resourceName) to the value you have had before.

=> wrkcfgsts *dev tapmlb* 

=> option 2 = vryoff

=> option 8 => wrkdevd  tapmlb*

=> option 7 = rename

=> vryon  again 

=> INZBRM  *DEVICE 

..... and that's it.

HTH

Christoph

[christoph_ostrop]

maybe you have an identical solution as we have here?

if you are using BRMS (Backup and Media Recovery Services) this name of the TAPMLBxx should be mentioned in an *EXIT Entry within the backup control group

a)

for example, we have a backup control group DAILY and in one of several *EXIT-entrys there is the SBMJOB of the R3TOOLS/RCVJRNBRM -Backup-Job with PARM('TAPMLBnn')

b)

normally, during the BRMS Maintenance operation (in our case a self-created CLP with 3 BRMS-Commands like MOVMEDBRM, PRTMOVBRM  and STRMNTBRM), this JRNRCV-backup-job should be stopped, then executed these 3 BRMS-CMDs, and after that, the R3TOOLS/RCVJRNBRM will be submitted again over the day.  -  so, in our CLP we have the second place for naming TAPMLBnn als PARM.

HTH

Christoph