ADRDSSU and updated data

[samb01]

Hello,

i would like to dump only upadated datasets with ADRDSSU because, my dump is using a huge number of tape actually (24).

My sysin is

Code: Select all

DUMP OUTDDNAME(OUTDD1)                    -                         
     DATASET(INCL(                        -                         
                  XFAL*.**)               -                         
                    XFAL*.V*.*.Q*.OUT       -                         
                                      ))  -                         
CANCELERROR TOL(ENQF) OPTIMIZE(4) FORCECP(0) WAIT(1,2) SHARE



There are lots of dataset so many tape is used...

Code: Select all

DSN=UVALUV.VBKPDEQ.PROD4.G0124V00,                           
VOLS=214023,329441,329923,331277,210478,363341,332669,212502,
VOLS=213012,336337,337953,373223,224829,340591,218462,342807,
VOLS=343369,214649,386823,345683,281952,347223,347393,301838,
VOLS=351801,TOTALBLOCKS=893153                               



I would like to use less tape...

I tried the compress option

Code: Select all

CANCELERROR TOL(ENQF) OPTIMIZE(4) COMPRESS FORCECP(0) WAIT(1,2) SHARE



But the number of tape is the same...

Is-it possible to dump only updated datasets... ?

Thanks for your hlep.

[NicC]

Well, assuming that you have read the manual and have not found anything why do you expect us to come up with something that is not in the manual. The manual explains what can be done so if it is not there then it can not be done - at least, not without some preparatory program that would generate the control cards for you.

[samb01]

Ok, thanks for your help...

[dick scherrer]

Hello,

What if every file is "updated" (i.e. a timestamp) every day or whatever cycle?

[enrico-sorichetti]

even if ADRDSSU aka DFDSS lets You <process> dataset using the filter clause BY DSCHA
using it for MANUAL backups is just one of the worst ideas hanging around
do You realize how much clerical work will be needed to find out on what tape the dataset You just lost resides ???

dataset management based on reference bit and change bit should be left to AUTOMATED dasd managers ...
they KNOW how to handle history... You do not, or at least not as well as them !