SV: [DB2-L] [DB2 V9 z/OS] Extents and indexes and RTS (and piecesize)

Olle Brostrom

SV: [DB2-L] [DB2 V9 z/OS] Extents and indexes and RTS (and piecesize)
Lynne,
I have made the same observation, I think it's time to pmr :)

Från: IDUG DB2-L [mailto:[login to unmask email] För Lynne Flatley
Skickat: den 16 december 2010 17:52
Till: [login to unmask email]
Ämne: [DB2-L] [DB2 V9 z/OS] Extents and indexes and RTS (and piecesize)

I'm wondering if this has been discussed before. I searched the archives and didn't see it.

I did a 3.4 (Data Set List) this morning on indexes in this production database. I then sorted the listing by extents and found several whose space allocations needed tweaking. I thought I'd double check my results in RTS and noticed that only one of the index datasets for an index with multiple files (because of the piecesize value) was stored in
SYSIBM.SYSINDEXSPACESTATS. So we cannot use RTS to monitor extents for indexes if we use the piecesize parm (and additional datasets actually get created)?
________________________________

[ http://www.idug.org/images/banners/idug_2011.gif ] < http://www.idug.org >

The IDUG DB2-L Listserv is only part of your membership in IDUG. If you are not already an IDUG member, please register here. < http://www.idug.org/register >

_____________________________________________________________________
* IDUG North America * Anaheim, California * May 2-6 2011 * http://IDUG.ORG/NA *
* Your only source for independent, unbiased, and trusted DB2 information. *
** The most DB2 technical sessions of any conference
** Access IBM experts and developers
_____________________________________________________________________

If you need to change settings, http://www.idug.org/cgi-bin/wa?A0=DB2-L is the home of IDUG's Listserv

Max Scarpa

Re: SV: [DB2-L] [DB2 V9 z/OS] Extents and indexes and RTS (and piecesize)
(in response to Olle Brostrom)
Db2 Version ? 9 ? 8 ? 10 ???





From: Olle Brostrom <[login to unmask email]>
To: [login to unmask email]
Date: 17/12/2010 07.39
Subject: [DB2-L] SV: [DB2-L] [DB2 V9 z/OS] Extents and indexes and
RTS (and piecesize)
Sent by: IDUG DB2-L <[login to unmask email]>



Lynne,
I have made the same observation, I think it’s time to pmr J

Från: IDUG DB2-L [mailto:[login to unmask email] För Lynne Flatley
Skickat: den 16 december 2010 17:52
Till: [login to unmask email]
Ämne: [DB2-L] [DB2 V9 z/OS] Extents and indexes and RTS (and piecesize)

I'm wondering if this has been discussed before. I searched the archives
and didn't see it.

I did a 3.4 (Data Set List) this morning on indexes in this production
database. I then sorted the listing by extents and found several whose
space allocations needed tweaking. I thought I'd double check my results
in RTS and noticed that only one of the index datasets for an index with
multiple files (because of the piecesize value) was stored in
SYSIBM.SYSINDEXSPACESTATS. So we cannot use RTS to monitor extents for
indexes if we use the piecesize parm (and additional datasets actually get
created)?


The IDUG DB2-L Listserv is only part of your membership in IDUG. If you
are not already an IDUG member, please register here.



The IDUG DB2-L Listserv is only part of your membership in IDUG. If you
are not already an IDUG member, please register here.


_____________________________________________________________________
* IDUG North America * Anaheim, California * May 2-6 2011 * http://IDUG.ORG/NA *
* Your only source for independent, unbiased, and trusted DB2 information. *
** The most DB2 technical sessions of any conference
** Access IBM experts and developers
_____________________________________________________________________

If you need to change settings, http://www.idug.org/cgi-bin/wa?A0=DB2-L is the home of IDUG's Listserv

Roy Boxwell

Re: [DB2 V9 z/OS] Extents and indexes and RTS (and piecesize)
(in response to Max Scarpa)
Sorry to say it WAD...The RTS contains only the LAST extent count from the
dataset(s) and this is how it was designed to be - Use of piecesize with
indices then gives you a little "challenge" if you base your space calcs
purely on RTS data! Like CA we also have software that does this for you
of course...sadly it costs money - or you can ply me with beer - the
choice is yours! :)



Roy Boxwell
SOFTWARE ENGINEERING GMBH
-Product Development-
Robert-Stolz-Straße 5
40470 Düsseldorf/Germany
Tel. +49 (0)211 96149-675
Fax +49 (0)211 96149-32
Email: [login to unmask email]
http://www.seg.de

Software Engineering GmbH
Amtsgericht Düsseldorf, HRB 37894
Geschäftsführung: Gerhard Schubert



Lynne Flatley <[login to unmask email]>
Gesendet von: IDUG DB2-L <[login to unmask email]>
16.12.2010 17:51
Bitte antworten an
IDUG DB2-L <[login to unmask email]>


An
[login to unmask email]
Kopie

Thema
[DB2-L] [DB2 V9 z/OS] Extents and indexes and RTS (and piecesize)






I'm wondering if this has been discussed before. I searched the archives
and didn't see it.

I did a 3.4 (Data Set List) this morning on indexes in this production
database. I then sorted the listing by extents and found several whose
space allocations needed tweaking. I thought I'd double check my results
in RTS and noticed that only one of the index datasets for an index with
multiple files (because of the piecesize value) was stored in
SYSIBM.SYSINDEXSPACESTATS. So we cannot use RTS to monitor extents for
indexes if we use the piecesize parm (and additional datasets actually get
created)?



The IDUG DB2-L Listserv is only part of your membership in IDUG. If you
are not already an IDUG member, please register here.

_____________________________________________________________________
* IDUG North America * Anaheim, California * May 2-6 2011 * http://IDUG.ORG/NA *
* Your only source for independent, unbiased, and trusted DB2 information. *
** The most DB2 technical sessions of any conference
** Access IBM experts and developers
_____________________________________________________________________

If you need to change settings, http://www.idug.org/cgi-bin/wa?A0=DB2-L is the home of IDUG's Listserv

Max Scarpa

Re: [DB2 V9 z/OS] Extents and indexes and RTS (and piecesize)
(in response to Roy Boxwell)
> several whose space allocations needed tweaking. I thought I'd
> double check my results in RTS and noticed that only one of the
> index datasets for an index with multiple files (because of the
> piecesize value) was stored in

It'd be the last datasets the one with extents as in multi-piece index
spaces RTS value is the number of extents for the last data set. Time to
plan a REXX to update RTS columns ?

Max Scarpa




_____________________________________________________________________
* IDUG North America * Anaheim, California * May 2-6 2011 * http://IDUG.ORG/NA *
* Your only source for independent, unbiased, and trusted DB2 information. *
** The most DB2 technical sessions of any conference
** Access IBM experts and developers
_____________________________________________________________________

If you need to change settings, http://www.idug.org/cgi-bin/wa?A0=DB2-L is the home of IDUG's Listserv

Roy Boxwell

Re: [DB2 V9 z/OS] Extents and indexes and RTS (and piecesize)
(in response to Max Scarpa)
dangerous idea Max! Then at the next externalization of RTS data the
latest last extents will replace you REXX computed value! Perhaps it's
better to not use pieces!!! :)

Roy Boxwell
SOFTWARE ENGINEERING GMBH
-Product Development-
Robert-Stolz-Straße 5
40470 Düsseldorf/Germany
Tel. +49 (0)211 96149-675
Fax +49 (0)211 96149-32
Email: [login to unmask email]
http://www.seg.de

Software Engineering GmbH
Amtsgericht Düsseldorf, HRB 37894
Geschäftsführung: Gerhard Schubert



Max Scarpa <[login to unmask email]>
Gesendet von: IDUG DB2-L <[login to unmask email]>
17.12.2010 10:46
Bitte antworten an
IDUG DB2-L <[login to unmask email]>


An
[login to unmask email]
Kopie

Thema
Re: [DB2-L] [DB2 V9 z/OS] Extents and indexes and RTS (and piecesize)






> several whose space allocations needed tweaking. I thought I'd
> double check my results in RTS and noticed that only one of the
> index datasets for an index with multiple files (because of the
> piecesize value) was stored in

It'd be the last datasets the one with extents as in multi-piece index
spaces RTS value is the number of extents for the last data set. Time to
plan a REXX to update RTS columns ?

Max Scarpa






The IDUG DB2-L Listserv is only part of your membership in IDUG. If you
are not already an IDUG member, please register here.

_____________________________________________________________________
* IDUG North America * Anaheim, California * May 2-6 2011 * http://IDUG.ORG/NA *
* Your only source for independent, unbiased, and trusted DB2 information. *
** The most DB2 technical sessions of any conference
** Access IBM experts and developers
_____________________________________________________________________

If you need to change settings, http://www.idug.org/cgi-bin/wa?A0=DB2-L is the home of IDUG's Listserv

Max Scarpa

Re: [DB2 V9 z/OS] Extents and indexes and RTS (and piecesize)
(in response to Roy Boxwell)
You're right of course, I meant use this technique to check if RTS
extents were the same obtained via SMS/LISTCAT/etc (I did it in the past
probably before to apply a PTF for RTS). It was not a clear phrase, I
agree. Probably it's better to not use piecesize if you can avoid it.


Max Scarpa


IDUG DB2-L <[login to unmask email]> wrote on 17/12/2010 10.50.10:

> From: Roy Boxwell <[login to unmask email]>
> To: [login to unmask email]
> Date: 17/12/2010 10.50
> Subject: Re: [DB2-L] [DB2 V9 z/OS] Extents and indexes and RTS (and
piecesize)
> Sent by: IDUG DB2-L <[login to unmask email]>
>
>
> dangerous idea Max! Then at the next externalization of RTS data the
> latest last extents will replace you REXX computed value! Perhaps
> it's better to not use pieces!!! :)
>
> Roy Boxwell
> SOFTWARE ENGINEERING GMBH
> -Product Development-
> Robert-Stolz-Straße 5
> 40470 Düsseldorf/Germany
> Tel. +49 (0)211 96149-675
> Fax +49 (0)211 96149-32
> Email: [login to unmask email]
> http://www.seg.de
>
> Software Engineering GmbH
> Amtsgericht Düsseldorf, HRB 37894
> Geschäftsführung: Gerhard Schubert
>

>
> Max Scarpa <[login to unmask email]>
> Gesendet von: IDUG DB2-L <[login to unmask email]>
> 17.12.2010 10:46
>
> Bitte antworten an
> IDUG DB2-L <[login to unmask email]>
>
> An
>
> [login to unmask email]
>
> Kopie
>
> Thema
>
> Re: [DB2-L] [DB2 V9 z/OS] Extents and indexes and RTS (and piecesize)
>
>
>
>
> > several whose space allocations needed tweaking. I thought I'd
> > double check my results in RTS and noticed that only one of the
> > index datasets for an index with multiple files (because of the
> > piecesize value) was stored in
>
> It'd be the last datasets the one with extents as in multi-piece
> index spaces RTS value is the number of extents for the last data
> set. Time to plan a REXX to update RTS columns ?
>
> Max Scarpa
>
>
>
>

>
> The IDUG DB2-L Listserv is only part of your membership in IDUG. If
> you are not already an IDUG member, please register here.
>

> [image removed]
> The IDUG DB2-L Listserv is only part of your membership in IDUG. If
> you are not already an IDUG member, please register here.

_____________________________________________________________________
* IDUG North America * Anaheim, California * May 2-6 2011 * http://IDUG.ORG/NA *
* Your only source for independent, unbiased, and trusted DB2 information. *
** The most DB2 technical sessions of any conference
** Access IBM experts and developers
_____________________________________________________________________

If you need to change settings, http://www.idug.org/cgi-bin/wa?A0=DB2-L is the home of IDUG's Listserv