IBM Mainframe Forum

Hi,

I have tapes which say "WHILECATLG" as the "Expr. / Retn date" in RMM PANEL. I change the expdt of it and it did change but on looking at simliar volumes it seems I have to find a way to change this expr./ retn date parameter to something so that it can expire when RMM HOUSE KEEPING jobs run, Because for another volume it has an EXPR. DATE / RETN. date of the past.

This is what I used to change the expdt

//EDITLOG EXEC PGM=IKJEFT01,DYNAMNBR=20
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
RMM CHANGEVOLUME 544037 EXPDT(2013/028)

Uncatalog the data set(s) on the tape. I am not an RMM expert, but WHILECATLG sounds like the tape will NOT expire as long as any data set on the tape is cataloged. Uncatalog the data set(s) and RMM will probably sratch the tape the next time housekeeping runs.

I agree with Mr. Sample. While I am not an RMM expert, long ago I was fairly expert with the CA-1 tape management system, which uses many of the same basic concepts, and that is what I would have done then.

Thx....Actually we have 22000 such tapes and so was looking for a batch job to do it...

Bad Man wrote:Thx....Actually we have 22000 such tapes and so was looking for a batch job to do it...

Ouch! I think the original idea for catalog expiration (to use the CA-1 terminology) was to automate tape retention with GDG overflow. Perhaps your use of catalog retention is inappropriate!

Regardless, it seems to me you will have to tred very cautiously here as you don't want to scratch really live production data!

I tried this and this guy does uncatalog the datasets and so I would think the tape becomes scracth right?

Actually I have two more clients who want me to do same and so though of this.

//STEP0001 EXEC PGM=IEFBR14
//DD1 DD DSN=SFTW.XXXX.XXXX.FEB2813,DISP=(OLD,UNCATLG),
// UNIT=(3490,,DEFER)
//DD1 DD DSN=SFTW.XXXX.FEB28131,DISP=(OLD,UNCATLG),
// UNIT=AFF=DD1

Hello,

Suggest you ensure that all of the files on the volume are known and accounted for. Scratching a tape with even one (1) good file could really be Bad.

If you are going to do something like this for 22k datasets, suggest you generate the jcl in groups rather than doing any uncataloging by hand.

But Dick we are just uncataloging the dataset will that affect other datasets on tape too? we are not mentioning the name of tape in this IEFBR14 jcl.

I would do this:
There is no practical limit on the number of DELETE xxx NOSCRATCH statements, where there are practical limits on the size of the JCL you can submit in one job.

Perfect Thanks