This is the first time I am mailing here so here goes....
I have a weekly job that has to backup several large GDG versions on Friday. Every hour a new version of the GDG file is to be created and this job initiates and causes a contention with the backup job. This is because large number of GDG versions get migrated over the week.
Is there any way to prevent the migration of these GDG files either by:
1) Coding some parameter in the JCL while creating a new creating a new version and this will override any storage class setting that are in place.
2) Will I have to find out and use a suitable storage class parameter in the JCL (which would be shop dependant). In this case what are the exact parameters I should look out for and what are the usual values (if any).
Joined: 01 Mar 2006 Posts: 290 Location: Basel, Switzerland
if this is a real problem at your site,
contact your storage manager, if
he can define any special file names
or some special storage management class,
which prevents this gdg versions from being
migrated so fast...
if there is no definition in sms, will be difficult...
I am inclined to agree with what you say, will take it up with the DFSMS team.
Meanwhile, I have been looking around and found coding MGMTCLAS=MCNOMIG might be able to do the trick while creating the newer versions of the GDG.
What are your thought on this? Is it a sure shot way or again depends....