Multi-volume catalog/directory datasets

teldb2kals

Multi-volume catalog/directory datasets
Hi,

Probably an obvious one; I just need confirmation.

Would there be any issue with allowing catalog/directory tablespace
datasets to extend into multiple volumes when the current volume becomes
full ? I understand about the performance implications of having them as
multi-volume datasets, but, I suppose we could allow them to extend at the
time of need and then reorg them later.

Our current datasets are defined as single-volume. If we do allow them to
extend, would we need to redefine the datasets specifying more volumes, or
could we just modify the SMS rules to extend the dataset to other volumes
in the DASD pool ?

Thanks.

Regards,
Kals.

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". If you will be out of the office, send the SET DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

michael bell

Re: Multi-volume catalog/directory datasets
(in response to teldb2kals)
If your data is defined as VCAT
1. alter addvols (*) will let them go to a second volume

If your data is defined STOGROUP, DB2 will do the alter addvol automatically
when the extend fails. You can't see a candidate volume from LISTCAT or SMS
but it will occur.

Above depends on MVS limits of 117 (or something close without checking the
manual) extents on a single volume and total 255 total extents accross all
volumes.

And after that comes the rules for multi-dataset simple or segmented tables.


Mike Bell
HLS Technologies

-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email]On
Behalf Of Teldb2kals
Sent: Monday, December 15, 2003 2:24 PM
To: [login to unmask email]
Subject: Multi-volume catalog/directory datasets


Hi,

Probably an obvious one; I just need confirmation.

Would there be any issue with allowing catalog/directory tablespace
datasets to extend into multiple volumes when the current volume becomes
full ? I understand about the performance implications of having them as
multi-volume datasets, but, I suppose we could allow them to extend at the
time of need and then reorg them later.

Our current datasets are defined as single-volume. If we do allow them to
extend, would we need to redefine the datasets specifying more volumes, or
could we just modify the SMS rules to extend the dataset to other volumes
in the DASD pool ?

Thanks.

Regards,
Kals.

----------------------------------------------------------------------------
-----
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select
"Join or Leave the list". If you will be out of the office, send the SET
DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins
can be reached at [login to unmask email] Find out the latest on
IDUG conferences at http://conferences.idug.org/index.cfm
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.530 / Virus Database: 325 - Release Date: 10/22/2003

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.530 / Virus Database: 325 - Release Date: 10/22/2003

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". If you will be out of the office, send the SET DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm

michael bell

Re: Multi-volume catalog/directory datasets
(in response to michael bell)
I forgot to mention that all catalog/directory tablespaces and indexspaces
are VCAT defined. It works the same as user VCAT data.
If I remember correctly, you have to run the ALTER ADDVOLS while DB2 is down
or that tablespace is stopped. If you stop SYSDBASE, almost everything stops
anyways.

Mike Bell
HLS Technologies

-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email]On
Behalf Of Teldb2kals
Sent: Monday, December 15, 2003 2:24 PM
To: [login to unmask email]
Subject: Multi-volume catalog/directory datasets


Hi,

Probably an obvious one; I just need confirmation.

Would there be any issue with allowing catalog/directory tablespace
datasets to extend into multiple volumes when the current volume becomes
full ? I understand about the performance implications of having them as
multi-volume datasets, but, I suppose we could allow them to extend at the
time of need and then reorg them later.

Our current datasets are defined as single-volume. If we do allow them to
extend, would we need to redefine the datasets specifying more volumes, or
could we just modify the SMS rules to extend the dataset to other volumes
in the DASD pool ?

Thanks.

Regards,
Kals.

----------------------------------------------------------------------------
-----
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home
page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select
"Join or Leave the list". If you will be out of the office, send the SET
DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins
can be reached at [login to unmask email] Find out the latest on
IDUG conferences at http://conferences.idug.org/index.cfm
---
Incoming mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.530 / Virus Database: 325 - Release Date: 10/22/2003

---
Outgoing mail is certified Virus Free.
Checked by AVG anti-virus system (http://www.grisoft.com).
Version: 6.0.530 / Virus Database: 325 - Release Date: 10/22/2003

---------------------------------------------------------------------------------
Welcome to the IDUG DB2-L list. To unsubscribe, go to the archives and home page at http://www.idugdb2-l.org/archives/db2-l.html. From that page select "Join or Leave the list". If you will be out of the office, send the SET DB2-L NO MAIL command to [login to unmask email] The IDUG List Admins can be reached at [login to unmask email] Find out the latest on IDUG conferences at http://conferences.idug.org/index.cfm