Movining Dataset from one volume serial to another vol ser

navneet.dewangan · New User Joined: 09 Oct 2005 Posts: 22 Location: INDIA

Hi All,

I wanted to Move my Datasets from one volume serials to another using TSO OR ANY OTHER COMMAND but not through JCL.

Please tell me what will be the dependencies of this.

shreevamsi · Posted: Thu Jan 25, 2007 8:43 pm

hi navneet.dewangan,

As of my knowledge, Once a dataset is allocated, we can't change its attributes unless u copy and rename.
Can anybody got any idea?

~Vamsi

dick scherrer · Posted: Fri Jan 26, 2007 4:56 am

Hello,

If this a PS or PO dataset?

If it is, here is a way to "move" it in tso.

First backup your file.

Then, using 3.2, get the attributes of the existing file.

Next (still in 3.2) allocate a new file (with a different dataset name) on the volume where you want your dataset to reside.

Now copy the old data into the new file (3.3 i believe) and verify the "new" file is correct.

Delete the original file.

Rename the "new" file to the original dataset name.

The file is now "moved".

William Thompson · Posted: Fri Jan 26, 2007 5:21 am

Dick,

I was looking at this this morning and was thinking as you are (uncatalog, allocate, copy and delete), but when I looked at 3.3, the move option did not have any restrictions on same name...?? except the delete came after the move rather than the catalog came after ther move... Didn't have time to test...

Bill

dick scherrer · Posted: Fri Jan 26, 2007 5:37 am

Hi Bill,

Don't know how it will work these days, but long ago, it rasied a "duplicate" error if an attempt was made to allocate (catalog) a second file of the "same" name in 3.2. I've been offsite all week and wasn't able to actually run it.

I seem to recall a "move" option as well (but it may be for members) - again, if i had access to a system from here, i'd look at that as well. I believe "move" is on the same screen as "copy".

For my $.02, i'd have done this in JCL rather than online. TS must have a situation where it is more desirable to do it online. I do hope there are not very many files and that they are small in size.

Bitneuker · Posted: Fri Jan 26, 2007 5:47 pm

Hi Dick & Bill,

Tried the move option. Same dsnames different volume: dataset not catalogued. Different dsname and volume entered, at next attribute screen selected option-2 (specify). Dataset was moved (new name) at different volume than typed. So my conclusion: move to different name and then rename; no coy needed.

dick scherrer · Posted: Fri Jan 26, 2007 7:04 pm

Hi George,

Sounds like a plan. . .

Being able to do the test makes a BIG difference.

Thanx for the update.

mmwife · Super Moderator Joined: 30 May 2003 Posts: 1592

It seems that SMS is the fly in this ointment. In the "old" days you could uncat the existing d/s then alloc a d/s with the same name to a different vol using the vol ser line directly under the DSN line of the 3.2 panel. Then you could copy the file using the vol ser lines of those panels.

I think you can still do that, but you have to get SMS out of the ointment 1st, or if your site doesn't use SMS. Unfortunately I have no solution for that.

dick scherrer · Posted: Sun Jan 28, 2007 11:35 pm

Yup,

In the pre-SMS days, you could also (via not so good jcl) propagate the same dsn to every volume in the generic (i.e. SYSDA). I was called one night by a frustrated programmer who was called in to fix an abort, but when he tried to run a "setup" job needed before re-running the aborted job, he kept getting "duplicate name on direct access volume". This particular dataset had found a home on EVERY sysda volume on the system. I never did find out how long they had been getting the ever popular "not cataloged 2" for that dataset, but it must have been a while. . .