Portal | Manuals | References | Downloads | Info | Programs | JCLs | Mainframe wiki | Quick Ref
IBM Mainframe Computers Forums Index
 
Register
 
IBM Mainframe Computers Forums Index Mainframe: Search IBM Mainframe Forum: FAQ Memberlist Profile Log in to check your private messages Log in
 
Question about dataset sequence number on a tape volume
Goto page Previous  1, 2
 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM
View previous topic :: :: View next topic  
Author Message
expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8725
Location: Welsh Wales

PostPosted: Thu May 31, 2018 5:11 pm    Post subject:
Reply with quote

DFdss incremental backup does exactly what it says on the tin

You can select datasets by dataset mask, and also select only those that have not been previously backed up, so guess that would only leave new creations.

Please, please don't tell me that you were considering backing up each dataset to one label, please, just don't.

Have you investigated your storage management people, really great people icon_biggrin.gif , to see if the DASD management software can do this, products like DFhsm use around 95% of any tapes automatically stacking datasets and also keeps track of exactly where they are. DFhsm can also create duplex copies too, as can DFdss

Had you have described the requirement accurately at the START of this thread maybe a much better solution would have been found much faster
Back to top
View user's profile Send private message

Willy Jensen

Active User


Joined: 01 Sep 2015
Posts: 228
Location: Denmark

PostPosted: Thu May 31, 2018 7:11 pm    Post subject:
Reply with quote

To me too this looks like a backup rather than a copy application.
Back to top
View user's profile Send private message
steve-myers

Active Member


Joined: 30 Nov 2013
Posts: 667
Location: The Universe

PostPosted: Thu May 31, 2018 8:59 pm    Post subject:
Reply with quote

harisukumaran wrote:
I was told that automated backups would require the dataset names to follow a pattern. Datasetsl names in my list do not have any naming pattern and so I need to develop this custom process.
I think you'll find there is a pattern, if you look carefully. As expat says, ADRDSSU's data set matching capability is very flexible. The only advantage of your idea is recovery of the backed up data sets should be much easier than using ADRDSSU.
harisukumaran wrote:
Also, my tape management person tells me that tapes backed up for extended periods of time need to be stacked with datasets.
At one level I agree with your tape management person. Stacking is not as fast - even if done properly, which your BPXWDYN idea is not doing, as documented before, as you think. I recall - this was in 1989 or 1990 - watching an old style drive with round tapes. It would write normally for a few seconds, then stop, the drive seemed to backup the tape, read something, write something, then write normally for a second or two, and so on. It turned out it was DFHSM stacking migrated data sets to the tape. This pause between files was MVS data management starting a new file.
Back to top
View user's profile Send private message
Pete Wilson

Active User


Joined: 31 Dec 2009
Posts: 470
Location: London

PostPosted: Sat Jun 09, 2018 8:31 pm    Post subject:
Reply with quote

Curious why would you want to backup GDG's which are effectively a backup anyway?

One easy way would be to use DFDSS DUMP that just takes all the datasets into a single backup dataset. (The only issue with this would be that it won't backup datasets that have been migrated/archived by DFHSM or similar.)

You can specify dataset name masks that would capture a lot of GDG names with a single line, and you can specify the relative generation numbers you want to capture. So specifying NAME(0) would only backup the latest generations. You can also refine the selection further if you want to using the BY selection criteria as well to check on things like creation date, last reference date and change flags.

e.g.
//DUMP EXEC PGM=ADRDSSU
//SYSPRINT DD SYSOUT=*
//TAPE DD DSN=BACKUP.DUMP(+1),DISP=(,CATLG),
// UNIT=VTS,VOL=(,,,255)
//SYSIN DD *
DUMP ODD(TAPE) ALLE -
DS(INC( -
G%%%.*.%%.MASK1(0) -
X%.*.*.MASK2(0) -
AN.OTHER.ONE*(0) -
))

Depending on your TAPE subsystem you may or may not want to code the COMPRESS parameter in the SYSIN or a DATACLAS in the JCL that provides ZEDC compression. Some TAPE subsystems such as DLM do their own compression so no point in coding COMPRESS.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> JCL & VSAM All times are GMT + 6 Hours
Goto page Previous  1, 2
Page 2 of 2

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts VSAM KSDS backup in TAPE joy_dey81 JCL & VSAM 3 Fri Oct 05, 2018 1:31 pm
No new posts DUMP A Multi volume datasets and rest... lind sh JCL & VSAM 6 Mon Oct 01, 2018 12:02 pm
No new posts Number of Packages required for stati... manojthokala7 DB2 4 Mon Sep 17, 2018 7:14 pm
No new posts Zipping a mainframe dataset using OSH... raviyuvi All Other Mainframe Topics 12 Thu Sep 06, 2018 7:13 pm
No new posts What is the purpose of z/OS dataset e... vasanthz All Other Mainframe Topics 3 Fri Aug 31, 2018 12:56 am

Facebook
Back to Top
 
Job Vacancies | Forum Rules | Bookmarks | Subscriptions | FAQ | Polls | Contact Us