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
 
GDG versions not being selected for backup/migrate

 
Post new topic   Reply to topic    IBMMAINFRAMES.com Support Forums -> SYNCSORT
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    Post subject: GDG versions not being selected for backup/migrate
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

expat

Global Moderator


Joined: 14 Mar 2007
Posts: 8593
Location: Back in jolly old England

PostPosted: Thu Aug 28, 2014 1:37 pm    Post subject:
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 User


Joined: 31 Dec 2009
Posts: 445
Location: London

PostPosted: Sat Aug 30, 2014 2:12 pm    Post subject:
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:
http://www-01.ibm.com/support/docview.wss?uid=isg1OA24059
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    IBMMAINFRAMES.com Support Forums -> SYNCSORT All times are GMT + 6 Hours
Page 1 of 1

 

Search our Forum:

Similar Topics
Topic Author Forum Replies Posted
No new posts IMS Database backup info ashek15 IMS DB/DC 14 Wed Nov 16, 2016 5:29 am
No new posts Reading selected volumes of a multi-v... RickBig JCL & VSAM 6 Wed Jul 13, 2016 7:26 pm
No new posts Need help on FDRABR incremental backu... sanpedro All Other Mainframe Topics 6 Wed Apr 06, 2016 3:24 am
No new posts Backup directory in USS (OMVS) autobox IBM Tools 3 Tue Jan 12, 2016 8:51 am
No new posts Database backup on IMS DB HABBIE IMS DB/DC 1 Wed Aug 12, 2015 9:02 pm

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