MVSFORUMS.com :: View topic - Problem with RMM and VRS definitions with GDG data sets

Problem with RMM and VRS definitions with GDG data sets

through

[^/[Print]\]

MVSFORUMS.com -> Data Management

#1: Problem with RMM and VRS definitions with GDG data sets Author: warp5, Location: Germany

Posted: Thu Feb 02, 2012 8:12 am
—
We have transferred from CA1 to RMM. After we are using RMM we have found that cataloged datasets on tape volumes are being scratched even
though the datasets are still cataloged and valid. We had a default
expiration of 7 days, when a data set is older than the 7 days it will
be scratched even though it should not be because it is still cataloged and a GDG. We also have some VRS definitions. The question is, what definitions are necessary to make sure that cataloged datasets, in particular GDG datasets, will not be scratched as long as they are cataloged? Any ideas would be appreciated.

One of our VRS definitions that should apply to the following two cases:

Code:

//*---------------------------------------------------------------------
//* VRS FOR GENERATION DATA GROUPS
//*---------------------------------------------------------------------
RMM ADDVRS DSNAME('**.G%%%%V00') GDG CYCLES COUNT(99999) -
DELDATE(1999/365) LOCATION(HOME) PRIORITY(0) OWNER(LIBRARY) -
WHILECATALOG

Here is a GDG that looks OK:

Code:

Data set name . . : 'PDBP1D.DBINS.DSNLOBTS.ICP.G0251V00'
Volume serial . . : B45094 Physical file sequence number . . : 1
Owner . . . . . . : UDBP1AD Data set sequence number . . . . : 1
Job name . . . . : ICP10C06
Step name . . . . : DSNUPROC Record format . . . . : FB
Program name . . : DSNUTILB Block size . . . . . : 28672
DD name . . . . . : SYS00078 Logical record length : 4096
Create date . . . : 2012/02/01 YYYY/MM/DD Block count . . . . . : 24
Create time . . . : 20:27:39 Total block count . . : 24
Data set size (KB) . : 672
Expiration date . : 2012/05/01 YYYY/MM/DD Percent of volume . . : 0
Original . . . . : YYYY/MM/DD Device number . . . . : D287
System id . . . . : Z9P1
Last job name . . : ICP10C06 Last DD name . . . . : SYS00078
Last step name . : DSNUPROC Last device number . : D287
Last program name : DSNUTILB
Date last read . : 2012/02/01 VRS management value :
Date last written : 2012/02/01 Management class . . :
Data class . . . . . :
Retention date . : WHILECATLG Storage class . . . . :
VRS retained . . : YES Storage group . . . . :

And here is a GDG that we can not explain at all:

Code:

Data set name . . : 'BACKUP.MVS040.SFULL.PRIM.G0504V00'
Volume serial . . : B21016 Physical file sequence number . . : 1
Owner . . . . . . : JOBTRAC Data set sequence number . . . . : 1
Job name . . . . : BKMVS040
Step name . . . . : DMMVS040 Record format . . . . : U
Program name . . : ADRDSSU Block size . . . . . : 32000
DD name . . . . . : BACKUP1 Logical record length : 255
Create date . . . : 2012/02/02 YYYY/MM/DD Block count . . . . . : 40191
Create time . . . : 06:30:57 Total block count . . : 40191
Data set size (KB) . : 1255969
Expiration date . : 1999/00/00 YYYY/MM/DD Percent of volume . . : 0
Original . . . . : 1999/00/00 YYYY/MM/DD Device number . . . . : D180
System id . . . . : Z9P1
Last job name . . : BKMVS040 Last DD name . . . . : BACKUP1
Last step name . : DMMVS040 Last device number . : D180
Last program name : ADRDSSU
Date last read . : 2012/02/02 VRS management value :
Date last written : 2012/02/02 Management class . . :
Data class . . . . . :
Retention date . : Storage class . . . . :
VRS retained . . : NO Storage group . . . . :

MVSFORUMS.com -> Data Management

output generated using printer-friendly topic mod. All times are GMT - 5 Hours

Page 1 of 1