z/OS v7.1 - Increase size of catalog index

Mark Vickers

z/OS v7.1 - Increase size of catalog index
Good day folks,
I have an index in DSNDB06.DSNHEX01 (SYSCOLUMNS_HIST) that ran out of
extents.
I searched all the doc. and web that I could and came up empty.

Could someone please point me in the right direction or help with the
process of increasing space for this index.

thanks,
Mark.

---------------------------------------------------------------------------------
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". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. 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

David Slocum

Re: z/OS v7.1 - Increase size of catalog index
(in response to Mark Vickers)
Hi Mark,

Where were you the past couple of days when there was a heated discussion
on how to resize an index on SYSCOPY? In answer to your question, look in
the DB2 Administration Guide, Volume 1, chapter 22 (Recovery Scenarios),
the section on "Integrated catalog facility catalog VSAM volume data set
failures", subsection on "Out of disk space or extent limit reached" (page
440 in my version of the manual). If you read through this section, it
will direct you to "Procedure 2. Enlarge a fully extended data set
(user-managed)" on page 442. Follow the directions as they are listed, and
you're home free.

Dave Slocum
Consumers Energy


---------------------------------------------------------------------------------
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". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. 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

Basivi Inaganti

Re: z/OS v7.1 - Increase size of catalog index
(in response to David Slocum)
Quick way to get out of extents is, move the dataset to different volume.
You got the answer form Dave Slocum on how to increase the space.

The following example shows how to move a data set from one DASD volume to
another using JCL and a DFSMSdss command. The source data set is deleted
and the target data set is cataloged to reflect its new location.




