VCAT name change for DB2 table space VSAM Linear Datasets

DBA Team

unread,

Sep 24, 1998, 3:00:00 AM9/24/98

to

Dear all,

When table space is created using DB2 Storage Group with VCAT name 'vvvv', DB2 will dynamically create the corresponding VSAM Linear datasets with the following naming convention:

vvvv.DSNDBx.dbname.tsname.I00001.A00n etc..

In our shop, vvvv corresponds to the team name that is using the table space. Sometimes, the name of the team will change due to organization change or whatever reasons, so there is a need to convert these dataset name to the new team name, say 'yyyy'. Apart from this high level qualifier (HLQ) change, there is nothing to be altered including the contents in the table space.

We understood that the formal way is to unload all the tables concerned, drop the table space and recreating them after the altering the storage group to use the new VCAT name. The last step of course is to reload them. But with hundreds of these table spaces need to be changed, this becomes extremely tedious and error prone.

We would like to share your experience if there is any simplier way to accomplish the task, given that only the dataset name need to be changed and of course the VCAT name of the storage group. Any idea is mostly welcome.

Thank you very much.

Please reply to sed...@hk.super.net
Regards,
Daniel.

Leblanc, Francis C - CNF

unread,

Sep 24, 1998, 3:00:00 AM9/24/98

to

If you are using stogroups, there is an easy way to do this.
First, Stop the affected tablespaces, indexes, or database, etc.
Second, Create a new storage group with the new VCAT name.
Third, Alter each tablespace and index to use the new STOGROUP.
Fourth, Alter the names of the underlying VSAM datasets to the new
high-level qualifier. Don't forget that you need to alter both the
CLUSTER and DATA components.
Fifth, Start the affected tablespaces and indexes

I've used this successfully when converting from user-defined datasets
to STOGROUPs, and it works very quickly. The slowest part of the
process is the actual IDCAMS alters.
Good luck to you.
Regards,

Fritz

Leigh, David

unread,

Sep 24, 1998, 3:00:00 AM9/24/98

to

Would re-orging the tables after you do the Stogroup alter do it?

David Leigh
UNIPAC Service Corporation
3015 South Parker Road
Suite 400
Aurora, CO 80014
(303) 696-5645
(303) 696-5669 fax
dle...@unipac.com

Fernando Estevez

unread,

Sep 24, 1998, 3:00:00 AM9/24/98

to

Daniel, perform the following steps:

0- Perform imagecopy.
1- Create the new stogroup with Vcat 'yyyy'.
2- Stop DB.
3- Alter tablespace using stogroup new.
4- Run Pgm Idcams with option 'Alter vvvv.dsndbc/d..... newname
(yyyy.dsndbc/d.....)'
5- Start DB.

That's all...

Henrik Bang Sorensen

unread,

Sep 25, 1998, 3:00:00 AM9/25/98

to

PUBLIC:

Truman G. Brown

unread,

Sep 25, 1998, 3:00:00 AM9/25/98

to

Oh, well... why not leave DSN's alone and use SYNONYM or ALIAS
for "team" names.

From: owner...@AMERICAN.EDU AT INTERNET on 09/24/98 07:07 PM

To: BRIAN KHONG/EMPL/VA/Bell-Atl, DAN BROGDON/VEND/VA/Bell-Atl,
DEBAPRATIM MUKHERJEE/EMPL/VA/Bell-Atl, TRUMAN G.
BROWN/EMPL/MD/Bell-Atl, DB...@AMERICAN.EDU AT INTERNET@CCDOMAIN
cc:

Subject: VCAT name change for DB2 table space VSAM Linear Datasets

Reese, Wayne, SITS

unread,

Sep 25, 1998, 3:00:00 AM9/25/98

to

I may be confusing this with something else, but I believe I've tried that
and had the utility fail because DB2 generated a VSAM delete and define
cluster, and used the new name for both. So it's necessary to rename the
VSAM datasets outside of DB2's influence.

Hope this helps,
wayne

