IBM Mainframe Forum Index
Log In
IBM Mainframe Forum Index Mainframe: Search IBM Mainframe Forum: FAQ Register

GDG versions not being selected for backup/migrate

IBM Mainframe Forums -> SYNCSORT
Post new topic   Reply to topic
View previous topic :: View next topic  
Author Message
Randy Wood

New User

Joined: 17 Apr 2014
Posts: 1
Location: USA

PostPosted: Wed Aug 27, 2014 10:24 pm
Reply with quote

We have a problem with old versions of a GDG not being selected by SMS for backup/migrate because of contention with a job that is running to create a new version. This is a typical "Read version +0, write version +1 scenario. I've been told by our MainFrame support vendor that SMS will not select prior versions of a GDG for backup/migrate if the BASE is in use. This has created a real problem because of the dataset size (~15K cyl per version). Before we re-design the application or degrade performance by moving the dataset to tape I want to know if there is an alternate solution within SMS. Anyone run into this before? If so, how did you resolve it?
Back to top
View user's profile Send private message

Global Moderator

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

PostPosted: Thu Aug 28, 2014 1:37 pm
Reply with quote

Only once, same sort of thing with generations not being migrated.

Used a REXX job to follow the one creating the GDS to determine the generations that needed migration and then issue HMIG ML2 commands.

If backups are not being taken then the job can issue HBACKS WAIT, or use ARCBAKDS to take backups and then migrate.
Back to top
View user's profile Send private message
Pete Wilson

Active Member

Joined: 31 Dec 2009
Posts: 500
Location: London

PostPosted: Sat Aug 30, 2014 2:12 pm
Reply with quote

I don't think it makes any difference if the GDS's are being AutoMigrated or Command Migrated, the same issue applies.

There is a PATCH for DFHSM that will allow Migration of GDS's where the base is being held but it does have some potential side issues so should be properly understood. I'm not sure if applies to Backup as well, but why backup GDS's anyway. Backing up a backup?

Read about the PATCH here:
Issue the following patch command if you want to enable or
disable this alternate serialization method for migration
of GDS data sets:

PATCH .MCVT.+595 BIT(.....x..)
x = 0 old method of enqueueing is desired
x = 1 new method of enqueueing is desired (default)

I've had the same issue with DFDSS COPY and RESTORE where you're copying or restoring multiple generations of the same base from different jobs. Only way I found around that was to specify a reasonably long WAIT(x,n) value so it retries the restore.
Back to top
View user's profile Send private message
View previous topic :: :: View next topic  
Post new topic   Reply to topic View Bookmarks
All times are GMT + 6 Hours
Forum Index -> SYNCSORT


Similar Topics
Topic Forum Replies
No new posts how to list the number of backup data... JCL & VSAM 3
No new posts Issue with CR+ catalog backup job. JCL & VSAM 18
No new posts Merge GDG versions JCL & VSAM 5
No new posts Backup issues after upgrade to zOS 2.2 All Other Mainframe Topics 0
No new posts Single step to take backup of multipl... JCL & VSAM 1
Search our Forums:

Back to Top