________________________________________________________________________
| |
| //MYJOB JOB accounting information,REGION=nnnnK |
| //STEP1 EXEC PGM=ADRDSSU |
| //SYSPRINT DD SYSOUT=A |
| //DASD1 DD UNIT=3380,VOL=(PRIVATE,SER=111111),DISP=OLD |
| //DASD2 DD UNIT=3390,VOL=(PRIVATE,SER=222222),DISP=OLD |
| //SYSIN DD * |
| COPY DATASET(INCLUDE(MYDATSET)) - |
| LOGINDDNAME(DASD1) OUTDDNAME(DASD2) DELETE CATALOG |
| /* |
| |

|________________________________________________________________________|


Thanks,
Basivi.







Mark E Vickers <[login to unmask email]>
Sent by: DB2 Data Base Discussion List <[login to unmask email]>
12/15/2005 03:21 PM
Please respond to DB2 Database Discussion list at IDUG

To: [login to unmask email]
cc:
Subject: [DB2-L] z/OS v7.1 - Increase size of catalog index


Good day folks,
I have an index in DSNDB06.DSNHEX01 (SYSCOLUMNS_HIST) that ran out of
extents.
I searched all the doc. and web that I could and came up empty.

Could someone please point me in the right direction or help with the
process of increasing space for this index.

thanks,
Mark.

---------------------------------------------------------------------------------
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". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. 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


---------------------------------------------------------------------------------
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". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. 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

Mark Vickers

Re: z/OS v7.1 - Increase size of catalog index
(in response to Basivi Inaganti)
Sorry I missed the discussion, just been one of those weeks where this is
about the extent of my visit to DB2-L.
thanks for your help.




Basivi Inaganti <[login to unmask email]>
Sent by: DB2 Data Base Discussion List <[login to unmask email]>
12/15/2005 03:03 PM
Please respond to
DB2 Database Discussion list at IDUG <[login to unmask email]>


To
[login to unmask email]
cc

Subject
Re: z/OS v7.1 - Increase size of catalog index







Quick way to get out of extents is, move the dataset to different volume.
You got the answer form Dave Slocum on how to increase the space.

The following example shows how to move a data set from one DASD volume to
another using JCL and a DFSMSdss command. The source data set is deleted
and the target data set is cataloged to reflect its new location.




________________________________________________________________________
| |
| //MYJOB JOB accounting information,REGION=nnnnK |
| //STEP1 EXEC PGM=ADRDSSU |
| //SYSPRINT DD SYSOUT=A |
| //DASD1 DD UNIT=3380,VOL=(PRIVATE,SER=111111),DISP=OLD |
| //DASD2 DD UNIT=3390,VOL=(PRIVATE,SER=222222),DISP=OLD |
| //SYSIN DD * |
| COPY DATASET(INCLUDE(MYDATSET)) - |
| LOGINDDNAME(DASD1) OUTDDNAME(DASD2) DELETE CATALOG |
| /* |
| |

|________________________________________________________________________|



Thanks,
Basivi.






Mark E Vickers <[login to unmask email]>
Sent by: DB2 Data Base Discussion List <[login to unmask email]>
12/15/2005 03:21 PM
Please respond to DB2 Database Discussion list at IDUG

To: [login to unmask email]
cc:
Subject: [DB2-L] z/OS v7.1 - Increase size of catalog index



Good day folks,
I have an index in DSNDB06.DSNHEX01 (SYSCOLUMNS_HIST) that ran out of
extents.
I searched all the doc. and web that I could and came up empty.

Could someone please point me in the right direction or help with the
process of increasing space for this index.

thanks,
Mark.

---------------------------------------------------------------------------------
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". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. 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

---------------------------------------------------------------------------------
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". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. 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

---------------------------------------------------------------------------------
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". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. 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

Avram Friedman

Re: z/OS v7.1 - Increase size of catalog index
(in response to Mark Vickers)
Mark,
There are many ways to handle out of space conditions in DB2 objects all with various advantages and disadvantages.

If one were to ask about the comparative justification of various methods that the question originator asks it would be appropriate to go into details as to what method is best and perhaps add a few additional ones.

In your case, and in the case of the question earlier this week ... A blind how too ...

Given the critical importance of DB2 objects and the need for Recover-ability, Maintainability, Supportability and Reference-ability there is only one answer.

Follow the instructions in the base set of IBM DB2 documentation for the DB2 version that you are running. If there is the slightest question of how to implement or follow the instructions, contact IBM support prior to making any attempt.

Correspondingly the instructions suggested in answer to your question by David R Slocum are the only correct ones.

If some one suggests a solution proposed by Joe Shmoe (or any other person) in a paper not sent to every DB2 licensee for your platform as part of the distribution materials ... RUN AWAY AS FAST AS POSSIBLE.

Once again the only acceptable answer to a general, non comparitive DB2 Backup, Recovery, object maintenance question is a pointer to the IBM DB2 base documentation coupled with advice to follow the instructions carefully. Contact the vendor in case of any doubt. DB2 is just too important to risk the environment to a blind lead.

Mark E Vickers <[login to unmask email]> wrote:
Good day folks,
I have an index in DSNDB06.DSNHEX01 (SYSCOLUMNS_HIST) that ran out of
extents.
I searched all the doc. and web that I could and came up empty.

Could someone please point me in the right direction or help with the
process of increasing space for this index.

thanks,
Mark.

---------------------------------------------------------------------------------
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". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. 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




Avram Friedman
(877)311-0480 Voice Mail
[login to unmask email]
Http://www.IBMsysProg.com




---------------------------------------------------------------------------------
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". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. 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 Ebert

Re: z/OS v7.1 - Increase size of catalog index
(in response to Avram Friedman)
Hi Mark,

use a JCL like this to consolidate extents in DB2 datasets (I assume you
have DFHMS). If someone tells you to slavishly follow the IBM docu,
remember that much of the info - especially the base info - hasn't been
updated since the very early days and is now outdated and unnecessarily
convoluted and complex, not to mention lengthy.
There is nothing magic about DB2 VSAM datasets. There is nothing magic
about Catalog and Directory TSs and indexes. Check out my V7 Cat/Dir
REORG, COPY, RECOVER etc. JCL from the IDUG Insider Code Place. Try it out
on your test system. Do your own thinking. If you're afraid of touching
your Catalog/Directory objects, you're not in a good position if something
actually does happen to them.

Dr. Michael Ebert
DB2 & Oracle Database Administrator
aMaDEUS Data Processing
Erding / Munich, Germany

//*------- Stop the Tablespace --------------------------
//STOP0001 EXEC PGM=IKJEFT1B,PARM='DSN S(DB2P)'
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
-STO DB(DSNDB06) SP(DSNHEX01)
//*------- Move the file --------------------------------
//MOVE0001 EXEC PGM=ADRDSSU
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
COPY DS(INC(DB2P.DSNDBC.DSNDB06.DSNHEX01.**)) -
SPHERE DEL RECAT(*) ALLD(*) ALLX
//*------- Re-start the Tablespace ----------------------
//STRT0001 EXEC PGM=IKJEFT1B,PARM='DSN S(DB2P)'
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
-STA DB(DSNDB06) SP(DSNHEX01)








Avram Friedman <[login to unmask email]>
Please respond to DB2 Database Discussion list at IDUG
<[login to unmask email]>
Sent by: DB2 Data Base Discussion List <[login to unmask email]>
16-12-05 02:28

To
[login to unmask email]
cc



Subject
Re: [DB2-L] z/OS v7.1 - Increase size of catalog index






Mark,
There are many ways to handle out of space conditions in DB2 objects all
with various advantages and disadvantages.

If one were to ask about the comparative justification of various methods
that the question originator asks it would be appropriate to go into
details as to what method is best and perhaps add a few additional ones.

In your case, and in the case of the question earlier this week ... A
blind how too ...

Given the critical importance of DB2 objects and the need for
Recover-ability, Maintainability, Supportability and Reference-ability
there is only one answer.

Follow the instructions in the base set of IBM DB2 documentation for the
DB2 version that you are running. If there is the slightest question of
how to implement or follow the instructions, contact IBM support prior to
making any attempt.

Correspondingly the instructions suggested in answer to your question by
David R Slocum are the only correct ones.

If some one suggests a solution proposed by Joe Shmoe (or any other
person) in a paper not sent to every DB2 licensee for your platform as
part of the distribution materials ... RUN AWAY AS FAST AS POSSIBLE.

Once again the only acceptable answer to a general, non comparitive DB2
Backup, Recovery, object maintenance question is a pointer to the IBM DB2
base documentation coupled with advice to follow the instructions
carefully. Contact the vendor in case of any doubt. DB2 is just too
important to risk the environment to a blind lead.

Mark E Vickers <[login to unmask email]> wrote:
Good day folks,
I have an index in DSNDB06.DSNHEX01 (SYSCOLUMNS_HIST) that ran out of
extents.
I searched all the doc. and web that I could and came up empty.

Could someone please point me in the right direction or help with the
process of increasing space for this index.

thanks,
Mark.

---------------------------------------------------------------------------------
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". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. 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

Mark Vickers

Re: z/OS v7.1 - Increase size of catalog index
(in response to Michael Ebert)
Thanks Michael (and Avram),
I had already downloaded your JCL, thanks.
At my previous job, I had successfully reorged the catalog when we
upgraded from v6 to 7, but never got to do this.
I guess my fear is deleting/redefining the underlying datasets and losing
the link from the systablespace - if that makes any sense.
thanks,
Mark.




Michael Ebert <[login to unmask email]>
Sent by: DB2 Data Base Discussion List <[login to unmask email]>
12/16/2005 02:21 AM
Please respond to
DB2 Database Discussion list at IDUG <[login to unmask email]>


To
[login to unmask email]
cc

Subject
Re: z/OS v7.1 - Increase size of catalog index







Hi Mark,

use a JCL like this to consolidate extents in DB2 datasets (I assume you
have DFHMS). If someone tells you to slavishly follow the IBM docu,
remember that much of the info - especially the base info - hasn't been
updated since the very early days and is now outdated and unnecessarily
convoluted and complex, not to mention lengthy.
There is nothing magic about DB2 VSAM datasets. There is nothing magic
about Catalog and Directory TSs and indexes. Check out my V7 Cat/Dir
REORG, COPY, RECOVER etc. JCL from the IDUG Insider Code Place. Try it out
on your test system. Do your own thinking. If you're afraid of touching
your Catalog/Directory objects, you're not in a good position if something
actually does happen to them.

Dr. Michael Ebert
DB2 & Oracle Database Administrator
aMaDEUS Data Processing
Erding / Munich, Germany

//*------- Stop the Tablespace --------------------------
//STOP0001 EXEC PGM=IKJEFT1B,PARM='DSN S(DB2P)'
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
-STO DB(DSNDB06) SP(DSNHEX01)
//*------- Move the file --------------------------------
//MOVE0001 EXEC PGM=ADRDSSU
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
COPY DS(INC(DB2P.DSNDBC.DSNDB06.DSNHEX01.**)) -
SPHERE DEL RECAT(*) ALLD(*) ALLX
//*------- Re-start the Tablespace ----------------------
//STRT0001 EXEC PGM=IKJEFT1B,PARM='DSN S(DB2P)'
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
-STA DB(DSNDB06) SP(DSNHEX01)





Avram Friedman <[login to unmask email]>

Please respond to DB2 Database Discussion list at IDUG
<[login to unmask email]>
Sent by: DB2 Data Base Discussion List <[login to unmask email]>
16-12-05 02:28


To
[login to unmask email]
cc



Subject
Re: [DB2-L] z/OS v7.1 - Increase size of catalog index








Mark,
There are many ways to handle out of space conditions in DB2 objects all
with various advantages and disadvantages.

If one were to ask about the comparative justification of various methods
that the question originator asks it would be appropriate to go into
details as to what method is best and perhaps add a few additional ones.

In your case, and in the case of the question earlier this week ... A
blind how too ...

Given the critical importance of DB2 objects and the need for
Recover-ability, Maintainability, Supportability and Reference-ability
there is only one answer.

Follow the instructions in the base set of IBM DB2 documentation for the
DB2 version that you are running. If there is the slightest question of
how to implement or follow the instructions, contact IBM support prior to
making any attempt.

Correspondingly the instructions suggested in answer to your question by
David R Slocum are the only correct ones.

If some one suggests a solution proposed by Joe Shmoe (or any other
person) in a paper not sent to every DB2 licensee for your platform as
part of the distribution materials ... RUN AWAY AS FAST AS POSSIBLE.

Once again the only acceptable answer to a general, non comparitive DB2
Backup, Recovery, object maintenance question is a pointer to the IBM DB2
base documentation coupled with advice to follow the instructions
carefully. Contact the vendor in case of any doubt. DB2 is just too
important to risk the environment to a blind lead.

Mark E Vickers <[login to unmask email]> wrote:
Good day folks,
I have an index in DSNDB06.DSNHEX01 (SYSCOLUMNS_HIST) that ran out of
extents.
I searched all the doc. and web that I could and came up empty.

Could someone please point me in the right direction or help with the
process of increasing space for this index.

thanks,
Mark.
---------------------------------------------------------------------------------
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". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. 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

---------------------------------------------------------------------------------
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". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. 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

Avram Friedman

Re: z/OS v7.1 - Increase size of catalog index
(in response to Mark Vickers)
For a number of years I have done volunteer hot line support for an organization that helps people with a particular type of physical / psychological disorder. I believe this organization has the best most effective solution for this particular by far.

When I was trained to do hot line support something that was drilled into me was "If some one calls saying he or she is ill from a related disorder and thinks they are in short term danger and may die" Tell them to hang up and call 911. This is true even knowing, for sure, that I have the best solution.

If some one tells me that they have a DB2 system that is sick and about to die, lets say for example that a catalog or directory object has become or is about to become unusable and they have no clue as to what too do. I tell them to follow IBM DB2s instructions carefully or call them. This is true even though I am a product author for some data base utilities, have done lots of tech support my self, am 110% sure there is a better solution than IBMs.

This is different from some one calling me as a tech person from ABC company and saying "We have purchased, installed, and tested your product and are now experiencing a related problem, walk us through the solution or hold our hand.

This is different from dealing with some one who calls and says "We are planning for future problems, how do I best prepare and position my self to handle this?"

We are now in a holiday season where people of many faiths deploy electrical and or candle lighting as part of there celebration. If some one were to ask me how to do this sort of lighting safely, I have some good ideas. On the other hand if some one says I have an unexpected fire I don't know how to control it! Do not discuss the advisability of having a spider web of frayed electrical cords plugged into a single jack ... Advise them to call the local fire department or call the fire department your self.

Happy and safe holidays

Michael Ebert <[login to unmask email]> wrote:

Hi Mark,

use a JCL like this to consolidate extents in DB2 datasets (I assume you have DFHMS). If someone tells you to slavishly follow the IBM docu, remember that much of the info - especially the base info - hasn't been updated since the very early days and is now outdated and unnecessarily convoluted and complex, not to mention lengthy.
There is nothing magic about DB2 VSAM datasets. There is nothing magic about Catalog and Directory TSs and indexes. Check out my V7 Cat/Dir REORG, COPY, RECOVER etc. JCL from the IDUG Insider Code Place. Try it out on your test system. Do your own thinking. If you're afraid of touching your Catalog/Directory objects, you're not in a good position if something actually does happen to them.

Dr. Michael Ebert
DB2 & Oracle Database Administrator
aMaDEUS Data Processing
Erding / Munich, Germany

//*------- Stop the Tablespace --------------------------
//STOP0001 EXEC PGM=IKJEFT1B,PARM='DSN S(DB2P)'
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
-STO DB(DSNDB06) SP(DSNHEX01)
//*------- Move the file --------------------------------
//MOVE0001 EXEC PGM=ADRDSSU
//SYSPRINT DD SYSOUT=*
//SYSIN DD *
COPY DS(INC(DB2P.DSNDBC.DSNDB06.DSNHEX01.**)) -
SPHERE DEL RECAT(*) ALLD(*) ALLX
//*------- Re-start the Tablespace ----------------------
//STRT0001 EXEC PGM=IKJEFT1B,PARM='DSN S(DB2P)'
//SYSTSPRT DD SYSOUT=*
//SYSTSIN DD *
-STA DB(DSNDB06) SP(DSNHEX01)





Avram Friedman <[login to unmask email]> Please respond to DB2 Database Discussion list at IDUG <[login to unmask email]>
Sent by: DB2 Data Base Discussion List <[login to unmask email]>
16-12-05 02:28


To
[login to unmask email] cc

Subject
Re: [DB2-L] z/OS v7.1 - Increase size of catalog index




Mark,
There are many ways to handle out of space conditions in DB2 objects all with various advantages and disadvantages.

If one were to ask about the comparative justification of various methods that the question originator asks it would be appropriate to go into details as to what method is best and perhaps add a few additional ones.

In your case, and in the case of the question earlier this week ... A blind how too ...

Given the critical importance of DB2 objects and the need for Recover-ability, Maintainability, Supportability and Reference-ability there is only one answer.

Follow the instructions in the base set of IBM DB2 documentation for the DB2 version that you are running. If there is the slightest question of how to implement or follow the instructions, contact IBM support prior to making any attempt.

Correspondingly the instructions suggested in answer to your question by David R Slocum are the only correct ones.

If some one suggests a solution proposed by Joe Shmoe (or any other person) in a paper not sent to every DB2 licensee for your platform as part of the distribution materials ... RUN AWAY AS FAST AS POSSIBLE.

Once again the only acceptable answer to a general, non comparitive DB2 Backup, Recovery, object maintenance question is a pointer to the IBM DB2 base documentation coupled with advice to follow the instructions carefully. Contact the vendor in case of any doubt. DB2 is just too important to risk the environment to a blind lead.

Mark E Vickers <[login to unmask email]> wrote:
Good day folks,
I have an index in DSNDB06.DSNHEX01 (SYSCOLUMNS_HIST) that ran out of
extents.
I searched all the doc. and web that I could and came up empty.

Could someone please point me in the right direction or help with the
process of increasing space for this index.

thanks,
Mark.
--------------------------------------------------------------------------------- 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". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. 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



Avram Friedman
(877)311-0480 Voice Mail
[login to unmask email]
Http://www.IBMsysProg.com




---------------------------------------------------------------------------------
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". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. 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

Sam Kitty

Re: z/OS v7.1 - Increase size of catalog index
(in response to Avram Friedman)
You will have a hard time reorganizing your catalog and directory
in a busy environment. However, if you can isolate some "quiet"
time, it will work fine, and yield great benefits.


Ivan B. Krnic

DBA
IS@D
Z/OS Platform



-----Original Message-----
From: DB2 Data Base Discussion List [mailto:[login to unmask email]On
Behalf Of Mark E Vickers
Sent: Friday, December 16, 2005 6:35 AM
To: [login to unmask email]
Subject: Re: [DB2-L] z/OS v7.1 - Increase size of catalog index


Thanks Michael (and Avram),
I had already downloaded your JCL, thanks.
At my previous job, I had successfully reorged the catalog when we
upgraded from v6 to 7, but never got to do this.
I guess my fear is deleting/redefining the underlying datasets and
losing
the link from the systablespace - if that makes any sense.
thanks,
Mark.




Michael Ebert <[login to unmask email]>
Sent by: DB2 Data Base Discussion List <[login to unmask email]>
12/16/2005 02:21 AM
Please respond to
DB2 Database Discussion list at IDUG <[login to unmask email]>


To
[login to unmask email]
cc

Subject
Re: z/OS v7.1 - Increase size of catalog index







Hi Mark,

use a JCL like this to consolidate extents in DB2 datasets (I assume you

have DFHMS). If someone tells you to slavishly follow the IBM docu,
remember that much of the info - especially the base info - hasn't been
updated since the very early days and is now outdated and unnecessarily
convoluted and complex, not to mention lengthy.
There is nothing magic about DB2 VSAM datasets. There is nothing magic
about Catalog and Directory TSs and indexes. Check out my V7 Cat/Dir
REORG, COPY, RECOVER etc. JCL from the IDUG Insider Code Place. Try it
out
on your test system. Do your own thinking. If you're afraid of touching
your Catalog/Directory objects, you're not in a good position if
something
actually does happen to them.

Dr. Michael Ebert
DB2 & Oracle Database Administrator
aMaDEUS Data Processing
Erding / Munich, Germany

//*------- Stop the Tablespace --------------------------
//STOP0001 EXEC PGM=IKJEFT1B,PARM='DSN S(DB2P)'
//SYSTSPRT DD SYSOUT=*

//SYSTSIN DD *
-STO DB(DSNDB06) SP(DSNHEX01)
//*------- Move the file --------------------------------
//MOVE0001 EXEC PGM=ADRDSSU
//SYSPRINT DD SYSOUT=*

//SYSIN DD *
COPY DS(INC(DB2P.DSNDBC.DSNDB06.DSNHEX01.**)) -
SPHERE DEL RECAT(*) ALLD(*) ALLX
//*------- Re-start the Tablespace ----------------------
//STRT0001 EXEC PGM=IKJEFT1B,PARM='DSN S(DB2P)'
//SYSTSPRT DD SYSOUT=*

//SYSTSIN DD *
-STA DB(DSNDB06) SP(DSNHEX01)





Avram Friedman <[login to unmask email]>

Please respond to DB2 Database Discussion list at IDUG
<[login to unmask email]>
Sent by: DB2 Data Base Discussion List <[login to unmask email]>
16-12-05 02:28


To
[login to unmask email]
cc



Subject
Re: [DB2-L] z/OS v7.1 - Increase size of catalog index








Mark,
There are many ways to handle out of space conditions in DB2 objects all

with various advantages and disadvantages.

If one were to ask about the comparative justification of various
methods
that the question originator asks it would be appropriate to go into
details as to what method is best and perhaps add a few additional ones.


In your case, and in the case of the question earlier this week ... A
blind how too ...

Given the critical importance of DB2 objects and the need for
Recover-ability, Maintainability, Supportability and Reference-ability
there is only one answer.

Follow the instructions in the base set of IBM DB2 documentation for
the
DB2 version that you are running. If there is the slightest question of

how to implement or follow the instructions, contact IBM support prior
to
making any attempt.

Correspondingly the instructions suggested in answer to your question by

David R Slocum are the only correct ones.

If some one suggests a solution proposed by Joe Shmoe (or any other
person) in a paper not sent to every DB2 licensee for your platform as
part of the distribution materials ... RUN AWAY AS FAST AS POSSIBLE.

Once again the only acceptable answer to a general, non comparitive DB2
Backup, Recovery, object maintenance question is a pointer to the IBM
DB2
base documentation coupled with advice to follow the instructions
carefully. Contact the vendor in case of any doubt. DB2 is just too
important to risk the environment to a blind lead.

Mark E Vickers <[login to unmask email]> wrote:
Good day folks,
I have an index in DSNDB06.DSNHEX01 (SYSCOLUMNS_HIST) that ran out of
extents.
I searched all the doc. and web that I could and came up empty.

Could someone please point me in the right direction or help with the
process of increasing space for this index.

thanks,
Mark.
------------------------------------------------------------------------
---------
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". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. 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

------------------------------------------------------------------------
---------
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". The IDUG DB2-L FAQ is at
http://www.idugdb2-l.org. 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

---------------------------------------------------------------------------------
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". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. 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

Ford Wong

Re: z/OS v7.1 - Increase size of catalog index
(in response to Sam Kitty)
Mark,

If you have the DASD, I never delete the underlying VSAM dataset. I just rename it and keep it around for a few days (just in case).

Ford

----- Original Message -----
From: Mark E Vickers <[login to unmask email]>
Date: Friday, December 16, 2005 5:34 am
Subject: Re: [DB2-L] z/OS v7.1 - Increase size of catalog index

> Thanks Michael (and Avram),
> I had already downloaded your JCL, thanks.
> At my previous job, I had successfully reorged the catalog when we
> upgraded from v6 to 7, but never got to do this.
> I guess my fear is deleting/redefining the underlying datasets and
> losing
> the link from the systablespace - if that makes any sense.
> thanks,
> Mark.
>
>
>
>
> Michael Ebert <[login to unmask email]>
> Sent by: DB2 Data Base Discussion List <[login to unmask email]>
> 12/16/2005 02:21 AM
> Please respond to
> DB2 Database Discussion list at IDUG <[login to unmask email]>
>
>
> To
> [login to unmask email]
> cc
>
> Subject
> Re: z/OS v7.1 - Increase size of catalog index
>
>
>
>
>
>
>
> Hi Mark,
>
> use a JCL like this to consolidate extents in DB2 datasets (I
> assume you
> have DFHMS). If someone tells you to slavishly follow the IBM
> docu,
> remember that much of the info - especially the base info - hasn't
> been
> updated since the very early days and is now outdated and
> unnecessarily
> convoluted and complex, not to mention lengthy.
> There is nothing magic about DB2 VSAM datasets. There is nothing
> magic
> about Catalog and Directory TSs and indexes. Check out my V7
> Cat/Dir
> REORG, COPY, RECOVER etc. JCL from the IDUG Insider Code Place.
> Try it out
> on your test system. Do your own thinking. If you're afraid of
> touching
> your Catalog/Directory objects, you're not in a good position if
> something
> actually does happen to them.
>
> Dr. Michael Ebert
> DB2 & Oracle Database Administrator
> aMaDEUS Data Processing
> Erding / Munich, Germany
>
> //*------- Stop the Tablespace --------------------------
> //STOP0001 EXEC PGM=IKJEFT1B,PARM='DSN S(DB2P)'
> //SYSTSPRT DD SYSOUT=*
>
> //SYSTSIN DD *
> -STO DB(DSNDB06) SP(DSNHEX01)
> //*------- Move the file --------------------------------
> //MOVE0001 EXEC PGM=ADRDSSU
> //SYSPRINT DD SYSOUT=*
>
> //SYSIN DD *
> COPY DS(INC(DB2P.DSNDBC.DSNDB06.DSNHEX01.**)) -
> SPHERE DEL RECAT(*) ALLD(*) ALLX
> //*------- Re-start the Tablespace ----------------------
> //STRT0001 EXEC PGM=IKJEFT1B,PARM='DSN S(DB2P)'
> //SYSTSPRT DD SYSOUT=*
>
> //SYSTSIN DD *
> -STA DB(DSNDB06) SP(DSNHEX01)
>
>
>
>
>
> Avram Friedman <[login to unmask email]>
>
> Please respond to DB2 Database Discussion list at IDUG
> <[login to unmask email]>
> Sent by: DB2 Data Base Discussion List <[login to unmask email]>
> 16-12-05 02:28
>
>
> To
> [login to unmask email]
> cc
>
>
>
> Subject
> Re: [DB2-L] z/OS v7.1 - Increase size of catalog index
>
>
>
>
>
>
>
>
> Mark,
> There are many ways to handle out of space conditions in DB2
> objects all
> with various advantages and disadvantages.
>
> If one were to ask about the comparative justification of various
> methods
> that the question originator asks it would be appropriate to go
> into
> details as to what method is best and perhaps add a few additional
> ones.
>
> In your case, and in the case of the question earlier this week
> ... A
> blind how too ...
>
> Given the critical importance of DB2 objects and the need for
> Recover-ability, Maintainability, Supportability and Reference-
> ability
> there is only one answer.
>
> Follow the instructions in the base set of IBM DB2 documentation
> for the
> DB2 version that you are running. If there is the slightest
> question of
> how to implement or follow the instructions, contact IBM support
> prior to
> making any attempt.
>
> Correspondingly the instructions suggested in answer to your
> question by
> David R Slocum are the only correct ones.
>
> If some one suggests a solution proposed by Joe Shmoe (or any
> other
> person) in a paper not sent to every DB2 licensee for your
> platform as
> part of the distribution materials ... RUN AWAY AS FAST AS
> POSSIBLE.
>
> Once again the only acceptable answer to a general, non
> comparitive DB2
> Backup, Recovery, object maintenance question is a pointer to the
> IBM DB2
> base documentation coupled with advice to follow the instructions
> carefully. Contact the vendor in case of any doubt. DB2 is just
> too
> important to risk the environment to a blind lead.
>
> Mark E Vickers <[login to unmask email]> wrote:
> Good day folks,
> I have an index in DSNDB06.DSNHEX01 (SYSCOLUMNS_HIST) that ran out
> of
> extents.
> I searched all the doc. and web that I could and came up empty.
>
> Could someone please point me in the right direction or help with
> the
> process of increasing space for this index.
>
> thanks,
> Mark.
> -------------------------------------------------------------------
> --------------
> 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". The IDUG DB2-L FAQ is at
> http://www.idugdb2-l.org. 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
>
> -------------------------------------------------------------------
> --------------
> 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". The IDUG DB2-L FAQ
> is at http://www.idugdb2-l.org. 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
>

---------------------------------------------------------------------------------
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". The IDUG DB2-L FAQ is at http://www.idugdb2-l.org. 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