Migrated Datasets marked as Non Migratable

Praveen Ellur · New User Joined: 24 Sep 2007 Posts: 5 Location: Uruguay

We have a database unload job, which unloads a particular database onto a new version of a GDG. The retention limit of this GDG is 10.

On two occasions, the Unload job was in "wait-exec" status for a long time, causing the batch cycle to be delayed.

This was because the DHFSM utility had exclusive hold on GDG base.
It was trying to recover the migrated dataset.

Got the datasets marked as Non Migratable from our Storage Management team.

Can you think of any other solution to overcome this problem

dick scherrer · Posted: Mon Sep 24, 2007 5:41 am

Hello,

How large is the volume of data to be unloaded/stored?

You might unload to a one-time-use dataset and after the unload is successfully complete, copy the unloaded data to the gdg.

An extra copy of the data, but would remove the risk of the delay.

Praveen Ellur · New User Joined: 24 Sep 2007 Posts: 5 Location: Uruguay

For now,
We have marked the datasets as Non-Migratable.

We haven't found any solution.

Will post if there are any improvements.

Thanks a ton for this idea.