Wayne Reese
Paragon Computer Professionals
at AT&T - 30 Knightsbridge Road
Piscataway, NJ
(732) 457-4727 cube 52d44
email: wre...@att.com

> -----Original Message-----
> From: Leigh, David [SMTP:dle...@HQMAIL.UNIPAC.COM]
> Sent: Thursday, September 24, 1998 3:55 PM
> To: DB...@AMERICAN.EDU
> Subject: FW: VCAT name change for DB2 table space VSAM Linear
> Datasets
>

> Would re-orging the tables after you do the Stogroup alter do it?
>
> David Leigh
> UNIPAC Service Corporation
> 3015 South Parker Road
> Suite 400
> Aurora, CO 80014
> (303) 696-5645
> (303) 696-5669 fax
> dle...@unipac.com
>
>
> -----Original Message-----
> From: DBA Team [ <mailto:sed...@HK.SUPER.NET>]
> Sent: Thursday, September 24, 1998 4:33 AM
> To: DB...@AMERICAN.EDU

Mike_...@tekhelp.net

unread,

Sep 25, 1998, 3:00:00 AM9/25/98

to

Hi,
You cannot alter a stogroup to use a new VCAT. If you alter the
tablespace to use a different stogroup with a different VCAT and then
attempt to access the tablespace (with reorg) DB2 will not be able
to locate the tablespace to unload. The correct method is to rename
the tablespace and then alter to a stogroup with the new alias. Reorg
is not necessary.

Regards,

Michael Levine
Premier Data Services, Inc.

><!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
><HTML>
><HEAD>
><META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=iso-8859-1">
><META NAME="Generator" CONTENT="MS Exchange Server version 5.0.1461.43">
><TITLE>RE: VCAT name change for DB2 table space VSAM Linear Datasets</TITLE>
></HEAD>
><BODY>
>
>Would re-orging the tables after you do the Stogroup alter
do it?
>
>
>David Leigh
> UNIPAC Service Corporation
> 3015 South Parker Road
> Suite 400
> Aurora, CO 80014
> (303) 696-5645
> (303) 696-5669 fax
> dle...@unipac.com
>
> 
>
>-----Original Message-----
> From: DBA Team [<A HREF="mailto:sed...@HK.SUPER.NET"
TARGET="_blank">mailto:sed...@HK.SUPER.NET</A>]
> Sent: Thursday, September 24, 1998 4:33 AM
> To: DB...@AMERICAN.EDU
> Subject: VCAT name change for DB2 table space VSAM Linear
Datasets
>
> 
>
>Dear all,
>
>
>When table space is created using DB2 Storage Group with

VCAT name 'vvvv', DB2 will dynamically create the corresponding VSAM Linear

datasets with the following naming convention:
>
>vvvv.DSNDBx.dbname.tsname.I00001.A00n etc..
>
>
>In our shop, vvvv corresponds to the team name that is

using the table space. Sometimes, the name of the team will change due to
organization change or whatever reasons, so there is a need to convert these

dataset name to the new  team name, say 'yyyy'. Apart from this high

level qualifier (HLQ) change, there is nothing to be altered including the

contents in the table space. 
>
>We understood that the formal way is to unload all the

tables concerned, drop the table space and recreating them after the
altering the storage group to use the new VCAT name. The last step of course
is to reload them. But with hundreds of these table spaces need to be

changed, this becomes extremely tedious and error prone. 
>
>We would like to share your experience if there is any

simplier way to accomplish the task, given that only the dataset name need
to be changed and of course the VCAT name of the storage group. Any idea is

mostly welcome.
>
>Thank you very much.
>
>
>Please reply to sed...@hk.super.net
> Regards,
> Daniel.
>
>
></BODY>
></HTML>

Kathryn Zeidenstein (8-543-3697)

unread,

Sep 28, 1998, 3:00:00 AM9/28/98

to

Daniel,
Please see page 2-145 of your Version 5 Administration Guide. I believe
that is the procedure you are looking for, correct?
(It's in V4, too, on page 2-146.)

Kathy Zeidenstein
DB2 Information Development