[DB2 ZOS DSN11015] Getting less extent for DB2 VSAM

Sam Bo

[DB2 ZOS DSN11015] Getting less extent for DB2 VSAM

Hello,

 

i am a db2 beginner and english is not my first language so sorry for the mistakes.

 

we have warning about tables space or index that have more than 70 extents.

So we reorg the table space but we always have the same number of extent and we afraid about the performance.

So i would like to know how to do to be sure to get less extent for a db2 vsam

 

here is an example : 

Command - Enter "/" to select action                        Tracks %Used   XT 
------------------------------------------------------------------------------
         DB2.DSNDBD.DBV.X5.J0001.A001          8700    ?    31 
         DB2.DSNDBD.DBV.X5.J0001.A001          3150    ?    37 
         DB2.DSNDBD.DBV.X5.J0001.A001         32040    ?    34 
         DB2.DSNDBD.DBV.X5.J0001.A001         36450    ?     1

It takes 36450 TRACKS in one M27 DASD Volume then 34 EXTENT in a second DASD Volume then 37 and 31.

So we have 103 extents !

 

So how to do to gent less extent ?

 

Thank's for your help.

Roy Boxwell

[DB2 ZOS DSN11015] Getting less extent for DB2 VSAM
(in response to Sam Bo)
I would check your REORG parameters – I would hazard a guess that you are using REUSE with SHRLEVEL NONE? If true this does not allocate new datasets or consolidate extents...



I have seen 4000+ extents and no performance problem... I would not even start to consider doing a reorg until well over 300 Extents!



Roy Boxwell

SOFTWARE ENGINEERING GmbH and SEGUS Inc.
-Product Development-

Vagedesstrasse 19
40479 Dusseldorf/Germany
Tel. +49 (0)211 96149-675
Fax +49 (0)211 96149-32
Email: <mailto:[login to unmask email]> [login to unmask email]
Web http://www.seg.de http://www.seg.de

https://www.seg.de/corporate/rechtliche-hinweise/datenschutz Link zur Datenschutzerklärung


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



From: Sam Bo [mailto:[login to unmask email]
Sent: Thursday, January 23, 2020 9:28 AM
To: [login to unmask email]
Subject: [DB2-L] - [DB2 ZOS DSN11015] Getting less extent for DB2 VSAM



Hello,



i am a db2 beginner and english is not my first language so sorry for the mistakes.



we have warning about tables space or index that have more than 70 extents.

So we reorg the table space but we always have the same number of extent and we afraid about the performance.

So i would like to know how to do to be sure to get less extent for a db2 vsam



here is an example :

Command - Enter "/" to select action Tracks %Used XT
------------------------------------------------------------------------------
DB2.DSNDBD.DBV.X5.J0001.A001 8700 ? 31
DB2.DSNDBD.DBV.X5.J0001.A001 3150 ? 37
DB2.DSNDBD.DBV.X5.J0001.A001 32040 ? 34
DB2.DSNDBD.DBV.X5.J0001.A001 36450 ? 1

It takes 36450 TRACKS in one M27 DASD Volume then 34 EXTENT in a second DASD Volume then 37 and 31.

So we have 103 extents !



So how to do to gent less extent ?



Thank's for your help.



-----End Original Message-----

Attachments

  • smime.p7s (5.1k)

Sam Bo

RE: [DB2 ZOS DSN11015] Getting less extent for DB2 VSAM
(in response to Roy Boxwell)

Hello Roy, may be you're right. It is unusefull to REORG in this case.

But the limit is 255 extent.

And we use thsi to creatate the table 

CREATE TABLESPACE TSPVEXRL
IN DBRL
USING STOGROUP SGRL
PRIQTY 1000
SECQTY 9000

CREATE TABLESPACE TSN973RL
IN DBRL
USING STOGROUP SGRL
PRIQTY 1000
SECQTY 100

In the LISTCAT we can see that 

 

ASSOCIATIONS
CLUSTER--DB2REEL.DSNDBC.DBRL.TSN973RL.I0001.A003
ATTRIBUTES
KEYLEN-----------------0 AVGLRECL---------------0 BUFSPACE------
------8192 CISIZE--------------4096
RKP--------------------0 MAXLRECL---------------0 EXCPEXIT------
----(NULL) CI/CA----------------180
SHROPTNS(3,3) SPEED UNIQUE NOERASE LINEAR
NOWRITECHK UNORDERED REUSE
NONSPANNED
STATISTICS
REC-TOTAL--------------0 SPLITS-CI--------------0 EXCPS---------
---------0

...

ALLOCATION
SPACE-TYPE------CYLINDER HI-A-RBA------4294656000
SPACE-PRI--------------2 HI-U-RBA------4293906432
SPACE-SEC--------------1
VOLUME
VOLSER------------PDBDJ0 PHYREC-SIZE---------4096 HI-A-RBA------
-221921280 EXTENT-NUMBER---------47
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
-221921280 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:
LOW-CCHH-----X'03120000' LOW-RBA----------------0 TRACKS--------
--------30
HIGH-CCHH----X'0313000E' HIGH-RBA---------1474559
LOW-CCHH-----X'03390000' LOW-RBA----------1474560 TRACKS--------
--------75
HIGH-CCHH----X'033D000E' HIGH-RBA---------5160959
LOW-CCHH-----X'05FF0000' LOW-RBA----------5160960 TRACKS--------
--------60

...

VOLSER------------PDBDI3 PHYREC-SIZE---------4096 HI-A-RBA------
1394933760 EXTENT-NUMBER---------44
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
1394933760 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:
LOW-CCHH-----X'11D30000' LOW-RBA--------221921280 TRACKS--------
-------375
HIGH-CCHH----X'11EB000E' HIGH-RBA-------240353279
LOW-CCHH-----X'12DA0000' LOW-RBA--------240353280 TRACKS--------
-------390
HIGH-CCHH----X'12F3000E' HIGH-RBA-------259522559
LOW-CCHH-----X'1CE50000' LOW-RBA--------259522560 TRACKS--------
-------825
HIGH-CCHH----X'1D1B000E' HIGH-RBA-------300072959
LOW-CCHH-----X'2A0A0000' LOW-RBA--------300072960 TRACKS--------

...

VOLUME
VOLSER------------PDBDK1 PHYREC-SIZE---------4096 HI-A-RBA------
2632826880 EXTENT-NUMBER---------27
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
2632826880 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:

...

LOW-CCHH-----X'55620000' LOW-RBA-------1394933760 TRACKS--------
-------930
HIGH-CCHH----X'559F000E' HIGH-RBA------1440645119
LOW-CCHH-----X'6ADB0000' LOW-RBA-------1440645120 TRACKS--------
-------945
HIGH-CCHH----X'6B19000E' HIGH-RBA------1487093759
LOW-CCHH-----X'6D440000' LOW-RBA-------1487093760 TRACKS--------
-------960
HIGH-CCHH----X'6D83000E' HIGH-RBA------1534279679
LOW-CCHH-----X'7CB50000' LOW-RBA-------1534279680 TRACKS--------
-----12525
HIGH-CCHH----X'7FF7000E' HIGH-RBA------2149908479
LOW-CCHH-----X'66010000' LOW-RBA-------2149908480 TRACKS--------
-------165

...

VOLUME
VOLSER------------PDBDJ2 PHYREC-SIZE---------4096 HI-A-RBA------
3949608960 EXTENT-NUMBER---------42
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
3949608960 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:
LOW-CCHH-----X'7DBB0000' LOW-RBA-------2632826880 TRACKS--------
------7875
HIGH-CCHH----X'7FC7000E' HIGH-RBA------3019898879
LOW-CCHH-----X'69810000' LOW-RBA-------3019898880 TRACKS--------

...

------1260
HIGH-CCHH----X'69D4000E' HIGH-RBA------3081830399
LOW-CCHH-----X'6AC40000' LOW-RBA-------3081830400 TRACKS--------
-------105
HIGH-CCHH----X'6ACA000E' HIGH-RBA------3086991359
LOW-CCHH-----X'64960000' LOW-RBA-------3086991360 TRACKS--------
-------975
HIGH-CCHH----X'64D6000E' HIGH-RBA------3134914559
LOW-CCHH-----X'6ACB0000' LOW-RBA-------3134914560 TRACKS--------
-------405
HIGH-CCHH----X'6AE5000E' HIGH-RBA------3154821119
LOW-CCHH-----X'4C7F0000' LOW-RBA-------3154821120 TRACKS--------
-------945

...

VOLUME
VOLSER------------PDBDN6 PHYREC-SIZE---------4096 HI-A-RBA------
4294656000 EXTENT-NUMBER----------3
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
4293906432 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:
LOW-CCHH-----X'1ED70000' LOW-RBA-------3949608960 TRACKS--------
------4725
HIGH-CCHH----X'2011000E' HIGH-RBA------4181852159
LOW-CCHH-----X'20CB0000' LOW-RBA-------4181852160 TRACKS--------
------1605
HIGH-CCHH----X'2135000E' HIGH-RBA------4260741119
LOW-CCHH-----X'0CED0000' LOW-RBA-------4260741120 TRACKS--------
-------690
HIGH-CCHH----X'0D1A000E' HIGH-RBA------4294655999

 

Roy Boxwell

[DB2 ZOS DSN11015] Getting less extent for DB2 VSAM
(in response to Sam Bo)
The limit of 255 Extents disappeared years ago...



VSAM Extent Constraint Relief in z/OS V1R7

- New support allowed for 123x59 extents (previous limit was 255)

In previous releases, there was a 255-extent limit for VSAM data sets and, for striped VSAM data sets, a limit of 255 extents per stripe. Now, using the VSAM extent constraint removal enhancement, these extent limits are removed for SMS-managed volumes, if the extent constraint removal parameter in the data class is set to Y (yes). For non SMS-managed volumes, the previous extent limits still apply.


A VSAM data set can be expanded to 123 extents per volume. This is unchanged from previous releases.



I bet you are at a z/OS release well above 1.7.... I know of no shops that do not have Extent Constraint relief active!



Roy Boxwell

SOFTWARE ENGINEERING GmbH and SEGUS Inc.
-Product Development-

Vagedesstrasse 19
40479 Dusseldorf/Germany
Tel. +49 (0)211 96149-675
Fax +49 (0)211 96149-32
Email: <mailto:[login to unmask email]> [login to unmask email]
Web http://www.seg.de http://www.seg.de

https://www.seg.de/corporate/rechtliche-hinweise/datenschutz Link zur Datenschutzerklärung


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



From: Sam Bo [mailto:[login to unmask email]
Sent: Thursday, January 23, 2020 11:06 AM
To: [login to unmask email]
Subject: [DB2-L] - RE: [DB2 ZOS DSN11015] Getting less extent for DB2 VSAM



Hello Roy, may be you're right. It is unusefull to REORG in this case.

But the limit is 255 extent.

And we use thsi to creatate the table

CREATE TABLESPACE TSPVEXRL
IN DBRL
USING STOGROUP SGRL
PRIQTY 1000
SECQTY 9000

CREATE TABLESPACE TSN973RL
IN DBRL
USING STOGROUP SGRL
PRIQTY 1000
SECQTY 100

In the LISTCAT we can see that



ASSOCIATIONS
CLUSTER--DB2REEL.DSNDBC.DBRL.TSN973RL.I0001.A003
ATTRIBUTES
KEYLEN-----------------0 AVGLRECL---------------0 BUFSPACE------
------8192 CISIZE--------------4096
RKP--------------------0 MAXLRECL---------------0 EXCPEXIT------
----(NULL) CI/CA----------------180
SHROPTNS(3,3) SPEED UNIQUE NOERASE LINEAR
NOWRITECHK UNORDERED REUSE
NONSPANNED
STATISTICS
REC-TOTAL--------------0 SPLITS-CI--------------0 EXCPS---------
---------0

...

ALLOCATION
SPACE-TYPE------CYLINDER HI-A-RBA------4294656000
SPACE-PRI--------------2 HI-U-RBA------4293906432
SPACE-SEC--------------1
VOLUME
VOLSER------------PDBDJ0 PHYREC-SIZE---------4096 HI-A-RBA------
-221921280 EXTENT-NUMBER---------47
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
-221921280 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:
LOW-CCHH-----X'03120000' LOW-RBA----------------0 TRACKS--------
--------30
HIGH-CCHH----X'0313000E' HIGH-RBA---------1474559
LOW-CCHH-----X'03390000' LOW-RBA----------1474560 TRACKS--------
--------75
HIGH-CCHH----X'033D000E' HIGH-RBA---------5160959
LOW-CCHH-----X'05FF0000' LOW-RBA----------5160960 TRACKS--------
--------60

...

VOLSER------------PDBDI3 PHYREC-SIZE---------4096 HI-A-RBA------
1394933760 EXTENT-NUMBER---------44
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
1394933760 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:
LOW-CCHH-----X'11D30000' LOW-RBA--------221921280 TRACKS--------
-------375
HIGH-CCHH----X'11EB000E' HIGH-RBA-------240353279
LOW-CCHH-----X'12DA0000' LOW-RBA--------240353280 TRACKS--------
-------390
HIGH-CCHH----X'12F3000E' HIGH-RBA-------259522559
LOW-CCHH-----X'1CE50000' LOW-RBA--------259522560 TRACKS--------
-------825
HIGH-CCHH----X'1D1B000E' HIGH-RBA-------300072959
LOW-CCHH-----X'2A0A0000' LOW-RBA--------300072960 TRACKS--------

...

VOLUME
VOLSER------------PDBDK1 PHYREC-SIZE---------4096 HI-A-RBA------
2632826880 EXTENT-NUMBER---------27
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
2632826880 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:

...

LOW-CCHH-----X'55620000' LOW-RBA-------1394933760 TRACKS--------
-------930
HIGH-CCHH----X'559F000E' HIGH-RBA------1440645119
LOW-CCHH-----X'6ADB0000' LOW-RBA-------1440645120 TRACKS--------
-------945
HIGH-CCHH----X'6B19000E' HIGH-RBA------1487093759
LOW-CCHH-----X'6D440000' LOW-RBA-------1487093760 TRACKS--------
-------960
HIGH-CCHH----X'6D83000E' HIGH-RBA------1534279679
LOW-CCHH-----X'7CB50000' LOW-RBA-------1534279680 TRACKS--------
-----12525
HIGH-CCHH----X'7FF7000E' HIGH-RBA------2149908479
LOW-CCHH-----X'66010000' LOW-RBA-------2149908480 TRACKS--------
-------165

...

VOLUME
VOLSER------------PDBDJ2 PHYREC-SIZE---------4096 HI-A-RBA------
3949608960 EXTENT-NUMBER---------42
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
3949608960 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:
LOW-CCHH-----X'7DBB0000' LOW-RBA-------2632826880 TRACKS--------
------7875
HIGH-CCHH----X'7FC7000E' HIGH-RBA------3019898879
LOW-CCHH-----X'69810000' LOW-RBA-------3019898880 TRACKS--------

...

------1260
HIGH-CCHH----X'69D4000E' HIGH-RBA------3081830399
LOW-CCHH-----X'6AC40000' LOW-RBA-------3081830400 TRACKS--------
-------105
HIGH-CCHH----X'6ACA000E' HIGH-RBA------3086991359
LOW-CCHH-----X'64960000' LOW-RBA-------3086991360 TRACKS--------
-------975
HIGH-CCHH----X'64D6000E' HIGH-RBA------3134914559
LOW-CCHH-----X'6ACB0000' LOW-RBA-------3134914560 TRACKS--------
-------405
HIGH-CCHH----X'6AE5000E' HIGH-RBA------3154821119
LOW-CCHH-----X'4C7F0000' LOW-RBA-------3154821120 TRACKS--------
-------945

...

VOLUME
VOLSER------------PDBDN6 PHYREC-SIZE---------4096 HI-A-RBA------
4294656000 EXTENT-NUMBER----------3
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
4293906432 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:
LOW-CCHH-----X'1ED70000' LOW-RBA-------3949608960 TRACKS--------
------4725
HIGH-CCHH----X'2011000E' HIGH-RBA------4181852159
LOW-CCHH-----X'20CB0000' LOW-RBA-------4181852160 TRACKS--------
------1605
HIGH-CCHH----X'2135000E' HIGH-RBA------4260741119
LOW-CCHH-----X'0CED0000' LOW-RBA-------4260741120 TRACKS--------
-------690
HIGH-CCHH----X'0D1A000E' HIGH-RBA------4294655999





-----End Original Message-----

Attachments

  • smime.p7s (5.1k)

Ruediger Kurtz

AW: [DB2 ZOS DSN11015] Getting less extent for DB2 VSAM
(in response to Sam Bo)
Sam,

you might as well use PRIQTY -1 and SECQTY -1; there’s been some discussion on that very topic here on DB2-L, you may want to search the archives.
We use PRIQTY / SECQTY set to -1, and we have not yet come across any problems.

The limit of 255 extents does no longer apply to each and every shop, you may also want to check the documentation.

Hth

Ruediger


Rüdiger Kurtz
Abteilung Informatik - Betrieb

HUK-COBURG
Bahnhofsplatz
96444 Coburg
Telefon: 09561 96-44148
Telefax: 09561 96-44104
E-Mail: [login to unmask email]
Internet: www.huk.de
________________________________
HUK-COBURG Haftpflicht-Unterstützungs-Kasse kraftfahrender Beamter Deutschlands a. G. in Coburg
Reg.-Gericht Coburg HRB 100; St.-Nr. 9212/101/00021
Sitz der Gesellschaft: Bahnhofsplatz, 96444 Coburg
Vorsitzender des Aufsichtsrats: Prof. Dr. Heinrich R. Schradin.
Vorstand: Klaus-Jürgen Heitmann (Sprecher), Stefan Gronbach, Dr. Hans Olav Herøy, Dr. Jörg Rheinländer, Sarah Rössler, Daniel Thomas.
________________________________
Diese Nachricht enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese Nachricht irrtümlich erhalten haben,
informieren Sie bitte sofort den Absender und vernichten Sie diese Nachricht.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Nachricht ist nicht gestattet.

This information may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this information in error) please notify the
sender immediately and destroy this information.
Any unauthorized copying, disclosure or distribution of the material in this information is strictly forbidden.
________________________________
Von: Sam Bo <[login to unmask email]>
Gesendet: Donnerstag, 23. Januar 2020 11:06
An: [login to unmask email]
Betreff: [DB2-L] - RE: [DB2 ZOS DSN11015] Getting less extent for DB2 VSAM


Hello Roy, may be you're right. It is unusefull to REORG in this case.

But the limit is 255 extent.

And we use thsi to creatate the table

CREATE TABLESPACE TSPVEXRL
IN DBRL
USING STOGROUP SGRL
PRIQTY 1000
SECQTY 9000

CREATE TABLESPACE TSN973RL
IN DBRL
USING STOGROUP SGRL
PRIQTY 1000
SECQTY 100

In the LISTCAT we can see that



ASSOCIATIONS
CLUSTER--DB2REEL.DSNDBC.DBRL.TSN973RL.I0001.A003
ATTRIBUTES
KEYLEN-----------------0 AVGLRECL---------------0 BUFSPACE------
------8192 CISIZE--------------4096
RKP--------------------0 MAXLRECL---------------0 EXCPEXIT------
----(NULL) CI/CA----------------180
SHROPTNS(3,3) SPEED UNIQUE NOERASE LINEAR
NOWRITECHK UNORDERED REUSE
NONSPANNED
STATISTICS
REC-TOTAL--------------0 SPLITS-CI--------------0 EXCPS---------
---------0

...

ALLOCATION
SPACE-TYPE------CYLINDER HI-A-RBA------4294656000
SPACE-PRI--------------2 HI-U-RBA------4293906432
SPACE-SEC--------------1
VOLUME
VOLSER------------PDBDJ0 PHYREC-SIZE---------4096 HI-A-RBA------
-221921280 EXTENT-NUMBER---------47
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
-221921280 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:
LOW-CCHH-----X'03120000' LOW-RBA----------------0 TRACKS--------
--------30
HIGH-CCHH----X'0313000E' HIGH-RBA---------1474559
LOW-CCHH-----X'03390000' LOW-RBA----------1474560 TRACKS--------
--------75
HIGH-CCHH----X'033D000E' HIGH-RBA---------5160959
LOW-CCHH-----X'05FF0000' LOW-RBA----------5160960 TRACKS--------
--------60

...

VOLSER------------PDBDI3 PHYREC-SIZE---------4096 HI-A-RBA------
1394933760 EXTENT-NUMBER---------44
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
1394933760 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:
LOW-CCHH-----X'11D30000' LOW-RBA--------221921280 TRACKS--------
-------375
HIGH-CCHH----X'11EB000E' HIGH-RBA-------240353279
LOW-CCHH-----X'12DA0000' LOW-RBA--------240353280 TRACKS--------
-------390
HIGH-CCHH----X'12F3000E' HIGH-RBA-------259522559
LOW-CCHH-----X'1CE50000' LOW-RBA--------259522560 TRACKS--------
-------825
HIGH-CCHH----X'1D1B000E' HIGH-RBA-------300072959
LOW-CCHH-----X'2A0A0000' LOW-RBA--------300072960 TRACKS--------

...

VOLUME
VOLSER------------PDBDK1 PHYREC-SIZE---------4096 HI-A-RBA------
2632826880 EXTENT-NUMBER---------27
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
2632826880 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:

...

LOW-CCHH-----X'55620000' LOW-RBA-------1394933760 TRACKS--------
-------930
HIGH-CCHH----X'559F000E' HIGH-RBA------1440645119
LOW-CCHH-----X'6ADB0000' LOW-RBA-------1440645120 TRACKS--------
-------945
HIGH-CCHH----X'6B19000E' HIGH-RBA------1487093759
LOW-CCHH-----X'6D440000' LOW-RBA-------1487093760 TRACKS--------
-------960
HIGH-CCHH----X'6D83000E' HIGH-RBA------1534279679
LOW-CCHH-----X'7CB50000' LOW-RBA-------1534279680 TRACKS--------
-----12525
HIGH-CCHH----X'7FF7000E' HIGH-RBA------2149908479
LOW-CCHH-----X'66010000' LOW-RBA-------2149908480 TRACKS--------
-------165

...

VOLUME
VOLSER------------PDBDJ2 PHYREC-SIZE---------4096 HI-A-RBA------
3949608960 EXTENT-NUMBER---------42
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
3949608960 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:
LOW-CCHH-----X'7DBB0000' LOW-RBA-------2632826880 TRACKS--------
------7875
HIGH-CCHH----X'7FC7000E' HIGH-RBA------3019898879
LOW-CCHH-----X'69810000' LOW-RBA-------3019898880 TRACKS--------

...

------1260
HIGH-CCHH----X'69D4000E' HIGH-RBA------3081830399
LOW-CCHH-----X'6AC40000' LOW-RBA-------3081830400 TRACKS--------
-------105
HIGH-CCHH----X'6ACA000E' HIGH-RBA------3086991359
LOW-CCHH-----X'64960000' LOW-RBA-------3086991360 TRACKS--------
-------975
HIGH-CCHH----X'64D6000E' HIGH-RBA------3134914559
LOW-CCHH-----X'6ACB0000' LOW-RBA-------3134914560 TRACKS--------
-------405
HIGH-CCHH----X'6AE5000E' HIGH-RBA------3154821119
LOW-CCHH-----X'4C7F0000' LOW-RBA-------3154821120 TRACKS--------
-------945

...

VOLUME
VOLSER------------PDBDN6 PHYREC-SIZE---------4096 HI-A-RBA------
4294656000 EXTENT-NUMBER----------3
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
4293906432 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:
LOW-CCHH-----X'1ED70000' LOW-RBA-------3949608960 TRACKS--------
------4725
HIGH-CCHH----X'2011000E' HIGH-RBA------4181852159
LOW-CCHH-----X'20CB0000' LOW-RBA-------4181852160 TRACKS--------
------1605
HIGH-CCHH----X'2135000E' HIGH-RBA------4260741119
LOW-CCHH-----X'0CED0000' LOW-RBA-------4260741120 TRACKS--------
-------690
HIGH-CCHH----X'0D1A000E' HIGH-RBA------4294655999



-----End Original Message-----

Raymond Bell

[DB2 ZOS DSN11015] Getting less extent for DB2 VSAM
(in response to Roy Boxwell)
If it bothers you, Sam, just alter the PRIQTY and SECQTY to -1 each, do a quick Reorg and let Db2 worry about it. Extents aren’t a big deal these days, as Roy alluded. Although I must confess to like seeing ‘low’ numbers for extents. Old habits die hard.

Cheers,


Raymond

From: Boxwell, Roy <[login to unmask email]>
Sent: 23 January 2020 10:21
To: [login to unmask email]
Subject: [DB2-L] - RE: [DB2 ZOS DSN11015] Getting less extent for DB2 VSAM

The limit of 255 Extents disappeared years ago...

VSAM Extent Constraint Relief in z/OS V1R7

- New support allowed for 123x59 extents (previous limit was 255)

In previous releases, there was a 255-extent limit for VSAM data sets and, for striped VSAM data sets, a limit of 255 extents per stripe. Now, using the VSAM extent constraint removal enhancement, these extent limits are removed for SMS-managed volumes, if the extent constraint removal parameter in the data class is set to Y (yes). For non SMS-managed volumes, the previous extent limits still apply.


A VSAM data set can be expanded to 123 extents per volume. This is unchanged from previous releases.

I bet you are at a z/OS release well above 1.7.... I know of no shops that do not have Extent Constraint relief active!

Roy Boxwell

SOFTWARE ENGINEERING GmbH and SEGUS Inc.
-Product Development-

Vagedesstrasse 19
40479 Dusseldorf/Germany
Tel. +49 (0)211 96149-675
Fax +49 (0)211 96149-32
Email: [login to unmask email]<mailto:[login to unmask email]>
Web http://www.seg.de http://www.seg.de
Link zur Datenschutzerklärung https://www.seg.de/corporate/rechtliche-hinweise/datenschutz

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

From: Sam Bo [mailto:[login to unmask email]
Sent: Thursday, January 23, 2020 11:06 AM
To: [login to unmask email]<mailto:[login to unmask email]>
Subject: [DB2-L] - RE: [DB2 ZOS DSN11015] Getting less extent for DB2 VSAM


Hello Roy, may be you're right. It is unusefull to REORG in this case.

But the limit is 255 extent.

And we use thsi to creatate the table

CREATE TABLESPACE TSPVEXRL
IN DBRL
USING STOGROUP SGRL
PRIQTY 1000
SECQTY 9000

CREATE TABLESPACE TSN973RL
IN DBRL
USING STOGROUP SGRL
PRIQTY 1000
SECQTY 100

In the LISTCAT we can see that



ASSOCIATIONS
CLUSTER--DB2REEL.DSNDBC.DBRL.TSN973RL.I0001.A003
ATTRIBUTES
KEYLEN-----------------0 AVGLRECL---------------0 BUFSPACE------
------8192 CISIZE--------------4096
RKP--------------------0 MAXLRECL---------------0 EXCPEXIT------
----(NULL) CI/CA----------------180
SHROPTNS(3,3) SPEED UNIQUE NOERASE LINEAR
NOWRITECHK UNORDERED REUSE
NONSPANNED
STATISTICS
REC-TOTAL--------------0 SPLITS-CI--------------0 EXCPS---------
---------0

...

ALLOCATION
SPACE-TYPE------CYLINDER HI-A-RBA------4294656000
SPACE-PRI--------------2 HI-U-RBA------4293906432
SPACE-SEC--------------1
VOLUME
VOLSER------------PDBDJ0 PHYREC-SIZE---------4096 HI-A-RBA------
-221921280 EXTENT-NUMBER---------47
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
-221921280 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:
LOW-CCHH-----X'03120000' LOW-RBA----------------0 TRACKS--------
--------30
HIGH-CCHH----X'0313000E' HIGH-RBA---------1474559
LOW-CCHH-----X'03390000' LOW-RBA----------1474560 TRACKS--------
--------75
HIGH-CCHH----X'033D000E' HIGH-RBA---------5160959
LOW-CCHH-----X'05FF0000' LOW-RBA----------5160960 TRACKS--------
--------60

...

VOLSER------------PDBDI3 PHYREC-SIZE---------4096 HI-A-RBA------
1394933760 EXTENT-NUMBER---------44
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
1394933760 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:
LOW-CCHH-----X'11D30000' LOW-RBA--------221921280 TRACKS--------
-------375
HIGH-CCHH----X'11EB000E' HIGH-RBA-------240353279
LOW-CCHH-----X'12DA0000' LOW-RBA--------240353280 TRACKS--------
-------390
HIGH-CCHH----X'12F3000E' HIGH-RBA-------259522559
LOW-CCHH-----X'1CE50000' LOW-RBA--------259522560 TRACKS--------
-------825
HIGH-CCHH----X'1D1B000E' HIGH-RBA-------300072959
LOW-CCHH-----X'2A0A0000' LOW-RBA--------300072960 TRACKS--------

...

VOLUME
VOLSER------------PDBDK1 PHYREC-SIZE---------4096 HI-A-RBA------
2632826880 EXTENT-NUMBER---------27
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
2632826880 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:

...

LOW-CCHH-----X'55620000' LOW-RBA-------1394933760 TRACKS--------
-------930
HIGH-CCHH----X'559F000E' HIGH-RBA------1440645119
LOW-CCHH-----X'6ADB0000' LOW-RBA-------1440645120 TRACKS--------
-------945
HIGH-CCHH----X'6B19000E' HIGH-RBA------1487093759
LOW-CCHH-----X'6D440000' LOW-RBA-------1487093760 TRACKS--------
-------960
HIGH-CCHH----X'6D83000E' HIGH-RBA------1534279679
LOW-CCHH-----X'7CB50000' LOW-RBA-------1534279680 TRACKS--------
-----12525
HIGH-CCHH----X'7FF7000E' HIGH-RBA------2149908479
LOW-CCHH-----X'66010000' LOW-RBA-------2149908480 TRACKS--------
-------165

...

VOLUME
VOLSER------------PDBDJ2 PHYREC-SIZE---------4096 HI-A-RBA------
3949608960 EXTENT-NUMBER---------42
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
3949608960 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:
LOW-CCHH-----X'7DBB0000' LOW-RBA-------2632826880 TRACKS--------
------7875
HIGH-CCHH----X'7FC7000E' HIGH-RBA------3019898879
LOW-CCHH-----X'69810000' LOW-RBA-------3019898880 TRACKS--------

...

------1260
HIGH-CCHH----X'69D4000E' HIGH-RBA------3081830399
LOW-CCHH-----X'6AC40000' LOW-RBA-------3081830400 TRACKS--------
-------105
HIGH-CCHH----X'6ACA000E' HIGH-RBA------3086991359
LOW-CCHH-----X'64960000' LOW-RBA-------3086991360 TRACKS--------
-------975
HIGH-CCHH----X'64D6000E' HIGH-RBA------3134914559
LOW-CCHH-----X'6ACB0000' LOW-RBA-------3134914560 TRACKS--------
-------405
HIGH-CCHH----X'6AE5000E' HIGH-RBA------3154821119
LOW-CCHH-----X'4C7F0000' LOW-RBA-------3154821120 TRACKS--------
-------945

...

VOLUME
VOLSER------------PDBDN6 PHYREC-SIZE---------4096 HI-A-RBA------
4294656000 EXTENT-NUMBER----------3
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
4293906432 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:
LOW-CCHH-----X'1ED70000' LOW-RBA-------3949608960 TRACKS--------
------4725
HIGH-CCHH----X'2011000E' HIGH-RBA------4181852159
LOW-CCHH-----X'20CB0000' LOW-RBA-------4181852160 TRACKS--------
------1605
HIGH-CCHH----X'2135000E' HIGH-RBA------4260741119
LOW-CCHH-----X'0CED0000' LOW-RBA-------4260741120 TRACKS--------
-------690
HIGH-CCHH----X'0D1A000E' HIGH-RBA------4294655999



-----End Original Message-----
The Royal Bank of Scotland plc. Registered in Scotland No 83026. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. The Royal Bank of Scotland is authorised by the Prudential Regulation Authority, and regulated by the Financial Conduct Authority and Prudential Regulation Authority. The Royal Bank of Scotland N.V. is authorised and regulated by the De Nederlandsche Bank and has its seat at Amsterdam, the Netherlands, and is registered in the Commercial Register under number 33002587. Registered Office: Gustav Mahlerlaan 350, Amsterdam, The Netherlands. The Royal Bank of Scotland N.V. and The Royal Bank of Scotland plc are authorised to act as agent for each other in certain jurisdictions.

National Westminster Bank Plc. Registered in England No. 929027. Registered Office: 135 Bishopsgate, London EC2M 3UR. National Westminster Bank Plc is authorised by the Prudential Regulation Authority, and regulated by the Financial Conduct Authority and the Prudential Regulation Authority.

The Royal Bank of Scotland plc and National Westminster Bank Plc are authorised to act as agent for each other.

This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc, The Royal Bank of Scotland N.V., National Westminster Bank Plc or any affiliated entity (RBS or us) does not accept responsibility for changes made to this message after it was sent. RBS may monitor e-mails for business and operational purposes. By replying to this message you understand that the content of your message may be monitored.

Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by RBS in this regard and the recipient should carry out such virus and other checks as it considers appropriate.

Visit our website at www.rbs.com http://www.rbs.com

Raymond Bell

[DB2 ZOS DSN11015] Getting less extent for DB2 VSAM
(in response to Ruediger Kurtz)
Snap!

From: Kurtz, Rüdiger <[login to unmask email]>
Sent: 23 January 2020 10:23
To: '[login to unmask email]' <[login to unmask email]>
Subject: [DB2-L] - AW: [DB2 ZOS DSN11015] Getting less extent for DB2 VSAM


*********************************************
"This is an external email. Do you know who has sent it? Can you be sure that any links and attachments contained within it are safe? If in any doubt, use the Phishing Reporter Button in your Outlook client or forward the email as an attachment to ~ I've Been Phished"
*********************************************
Sam,

you might as well use PRIQTY -1 and SECQTY -1; there’s been some discussion on that very topic here on DB2-L, you may want to search the archives.
We use PRIQTY / SECQTY set to -1, and we have not yet come across any problems.

The limit of 255 extents does no longer apply to each and every shop, you may also want to check the documentation.

Hth

Ruediger


Rüdiger Kurtz
Abteilung Informatik - Betrieb

HUK-COBURG
Bahnhofsplatz
96444 Coburg
Telefon:
09561 96-44148
Telefax:
09561 96-44104
E-Mail:
[login to unmask email]<mailto:[login to unmask email]>
Internet:
www.huk.de http://www.huk.de
________________________________
HUK-COBURG Haftpflicht-Unterstützungs-Kasse kraftfahrender Beamter Deutschlands a. G. in Coburg
Reg.-Gericht Coburg HRB 100; St.-Nr. 9212/101/00021
Sitz der Gesellschaft: Bahnhofsplatz, 96444 Coburg
Vorsitzender des Aufsichtsrats: Prof. Dr. Heinrich R. Schradin.
Vorstand: Klaus-Jürgen Heitmann (Sprecher), Stefan Gronbach, Dr. Hans Olav Herøy, Dr. Jörg Rheinländer, Sarah Rössler, Daniel Thomas.
________________________________
Diese Nachricht enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese Nachricht irrtümlich erhalten haben,
informieren Sie bitte sofort den Absender und vernichten Sie diese Nachricht.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Nachricht ist nicht gestattet.

This information may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this information in error) please notify the
sender immediately and destroy this information.
Any unauthorized copying, disclosure or distribution of the material in this information is strictly forbidden.
________________________________
Von: Sam Bo <[login to unmask email]<mailto:[login to unmask email]>>
Gesendet: Donnerstag, 23. Januar 2020 11:06
An: [login to unmask email]<mailto:[login to unmask email]>
Betreff: [DB2-L] - RE: [DB2 ZOS DSN11015] Getting less extent for DB2 VSAM


Hello Roy, may be you're right. It is unusefull to REORG in this case.

But the limit is 255 extent.

And we use thsi to creatate the table

CREATE TABLESPACE TSPVEXRL
IN DBRL
USING STOGROUP SGRL
PRIQTY 1000
SECQTY 9000

CREATE TABLESPACE TSN973RL
IN DBRL
USING STOGROUP SGRL
PRIQTY 1000
SECQTY 100

In the LISTCAT we can see that



ASSOCIATIONS
CLUSTER--DB2REEL.DSNDBC.DBRL.TSN973RL.I0001.A003
ATTRIBUTES
KEYLEN-----------------0 AVGLRECL---------------0 BUFSPACE------
------8192 CISIZE--------------4096
RKP--------------------0 MAXLRECL---------------0 EXCPEXIT------
----(NULL) CI/CA----------------180
SHROPTNS(3,3) SPEED UNIQUE NOERASE LINEAR
NOWRITECHK UNORDERED REUSE
NONSPANNED
STATISTICS
REC-TOTAL--------------0 SPLITS-CI--------------0 EXCPS---------
---------0

...

ALLOCATION
SPACE-TYPE------CYLINDER HI-A-RBA------4294656000
SPACE-PRI--------------2 HI-U-RBA------4293906432
SPACE-SEC--------------1
VOLUME
VOLSER------------PDBDJ0 PHYREC-SIZE---------4096 HI-A-RBA------
-221921280 EXTENT-NUMBER---------47
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
-221921280 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:
LOW-CCHH-----X'03120000' LOW-RBA----------------0 TRACKS--------
--------30
HIGH-CCHH----X'0313000E' HIGH-RBA---------1474559
LOW-CCHH-----X'03390000' LOW-RBA----------1474560 TRACKS--------
--------75
HIGH-CCHH----X'033D000E' HIGH-RBA---------5160959
LOW-CCHH-----X'05FF0000' LOW-RBA----------5160960 TRACKS--------
--------60

...

VOLSER------------PDBDI3 PHYREC-SIZE---------4096 HI-A-RBA------
1394933760 EXTENT-NUMBER---------44
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
1394933760 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:
LOW-CCHH-----X'11D30000' LOW-RBA--------221921280 TRACKS--------
-------375
HIGH-CCHH----X'11EB000E' HIGH-RBA-------240353279
LOW-CCHH-----X'12DA0000' LOW-RBA--------240353280 TRACKS--------
-------390
HIGH-CCHH----X'12F3000E' HIGH-RBA-------259522559
LOW-CCHH-----X'1CE50000' LOW-RBA--------259522560 TRACKS--------
-------825
HIGH-CCHH----X'1D1B000E' HIGH-RBA-------300072959
LOW-CCHH-----X'2A0A0000' LOW-RBA--------300072960 TRACKS--------

...

VOLUME
VOLSER------------PDBDK1 PHYREC-SIZE---------4096 HI-A-RBA------
2632826880 EXTENT-NUMBER---------27
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
2632826880 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:

...

LOW-CCHH-----X'55620000' LOW-RBA-------1394933760 TRACKS--------
-------930
HIGH-CCHH----X'559F000E' HIGH-RBA------1440645119
LOW-CCHH-----X'6ADB0000' LOW-RBA-------1440645120 TRACKS--------
-------945
HIGH-CCHH----X'6B19000E' HIGH-RBA------1487093759
LOW-CCHH-----X'6D440000' LOW-RBA-------1487093760 TRACKS--------
-------960
HIGH-CCHH----X'6D83000E' HIGH-RBA------1534279679
LOW-CCHH-----X'7CB50000' LOW-RBA-------1534279680 TRACKS--------
-----12525
HIGH-CCHH----X'7FF7000E' HIGH-RBA------2149908479
LOW-CCHH-----X'66010000' LOW-RBA-------2149908480 TRACKS--------
-------165

...

VOLUME
VOLSER------------PDBDJ2 PHYREC-SIZE---------4096 HI-A-RBA------
3949608960 EXTENT-NUMBER---------42
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
3949608960 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:
LOW-CCHH-----X'7DBB0000' LOW-RBA-------2632826880 TRACKS--------
------7875
HIGH-CCHH----X'7FC7000E' HIGH-RBA------3019898879
LOW-CCHH-----X'69810000' LOW-RBA-------3019898880 TRACKS--------

...

------1260
HIGH-CCHH----X'69D4000E' HIGH-RBA------3081830399
LOW-CCHH-----X'6AC40000' LOW-RBA-------3081830400 TRACKS--------
-------105
HIGH-CCHH----X'6ACA000E' HIGH-RBA------3086991359
LOW-CCHH-----X'64960000' LOW-RBA-------3086991360 TRACKS--------
-------975
HIGH-CCHH----X'64D6000E' HIGH-RBA------3134914559
LOW-CCHH-----X'6ACB0000' LOW-RBA-------3134914560 TRACKS--------
-------405
HIGH-CCHH----X'6AE5000E' HIGH-RBA------3154821119
LOW-CCHH-----X'4C7F0000' LOW-RBA-------3154821120 TRACKS--------
-------945

...

VOLUME
VOLSER------------PDBDN6 PHYREC-SIZE---------4096 HI-A-RBA------
4294656000 EXTENT-NUMBER----------3
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
4293906432 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:
LOW-CCHH-----X'1ED70000' LOW-RBA-------3949608960 TRACKS--------
------4725
HIGH-CCHH----X'2011000E' HIGH-RBA------4181852159
LOW-CCHH-----X'20CB0000' LOW-RBA-------4181852160 TRACKS--------
------1605
HIGH-CCHH----X'2135000E' HIGH-RBA------4260741119
LOW-CCHH-----X'0CED0000' LOW-RBA-------4260741120 TRACKS--------
-------690
HIGH-CCHH----X'0D1A000E' HIGH-RBA------4294655999



-----End Original Message-----

-----End Original Message-----
The Royal Bank of Scotland plc. Registered in Scotland No 83026. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. The Royal Bank of Scotland is authorised by the Prudential Regulation Authority, and regulated by the Financial Conduct Authority and Prudential Regulation Authority. The Royal Bank of Scotland N.V. is authorised and regulated by the De Nederlandsche Bank and has its seat at Amsterdam, the Netherlands, and is registered in the Commercial Register under number 33002587. Registered Office: Gustav Mahlerlaan 350, Amsterdam, The Netherlands. The Royal Bank of Scotland N.V. and The Royal Bank of Scotland plc are authorised to act as agent for each other in certain jurisdictions.

National Westminster Bank Plc. Registered in England No. 929027. Registered Office: 135 Bishopsgate, London EC2M 3UR. National Westminster Bank Plc is authorised by the Prudential Regulation Authority, and regulated by the Financial Conduct Authority and the Prudential Regulation Authority.

The Royal Bank of Scotland plc and National Westminster Bank Plc are authorised to act as agent for each other.

This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc, The Royal Bank of Scotland N.V., National Westminster Bank Plc or any affiliated entity (RBS or us) does not accept responsibility for changes made to this message after it was sent. RBS may monitor e-mails for business and operational purposes. By replying to this message you understand that the content of your message may be monitored.

Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by RBS in this regard and the recipient should carry out such virus and other checks as it considers appropriate.

Visit our website at www.rbs.com http://www.rbs.com

Ruediger Kurtz

AW: [DB2 ZOS DSN11015] Getting less extent for DB2 VSAM
(in response to Raymond Bell)
too true, old habits die hard - same here … in my younger days I divided priqty / secqty by 720 and shyed away from huge primary allocations; well, times have changed a bit along my way from V1.3, have they not.

Rüdiger


Rüdiger Kurtz
Abteilung Informatik - Betrieb

HUK-COBURG
Bahnhofsplatz
96444 Coburg
Telefon: 09561 96-44148
Telefax: 09561 96-44104
E-Mail: [login to unmask email]
Internet: www.huk.de
________________________________
HUK-COBURG Haftpflicht-Unterstützungs-Kasse kraftfahrender Beamter Deutschlands a. G. in Coburg
Reg.-Gericht Coburg HRB 100; St.-Nr. 9212/101/00021
Sitz der Gesellschaft: Bahnhofsplatz, 96444 Coburg
Vorsitzender des Aufsichtsrats: Prof. Dr. Heinrich R. Schradin.
Vorstand: Klaus-Jürgen Heitmann (Sprecher), Stefan Gronbach, Dr. Hans Olav Herøy, Dr. Jörg Rheinländer, Sarah Rössler, Daniel Thomas.
________________________________
Diese Nachricht enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese Nachricht irrtümlich erhalten haben,
informieren Sie bitte sofort den Absender und vernichten Sie diese Nachricht.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Nachricht ist nicht gestattet.

This information may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this information in error) please notify the
sender immediately and destroy this information.
Any unauthorized copying, disclosure or distribution of the material in this information is strictly forbidden.
________________________________
Von: Bell, Raymond (Hosting Services, Technology) <[login to unmask email]>
Gesendet: Donnerstag, 23. Januar 2020 11:25
An: [login to unmask email]
Betreff: [DB2-L] - RE: [DB2 ZOS DSN11015] Getting less extent for DB2 VSAM

If it bothers you, Sam, just alter the PRIQTY and SECQTY to -1 each, do a quick Reorg and let Db2 worry about it. Extents aren’t a big deal these days, as Roy alluded. Although I must confess to like seeing ‘low’ numbers for extents. Old habits die hard.

Cheers,


Raymond

From: Boxwell, Roy <[login to unmask email]<mailto:[login to unmask email]>>
Sent: 23 January 2020 10:21
To: [login to unmask email]<mailto:[login to unmask email]>
Subject: [DB2-L] - RE: [DB2 ZOS DSN11015] Getting less extent for DB2 VSAM

The limit of 255 Extents disappeared years ago...

VSAM Extent Constraint Relief in z/OS V1R7

- New support allowed for 123x59 extents (previous limit was 255)

In previous releases, there was a 255-extent limit for VSAM data sets and, for striped VSAM data sets, a limit of 255 extents per stripe. Now, using the VSAM extent constraint removal enhancement, these extent limits are removed for SMS-managed volumes, if the extent constraint removal parameter in the data class is set to Y (yes). For non SMS-managed volumes, the previous extent limits still apply.


A VSAM data set can be expanded to 123 extents per volume. This is unchanged from previous releases.

I bet you are at a z/OS release well above 1.7.... I know of no shops that do not have Extent Constraint relief active!

Roy Boxwell

SOFTWARE ENGINEERING GmbH and SEGUS Inc.
-Product Development-

Vagedesstrasse 19
40479 Dusseldorf/Germany
Tel. +49 (0)211 96149-675
Fax +49 (0)211 96149-32
Email: [login to unmask email]<mailto:[login to unmask email]>
Web http://www.seg.de http://www.seg.de
Link zur Datenschutzerklärung https://www.seg.de/corporate/rechtliche-hinweise/datenschutz

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

From: Sam Bo [mailto:[login to unmask email]
Sent: Thursday, January 23, 2020 11:06 AM
To: [login to unmask email]<mailto:[login to unmask email]>
Subject: [DB2-L] - RE: [DB2 ZOS DSN11015] Getting less extent for DB2 VSAM


Hello Roy, may be you're right. It is unusefull to REORG in this case.

But the limit is 255 extent.

And we use thsi to creatate the table

CREATE TABLESPACE TSPVEXRL
IN DBRL
USING STOGROUP SGRL
PRIQTY 1000
SECQTY 9000

CREATE TABLESPACE TSN973RL
IN DBRL
USING STOGROUP SGRL
PRIQTY 1000
SECQTY 100

In the LISTCAT we can see that



ASSOCIATIONS
CLUSTER--DB2REEL.DSNDBC.DBRL.TSN973RL.I0001.A003
ATTRIBUTES
KEYLEN-----------------0 AVGLRECL---------------0 BUFSPACE------
------8192 CISIZE--------------4096
RKP--------------------0 MAXLRECL---------------0 EXCPEXIT------
----(NULL) CI/CA----------------180
SHROPTNS(3,3) SPEED UNIQUE NOERASE LINEAR
NOWRITECHK UNORDERED REUSE
NONSPANNED
STATISTICS
REC-TOTAL--------------0 SPLITS-CI--------------0 EXCPS---------
---------0

...

ALLOCATION
SPACE-TYPE------CYLINDER HI-A-RBA------4294656000
SPACE-PRI--------------2 HI-U-RBA------4293906432
SPACE-SEC--------------1
VOLUME
VOLSER------------PDBDJ0 PHYREC-SIZE---------4096 HI-A-RBA------
-221921280 EXTENT-NUMBER---------47
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
-221921280 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:
LOW-CCHH-----X'03120000' LOW-RBA----------------0 TRACKS--------
--------30
HIGH-CCHH----X'0313000E' HIGH-RBA---------1474559
LOW-CCHH-----X'03390000' LOW-RBA----------1474560 TRACKS--------
--------75
HIGH-CCHH----X'033D000E' HIGH-RBA---------5160959
LOW-CCHH-----X'05FF0000' LOW-RBA----------5160960 TRACKS--------
--------60

...

VOLSER------------PDBDI3 PHYREC-SIZE---------4096 HI-A-RBA------
1394933760 EXTENT-NUMBER---------44
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
1394933760 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:
LOW-CCHH-----X'11D30000' LOW-RBA--------221921280 TRACKS--------
-------375
HIGH-CCHH----X'11EB000E' HIGH-RBA-------240353279
LOW-CCHH-----X'12DA0000' LOW-RBA--------240353280 TRACKS--------
-------390
HIGH-CCHH----X'12F3000E' HIGH-RBA-------259522559
LOW-CCHH-----X'1CE50000' LOW-RBA--------259522560 TRACKS--------
-------825
HIGH-CCHH----X'1D1B000E' HIGH-RBA-------300072959
LOW-CCHH-----X'2A0A0000' LOW-RBA--------300072960 TRACKS--------

...

VOLUME
VOLSER------------PDBDK1 PHYREC-SIZE---------4096 HI-A-RBA------
2632826880 EXTENT-NUMBER---------27
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
2632826880 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:

...

LOW-CCHH-----X'55620000' LOW-RBA-------1394933760 TRACKS--------
-------930
HIGH-CCHH----X'559F000E' HIGH-RBA------1440645119
LOW-CCHH-----X'6ADB0000' LOW-RBA-------1440645120 TRACKS--------
-------945
HIGH-CCHH----X'6B19000E' HIGH-RBA------1487093759
LOW-CCHH-----X'6D440000' LOW-RBA-------1487093760 TRACKS--------
-------960
HIGH-CCHH----X'6D83000E' HIGH-RBA------1534279679
LOW-CCHH-----X'7CB50000' LOW-RBA-------1534279680 TRACKS--------
-----12525
HIGH-CCHH----X'7FF7000E' HIGH-RBA------2149908479
LOW-CCHH-----X'66010000' LOW-RBA-------2149908480 TRACKS--------
-------165

...

VOLUME
VOLSER------------PDBDJ2 PHYREC-SIZE---------4096 HI-A-RBA------
3949608960 EXTENT-NUMBER---------42
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
3949608960 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:
LOW-CCHH-----X'7DBB0000' LOW-RBA-------2632826880 TRACKS--------
------7875
HIGH-CCHH----X'7FC7000E' HIGH-RBA------3019898879
LOW-CCHH-----X'69810000' LOW-RBA-------3019898880 TRACKS--------

...

------1260
HIGH-CCHH----X'69D4000E' HIGH-RBA------3081830399
LOW-CCHH-----X'6AC40000' LOW-RBA-------3081830400 TRACKS--------
-------105
HIGH-CCHH----X'6ACA000E' HIGH-RBA------3086991359
LOW-CCHH-----X'64960000' LOW-RBA-------3086991360 TRACKS--------
-------975
HIGH-CCHH----X'64D6000E' HIGH-RBA------3134914559
LOW-CCHH-----X'6ACB0000' LOW-RBA-------3134914560 TRACKS--------
-------405
HIGH-CCHH----X'6AE5000E' HIGH-RBA------3154821119
LOW-CCHH-----X'4C7F0000' LOW-RBA-------3154821120 TRACKS--------
-------945

...

VOLUME
VOLSER------------PDBDN6 PHYREC-SIZE---------4096 HI-A-RBA------
4294656000 EXTENT-NUMBER----------3
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
4293906432 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:
LOW-CCHH-----X'1ED70000' LOW-RBA-------3949608960 TRACKS--------
------4725
HIGH-CCHH----X'2011000E' HIGH-RBA------4181852159
LOW-CCHH-----X'20CB0000' LOW-RBA-------4181852160 TRACKS--------
------1605
HIGH-CCHH----X'2135000E' HIGH-RBA------4260741119
LOW-CCHH-----X'0CED0000' LOW-RBA-------4260741120 TRACKS--------
-------690
HIGH-CCHH----X'0D1A000E' HIGH-RBA------4294655999



-----End Original Message-----
The Royal Bank of Scotland plc. Registered in Scotland No 83026. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. The Royal Bank of Scotland is authorised by the Prudential Regulation Authority, and regulated by the Financial Conduct Authority and Prudential Regulation Authority. The Royal Bank of Scotland N.V. is authorised and regulated by the De Nederlandsche Bank and has its seat at Amsterdam, the Netherlands, and is registered in the Commercial Register under number 33002587. Registered Office: Gustav Mahlerlaan 350, Amsterdam, The Netherlands. The Royal Bank of Scotland N.V. and The Royal Bank of Scotland plc are authorised to act as agent for each other in certain jurisdictions.

National Westminster Bank Plc. Registered in England No. 929027. Registered Office: 250 Bishopsgate, London EC2M 4AA. National Westminster Bank Plc is authorised by the Prudential Regulation Authority, and regulated by the Financial Conduct Authority and the Prudential Regulation Authority.

The Royal Bank of Scotland plc and National Westminster Bank Plc are authorised to act as agent for each other.

This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc, The Royal Bank of Scotland N.V., National Westminster Bank Plc or any affiliated entity (RBS or us) does not accept responsibility for changes made to this message after it was sent. RBS may monitor e-mails for business and operational purposes. By replying to this message you understand that the content of your message may be monitored.

Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by RBS in this regard and the recipient should carry out such virus and other checks as it considers appropriate.


Visit our website at www.rbs.com http://www.rbs.com
-----End Original Message-----

Roy Boxwell

[DB2 ZOS DSN11015] Getting less extent for DB2 VSAM
(in response to Raymond Bell)
I will just mention one tiny problem with the global -1 -1 settings



If you are using DSN1COPY to move data around then you can actually have a problem due to the space allocation being incorrect. I small problem but one you need to be aware of... SECQTY -1 every time!!!



Roy Boxwell

SOFTWARE ENGINEERING GmbH and SEGUS Inc.
-Product Development-

Vagedesstrasse 19
40479 Dusseldorf/Germany
Tel. +49 (0)211 96149-675
Fax +49 (0)211 96149-32
Email: <mailto:[login to unmask email]> [login to unmask email]
Web http://www.seg.de http://www.seg.de

https://www.seg.de/corporate/rechtliche-hinweise/datenschutz Link zur Datenschutzerklärung


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



From: Bell, Raymond (Hosting Services, Technology) [mailto:[login to unmask email]
Sent: Thursday, January 23, 2020 11:25 AM
To: [login to unmask email]
Subject: [DB2-L] - RE: [DB2 ZOS DSN11015] Getting less extent for DB2 VSAM



If it bothers you, Sam, just alter the PRIQTY and SECQTY to -1 each, do a quick Reorg and let Db2 worry about it. Extents aren’t a big deal these days, as Roy alluded. Although I must confess to like seeing ‘low’ numbers for extents. Old habits die hard.



Cheers,





Raymond



From: Boxwell, Roy <[login to unmask email] <mailto:[login to unmask email]> >
Sent: 23 January 2020 10:21
To: [login to unmask email] <mailto:[login to unmask email]>
Subject: [DB2-L] - RE: [DB2 ZOS DSN11015] Getting less extent for DB2 VSAM



The limit of 255 Extents disappeared years ago...



VSAM Extent Constraint Relief in z/OS V1R7

- New support allowed for 123x59 extents (previous limit was 255)

In previous releases, there was a 255-extent limit for VSAM data sets and, for striped VSAM data sets, a limit of 255 extents per stripe. Now, using the VSAM extent constraint removal enhancement, these extent limits are removed for SMS-managed volumes, if the extent constraint removal parameter in the data class is set to Y (yes). For non SMS-managed volumes, the previous extent limits still apply.


A VSAM data set can be expanded to 123 extents per volume. This is unchanged from previous releases.



I bet you are at a z/OS release well above 1.7.... I know of no shops that do not have Extent Constraint relief active!



Roy Boxwell

SOFTWARE ENGINEERING GmbH and SEGUS Inc.
-Product Development-

Vagedesstrasse 19
40479 Dusseldorf/Germany
Tel. +49 (0)211 96149-675
Fax +49 (0)211 96149-32
Email: <mailto:[login to unmask email]> [login to unmask email]
Web http://www.seg.de http://www.seg.de

https://www.seg.de/corporate/rechtliche-hinweise/datenschutz Link zur Datenschutzerklärung


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



From: Sam Bo [mailto:[login to unmask email]
Sent: Thursday, January 23, 2020 11:06 AM
To: [login to unmask email] <mailto:[login to unmask email]>
Subject: [DB2-L] - RE: [DB2 ZOS DSN11015] Getting less extent for DB2 VSAM



Hello Roy, may be you're right. It is unusefull to REORG in this case.

But the limit is 255 extent.

And we use thsi to creatate the table

CREATE TABLESPACE TSPVEXRL
IN DBRL
USING STOGROUP SGRL
PRIQTY 1000
SECQTY 9000

CREATE TABLESPACE TSN973RL
IN DBRL
USING STOGROUP SGRL
PRIQTY 1000
SECQTY 100

In the LISTCAT we can see that



ASSOCIATIONS
CLUSTER--DB2REEL.DSNDBC.DBRL.TSN973RL.I0001.A003
ATTRIBUTES
KEYLEN-----------------0 AVGLRECL---------------0 BUFSPACE------
------8192 CISIZE--------------4096
RKP--------------------0 MAXLRECL---------------0 EXCPEXIT------
----(NULL) CI/CA----------------180
SHROPTNS(3,3) SPEED UNIQUE NOERASE LINEAR
NOWRITECHK UNORDERED REUSE
NONSPANNED
STATISTICS
REC-TOTAL--------------0 SPLITS-CI--------------0 EXCPS---------
---------0

...

ALLOCATION
SPACE-TYPE------CYLINDER HI-A-RBA------4294656000
SPACE-PRI--------------2 HI-U-RBA------4293906432
SPACE-SEC--------------1
VOLUME
VOLSER------------PDBDJ0 PHYREC-SIZE---------4096 HI-A-RBA------
-221921280 EXTENT-NUMBER---------47
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
-221921280 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:
LOW-CCHH-----X'03120000' LOW-RBA----------------0 TRACKS--------
--------30
HIGH-CCHH----X'0313000E' HIGH-RBA---------1474559
LOW-CCHH-----X'03390000' LOW-RBA----------1474560 TRACKS--------
--------75
HIGH-CCHH----X'033D000E' HIGH-RBA---------5160959
LOW-CCHH-----X'05FF0000' LOW-RBA----------5160960 TRACKS--------
--------60

...

VOLSER------------PDBDI3 PHYREC-SIZE---------4096 HI-A-RBA------
1394933760 EXTENT-NUMBER---------44
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
1394933760 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:
LOW-CCHH-----X'11D30000' LOW-RBA--------221921280 TRACKS--------
-------375
HIGH-CCHH----X'11EB000E' HIGH-RBA-------240353279
LOW-CCHH-----X'12DA0000' LOW-RBA--------240353280 TRACKS--------
-------390
HIGH-CCHH----X'12F3000E' HIGH-RBA-------259522559
LOW-CCHH-----X'1CE50000' LOW-RBA--------259522560 TRACKS--------
-------825
HIGH-CCHH----X'1D1B000E' HIGH-RBA-------300072959
LOW-CCHH-----X'2A0A0000' LOW-RBA--------300072960 TRACKS--------

...

VOLUME
VOLSER------------PDBDK1 PHYREC-SIZE---------4096 HI-A-RBA------
2632826880 EXTENT-NUMBER---------27
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
2632826880 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:

...

LOW-CCHH-----X'55620000' LOW-RBA-------1394933760 TRACKS--------
-------930
HIGH-CCHH----X'559F000E' HIGH-RBA------1440645119
LOW-CCHH-----X'6ADB0000' LOW-RBA-------1440645120 TRACKS--------
-------945
HIGH-CCHH----X'6B19000E' HIGH-RBA------1487093759
LOW-CCHH-----X'6D440000' LOW-RBA-------1487093760 TRACKS--------
-------960
HIGH-CCHH----X'6D83000E' HIGH-RBA------1534279679
LOW-CCHH-----X'7CB50000' LOW-RBA-------1534279680 TRACKS--------
-----12525
HIGH-CCHH----X'7FF7000E' HIGH-RBA------2149908479
LOW-CCHH-----X'66010000' LOW-RBA-------2149908480 TRACKS--------
-------165

...

VOLUME
VOLSER------------PDBDJ2 PHYREC-SIZE---------4096 HI-A-RBA------
3949608960 EXTENT-NUMBER---------42
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
3949608960 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:
LOW-CCHH-----X'7DBB0000' LOW-RBA-------2632826880 TRACKS--------
------7875
HIGH-CCHH----X'7FC7000E' HIGH-RBA------3019898879
LOW-CCHH-----X'69810000' LOW-RBA-------3019898880 TRACKS--------

...

------1260
HIGH-CCHH----X'69D4000E' HIGH-RBA------3081830399
LOW-CCHH-----X'6AC40000' LOW-RBA-------3081830400 TRACKS--------
-------105
HIGH-CCHH----X'6ACA000E' HIGH-RBA------3086991359
LOW-CCHH-----X'64960000' LOW-RBA-------3086991360 TRACKS--------
-------975
HIGH-CCHH----X'64D6000E' HIGH-RBA------3134914559
LOW-CCHH-----X'6ACB0000' LOW-RBA-------3134914560 TRACKS--------
-------405
HIGH-CCHH----X'6AE5000E' HIGH-RBA------3154821119
LOW-CCHH-----X'4C7F0000' LOW-RBA-------3154821120 TRACKS--------
-------945

...

VOLUME
VOLSER------------PDBDN6 PHYREC-SIZE---------4096 HI-A-RBA------
4294656000 EXTENT-NUMBER----------3
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
4293906432 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:
LOW-CCHH-----X'1ED70000' LOW-RBA-------3949608960 TRACKS--------
------4725
HIGH-CCHH----X'2011000E' HIGH-RBA------4181852159
LOW-CCHH-----X'20CB0000' LOW-RBA-------4181852160 TRACKS--------
------1605
HIGH-CCHH----X'2135000E' HIGH-RBA------4260741119
LOW-CCHH-----X'0CED0000' LOW-RBA-------4260741120 TRACKS--------
-------690
HIGH-CCHH----X'0D1A000E' HIGH-RBA------4294655999





-----End Original Message-----


The Royal Bank of Scotland plc. Registered in Scotland No 83026. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. The Royal Bank of Scotland is authorised by the Prudential Regulation Authority, and regulated by the Financial Conduct Authority and Prudential Regulation Authority. The Royal Bank of Scotland N.V. is authorised and regulated by the De Nederlandsche Bank and has its seat at Amsterdam, the Netherlands, and is registered in the Commercial Register under number 33002587. Registered Office: Gustav Mahlerlaan 350, Amsterdam, The Netherlands. The Royal Bank of Scotland N.V. and The Royal Bank of Scotland plc are authorised to act as agent for each other in certain jurisdictions.



National Westminster Bank Plc. Registered in England No. 929027. Registered Office: 250 Bishopsgate, London EC2M 4AA. National Westminster Bank Plc is authorised by the Prudential Regulation Authority, and regulated by the Financial Conduct Authority and the Prudential Regulation Authority.



The Royal Bank of Scotland plc and National Westminster Bank Plc are authorised to act as agent for each other.



This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc, The Royal Bank of Scotland N.V., National Westminster Bank Plc or any affiliated entity (RBS or us) does not accept responsibility for changes made to this message after it was sent. RBS may monitor e-mails for business and operational purposes. By replying to this message you understand that the content of your message may be monitored.



Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by RBS in this regard and the recipient should carry out such virus and other checks as it considers appropriate.



Visit our website at www.rbs.com http://www.rbs.com

-----End Original Message-----

Attachments

  • smime.p7s (5.1k)

Raymond Bell

[DB2 ZOS DSN11015] Getting less extent for DB2 VSAM
(in response to Roy Boxwell)
DSN1COPY? I laugh in the face of DSN1COPY!

It’s mother was a hamster and its father smelled of elderberries.

Cheers,


Raymond
RIP Terry Jones.

From: Boxwell, Roy <[login to unmask email]>
Sent: 23 January 2020 10:58
To: [login to unmask email]
Subject: [DB2-L] - RE: [DB2 ZOS DSN11015] Getting less extent for DB2 VSAM

I will just mention one tiny problem with the global -1 -1 settings

If you are using DSN1COPY to move data around then you can actually have a problem due to the space allocation being incorrect. I small problem but one you need to be aware of... SECQTY -1 every time!!!

Roy Boxwell

SOFTWARE ENGINEERING GmbH and SEGUS Inc.
-Product Development-

Vagedesstrasse 19
40479 Dusseldorf/Germany
Tel. +49 (0)211 96149-675
Fax +49 (0)211 96149-32
Email: [login to unmask email]<mailto:[login to unmask email]>
Web http://www.seg.de http://www.seg.de
Link zur Datenschutzerklärung https://www.seg.de/corporate/rechtliche-hinweise/datenschutz

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

From: Bell, Raymond (Hosting Services, Technology) [mailto:[login to unmask email]
Sent: Thursday, January 23, 2020 11:25 AM
To: [login to unmask email]<mailto:[login to unmask email]>
Subject: [DB2-L] - RE: [DB2 ZOS DSN11015] Getting less extent for DB2 VSAM

If it bothers you, Sam, just alter the PRIQTY and SECQTY to -1 each, do a quick Reorg and let Db2 worry about it. Extents aren’t a big deal these days, as Roy alluded. Although I must confess to like seeing ‘low’ numbers for extents. Old habits die hard.

Cheers,


Raymond

From: Boxwell, Roy <[login to unmask email]<mailto:[login to unmask email]>>
Sent: 23 January 2020 10:21
To: [login to unmask email]<mailto:[login to unmask email]>
Subject: [DB2-L] - RE: [DB2 ZOS DSN11015] Getting less extent for DB2 VSAM

The limit of 255 Extents disappeared years ago...

VSAM Extent Constraint Relief in z/OS V1R7

- New support allowed for 123x59 extents (previous limit was 255)

In previous releases, there was a 255-extent limit for VSAM data sets and, for striped VSAM data sets, a limit of 255 extents per stripe. Now, using the VSAM extent constraint removal enhancement, these extent limits are removed for SMS-managed volumes, if the extent constraint removal parameter in the data class is set to Y (yes). For non SMS-managed volumes, the previous extent limits still apply.


A VSAM data set can be expanded to 123 extents per volume. This is unchanged from previous releases.

I bet you are at a z/OS release well above 1.7.... I know of no shops that do not have Extent Constraint relief active!

Roy Boxwell

SOFTWARE ENGINEERING GmbH and SEGUS Inc.
-Product Development-

Vagedesstrasse 19
40479 Dusseldorf/Germany
Tel. +49 (0)211 96149-675
Fax +49 (0)211 96149-32
Email: [login to unmask email]<mailto:[login to unmask email]>
Web http://www.seg.de http://www.seg.de
Link zur Datenschutzerklärung https://www.seg.de/corporate/rechtliche-hinweise/datenschutz

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

From: Sam Bo [mailto:[login to unmask email]
Sent: Thursday, January 23, 2020 11:06 AM
To: [login to unmask email]<mailto:[login to unmask email]>
Subject: [DB2-L] - RE: [DB2 ZOS DSN11015] Getting less extent for DB2 VSAM


Hello Roy, may be you're right. It is unusefull to REORG in this case.

But the limit is 255 extent.

And we use thsi to creatate the table

CREATE TABLESPACE TSPVEXRL
IN DBRL
USING STOGROUP SGRL
PRIQTY 1000
SECQTY 9000

CREATE TABLESPACE TSN973RL
IN DBRL
USING STOGROUP SGRL
PRIQTY 1000
SECQTY 100

In the LISTCAT we can see that



ASSOCIATIONS
CLUSTER--DB2REEL.DSNDBC.DBRL.TSN973RL.I0001.A003
ATTRIBUTES
KEYLEN-----------------0 AVGLRECL---------------0 BUFSPACE------
------8192 CISIZE--------------4096
RKP--------------------0 MAXLRECL---------------0 EXCPEXIT------
----(NULL) CI/CA----------------180
SHROPTNS(3,3) SPEED UNIQUE NOERASE LINEAR
NOWRITECHK UNORDERED REUSE
NONSPANNED
STATISTICS
REC-TOTAL--------------0 SPLITS-CI--------------0 EXCPS---------
---------0

...

ALLOCATION
SPACE-TYPE------CYLINDER HI-A-RBA------4294656000
SPACE-PRI--------------2 HI-U-RBA------4293906432
SPACE-SEC--------------1
VOLUME
VOLSER------------PDBDJ0 PHYREC-SIZE---------4096 HI-A-RBA------
-221921280 EXTENT-NUMBER---------47
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
-221921280 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:
LOW-CCHH-----X'03120000' LOW-RBA----------------0 TRACKS--------
--------30
HIGH-CCHH----X'0313000E' HIGH-RBA---------1474559
LOW-CCHH-----X'03390000' LOW-RBA----------1474560 TRACKS--------
--------75
HIGH-CCHH----X'033D000E' HIGH-RBA---------5160959
LOW-CCHH-----X'05FF0000' LOW-RBA----------5160960 TRACKS--------
--------60

...

VOLSER------------PDBDI3 PHYREC-SIZE---------4096 HI-A-RBA------
1394933760 EXTENT-NUMBER---------44
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
1394933760 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:
LOW-CCHH-----X'11D30000' LOW-RBA--------221921280 TRACKS--------
-------375
HIGH-CCHH----X'11EB000E' HIGH-RBA-------240353279
LOW-CCHH-----X'12DA0000' LOW-RBA--------240353280 TRACKS--------
-------390
HIGH-CCHH----X'12F3000E' HIGH-RBA-------259522559
LOW-CCHH-----X'1CE50000' LOW-RBA--------259522560 TRACKS--------
-------825
HIGH-CCHH----X'1D1B000E' HIGH-RBA-------300072959
LOW-CCHH-----X'2A0A0000' LOW-RBA--------300072960 TRACKS--------

...

VOLUME
VOLSER------------PDBDK1 PHYREC-SIZE---------4096 HI-A-RBA------
2632826880 EXTENT-NUMBER---------27
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
2632826880 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:

...

LOW-CCHH-----X'55620000' LOW-RBA-------1394933760 TRACKS--------
-------930
HIGH-CCHH----X'559F000E' HIGH-RBA------1440645119
LOW-CCHH-----X'6ADB0000' LOW-RBA-------1440645120 TRACKS--------
-------945
HIGH-CCHH----X'6B19000E' HIGH-RBA------1487093759
LOW-CCHH-----X'6D440000' LOW-RBA-------1487093760 TRACKS--------
-------960
HIGH-CCHH----X'6D83000E' HIGH-RBA------1534279679
LOW-CCHH-----X'7CB50000' LOW-RBA-------1534279680 TRACKS--------
-----12525
HIGH-CCHH----X'7FF7000E' HIGH-RBA------2149908479
LOW-CCHH-----X'66010000' LOW-RBA-------2149908480 TRACKS--------
-------165

...

VOLUME
VOLSER------------PDBDJ2 PHYREC-SIZE---------4096 HI-A-RBA------
3949608960 EXTENT-NUMBER---------42
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
3949608960 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:
LOW-CCHH-----X'7DBB0000' LOW-RBA-------2632826880 TRACKS--------
------7875
HIGH-CCHH----X'7FC7000E' HIGH-RBA------3019898879
LOW-CCHH-----X'69810000' LOW-RBA-------3019898880 TRACKS--------

...

------1260
HIGH-CCHH----X'69D4000E' HIGH-RBA------3081830399
LOW-CCHH-----X'6AC40000' LOW-RBA-------3081830400 TRACKS--------
-------105
HIGH-CCHH----X'6ACA000E' HIGH-RBA------3086991359
LOW-CCHH-----X'64960000' LOW-RBA-------3086991360 TRACKS--------
-------975
HIGH-CCHH----X'64D6000E' HIGH-RBA------3134914559
LOW-CCHH-----X'6ACB0000' LOW-RBA-------3134914560 TRACKS--------
-------405
HIGH-CCHH----X'6AE5000E' HIGH-RBA------3154821119
LOW-CCHH-----X'4C7F0000' LOW-RBA-------3154821120 TRACKS--------
-------945

...

VOLUME
VOLSER------------PDBDN6 PHYREC-SIZE---------4096 HI-A-RBA------
4294656000 EXTENT-NUMBER----------3
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
4293906432 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:
LOW-CCHH-----X'1ED70000' LOW-RBA-------3949608960 TRACKS--------
------4725
HIGH-CCHH----X'2011000E' HIGH-RBA------4181852159
LOW-CCHH-----X'20CB0000' LOW-RBA-------4181852160 TRACKS--------
------1605
HIGH-CCHH----X'2135000E' HIGH-RBA------4260741119
LOW-CCHH-----X'0CED0000' LOW-RBA-------4260741120 TRACKS--------
-------690
HIGH-CCHH----X'0D1A000E' HIGH-RBA------4294655999



-----End Original Message-----
The Royal Bank of Scotland plc. Registered in Scotland No 83026. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. The Royal Bank of Scotland is authorised by the Prudential Regulation Authority, and regulated by the Financial Conduct Authority and Prudential Regulation Authority. The Royal Bank of Scotland N.V. is authorised and regulated by the De Nederlandsche Bank and has its seat at Amsterdam, the Netherlands, and is registered in the Commercial Register under number 33002587. Registered Office: Gustav Mahlerlaan 350, Amsterdam, The Netherlands. The Royal Bank of Scotland N.V. and The Royal Bank of Scotland plc are authorised to act as agent for each other in certain jurisdictions.

National Westminster Bank Plc. Registered in England No. 929027. Registered Office: 250 Bishopsgate, London EC2M 4AA. National Westminster Bank Plc is authorised by the Prudential Regulation Authority, and regulated by the Financial Conduct Authority and the Prudential Regulation Authority.

The Royal Bank of Scotland plc and National Westminster Bank Plc are authorised to act as agent for each other.

This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc, The Royal Bank of Scotland N.V., National Westminster Bank Plc or any affiliated entity (RBS or us) does not accept responsibility for changes made to this message after it was sent. RBS may monitor e-mails for business and operational purposes. By replying to this message you understand that the content of your message may be monitored.

Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by RBS in this regard and the recipient should carry out such virus and other checks as it considers appropriate.

Visit our website at www.rbs.com http://www.rbs.com
-----End Original Message-----
The Royal Bank of Scotland plc. Registered in Scotland No 83026. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. The Royal Bank of Scotland is authorised by the Prudential Regulation Authority, and regulated by the Financial Conduct Authority and Prudential Regulation Authority. The Royal Bank of Scotland N.V. is authorised and regulated by the De Nederlandsche Bank and has its seat at Amsterdam, the Netherlands, and is registered in the Commercial Register under number 33002587. Registered Office: Gustav Mahlerlaan 350, Amsterdam, The Netherlands. The Royal Bank of Scotland N.V. and The Royal Bank of Scotland plc are authorised to act as agent for each other in certain jurisdictions.

National Westminster Bank Plc. Registered in England No. 929027. Registered Office: 135 Bishopsgate, London EC2M 3UR. National Westminster Bank Plc is authorised by the Prudential Regulation Authority, and regulated by the Financial Conduct Authority and the Prudential Regulation Authority.

The Royal Bank of Scotland plc and National Westminster Bank Plc are authorised to act as agent for each other.

This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc, The Royal Bank of Scotland N.V., National Westminster Bank Plc or any affiliated entity (RBS or us) does not accept responsibility for changes made to this message after it was sent. RBS may monitor e-mails for business and operational purposes. By replying to this message you understand that the content of your message may be monitored.

Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by RBS in this regard and the recipient should carry out such virus and other checks as it considers appropriate.

Visit our website at www.rbs.com http://www.rbs.com

Sam Bo

RE: [DB2 ZOS DSN11015] Getting less extent for DB2 VSAM
(in response to Roy Boxwell)



In Reply to Roy Boxwell:

The limit of 255 Extents disappeared years ago...



VSAM Extent Constraint Relief in z/OS V1R7

- New support allowed for 123x59 extents (previous limit was 255)

In previous releases, there was a 255-extent limit for VSAM data sets and, for striped VSAM data sets, a limit of 255 extents per stripe. Now, using the VSAM extent constraint removal enhancement, these extent limits are removed for SMS-managed volumes, if the extent constraint removal parameter in the data class is set to Y (yes). For non SMS-managed volumes, the previous extent limits still apply.


A VSAM data set can be expanded to 123 extents per volume. This is unchanged from previous releases.



I bet you are at a z/OS release well above 1.7.... I know of no shops that do not have Extent Constraint relief active!



Roy Boxwell

SOFTWARE ENGINEERING GmbH and SEGUS Inc.
-Product Development-

Vagedesstrasse 19
40479 Dusseldorf/Germany
Tel. +49 (0)211 96149-675
Fax +49 (0)211 96149-32
Email: <mailto:[login to unmask email]> [login to unmask email]
Web http://www.seg.de http://www.seg.de

https://www.seg.de/corporate/rechtliche-hinweise/datenschutz Link zur Datenschutzerklärung


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

Hello,

 

i've just checked the dataclass and the option "Extent Constraint Removal' is set to NO.

I can't anderstand why, but certainly it's a mistake.

I don't think it is not safe to set it to YES. What do you think about it ?

I think i will ste the PRIQTY et SECQTY to -1 to be quiet.

Daniel Luksetich

AW: [DB2 ZOS DSN11015] Getting less extent for DB2 VSAM
(in response to Ruediger Kurtz)
In very rare instances we run out of extents with -1/-1. It is a combination of many things



Really big objects

Fragmented logical DASD

Limit storage group free space

Software products design to prevent a dataset running out of space





Very rare, but possible. I experienced it once in 2019 and adjusted the priqty and secqty to fit better into holes.



Dan



+--------------------------------------+-----------------------------------------------------------+

| Daniel L Luksetich | IBM Certified Advanced Database Administrator – |

| IBM GOLD Consultant | Db2 10.1 for Linux UNIX and Windows |

| IDUG Content Committee Past-Chairman | IBM Certified Database Adminstrator – Db2 11 DBA for z/OS |

| IDUG DB2-L Administrator | IBM Certified System Administrator – Db2 11 for z/OS |

| URL: https://db2expert.com https://db2expert.com | IBM Certified Application Developer – Db2 11 for z/OS |

+--------------------------------------+-----------------------------------------------------------+





From: Kurtz, Rüdiger <[login to unmask email]>
Sent: Thursday, January 23, 2020 4:23 AM
To: '[login to unmask email]' <[login to unmask email]>
Subject: [DB2-L] - AW: [DB2 ZOS DSN11015] Getting less extent for DB2 VSAM



Sam,



you might as well use PRIQTY -1 and SECQTY -1; there’s been some discussion on that very topic here on DB2-L, you may want to search the archives.
We use PRIQTY / SECQTY set to -1, and we have not yet come across any problems.

The limit of 255 extents does no longer apply to each and every shop, you may also want to check the documentation.

Hth

Ruediger



Rüdiger Kurtz
Abteilung Informatik - Betrieb

HUK-COBURG
Bahnhofsplatz
96444 Coburg


Telefon:

09561 96-44148


Telefax:

09561 96-44104


E-Mail:

[login to unmask email] <mailto:[login to unmask email]>


Internet:

www.huk.de http://www.huk.de

_____

HUK-COBURG Haftpflicht-Unterstützungs-Kasse kraftfahrender Beamter Deutschlands a. G. in Coburg
Reg.-Gericht Coburg HRB 100; St.-Nr. 9212/101/00021
Sitz der Gesellschaft: Bahnhofsplatz, 96444 Coburg
Vorsitzender des Aufsichtsrats: Prof. Dr. Heinrich R. Schradin.
Vorstand: Klaus-Jürgen Heitmann (Sprecher), Stefan Gronbach, Dr. Hans Olav Herøy, Dr. Jörg Rheinländer, Sarah Rössler, Daniel Thomas.

_____

Diese Nachricht enthält vertrauliche und/oder rechtlich geschützte Informationen.
Wenn Sie nicht der richtige Adressat sind oder diese Nachricht irrtümlich erhalten haben,
informieren Sie bitte sofort den Absender und vernichten Sie diese Nachricht.
Das unerlaubte Kopieren sowie die unbefugte Weitergabe dieser Nachricht ist nicht gestattet.

This information may contain confidential and/or privileged information.
If you are not the intended recipient (or have received this information in error) please notify the
sender immediately and destroy this information.
Any unauthorized copying, disclosure or distribution of the material in this information is strictly forbidden.

_____

Von: Sam Bo <[login to unmask email] <mailto:[login to unmask email]> >
Gesendet: Donnerstag, 23. Januar 2020 11:06
An: [login to unmask email] <mailto:[login to unmask email]>
Betreff: [DB2-L] - RE: [DB2 ZOS DSN11015] Getting less extent for DB2 VSAM



Hello Roy, may be you're right. It is unusefull to REORG in this case.

But the limit is 255 extent.

And we use thsi to creatate the table

CREATE TABLESPACE TSPVEXRL
IN DBRL
USING STOGROUP SGRL
PRIQTY 1000
SECQTY 9000

CREATE TABLESPACE TSN973RL
IN DBRL
USING STOGROUP SGRL
PRIQTY 1000
SECQTY 100

In the LISTCAT we can see that



ASSOCIATIONS
CLUSTER--DB2REEL.DSNDBC.DBRL.TSN973RL.I0001.A003
ATTRIBUTES
KEYLEN-----------------0 AVGLRECL---------------0 BUFSPACE------
------8192 CISIZE--------------4096
RKP--------------------0 MAXLRECL---------------0 EXCPEXIT------
----(NULL) CI/CA----------------180
SHROPTNS(3,3) SPEED UNIQUE NOERASE LINEAR
NOWRITECHK UNORDERED REUSE
NONSPANNED
STATISTICS
REC-TOTAL--------------0 SPLITS-CI--------------0 EXCPS---------
---------0

...

ALLOCATION
SPACE-TYPE------CYLINDER HI-A-RBA------4294656000
SPACE-PRI--------------2 HI-U-RBA------4293906432
SPACE-SEC--------------1
VOLUME
VOLSER------------PDBDJ0 PHYREC-SIZE---------4096 HI-A-RBA------
-221921280 EXTENT-NUMBER---------47
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
-221921280 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:
LOW-CCHH-----X'03120000' LOW-RBA----------------0 TRACKS--------
--------30
HIGH-CCHH----X'0313000E' HIGH-RBA---------1474559
LOW-CCHH-----X'03390000' LOW-RBA----------1474560 TRACKS--------
--------75
HIGH-CCHH----X'033D000E' HIGH-RBA---------5160959
LOW-CCHH-----X'05FF0000' LOW-RBA----------5160960 TRACKS--------
--------60

...

VOLSER------------PDBDI3 PHYREC-SIZE---------4096 HI-A-RBA------
1394933760 EXTENT-NUMBER---------44
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
1394933760 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:
LOW-CCHH-----X'11D30000' LOW-RBA--------221921280 TRACKS--------
-------375
HIGH-CCHH----X'11EB000E' HIGH-RBA-------240353279
LOW-CCHH-----X'12DA0000' LOW-RBA--------240353280 TRACKS--------
-------390
HIGH-CCHH----X'12F3000E' HIGH-RBA-------259522559
LOW-CCHH-----X'1CE50000' LOW-RBA--------259522560 TRACKS--------
-------825
HIGH-CCHH----X'1D1B000E' HIGH-RBA-------300072959
LOW-CCHH-----X'2A0A0000' LOW-RBA--------300072960 TRACKS--------

...

VOLUME
VOLSER------------PDBDK1 PHYREC-SIZE---------4096 HI-A-RBA------
2632826880 EXTENT-NUMBER---------27
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
2632826880 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:

...

LOW-CCHH-----X'55620000' LOW-RBA-------1394933760 TRACKS--------
-------930
HIGH-CCHH----X'559F000E' HIGH-RBA------1440645119
LOW-CCHH-----X'6ADB0000' LOW-RBA-------1440645120 TRACKS--------
-------945
HIGH-CCHH----X'6B19000E' HIGH-RBA------1487093759
LOW-CCHH-----X'6D440000' LOW-RBA-------1487093760 TRACKS--------
-------960
HIGH-CCHH----X'6D83000E' HIGH-RBA------1534279679
LOW-CCHH-----X'7CB50000' LOW-RBA-------1534279680 TRACKS--------
-----12525
HIGH-CCHH----X'7FF7000E' HIGH-RBA------2149908479
LOW-CCHH-----X'66010000' LOW-RBA-------2149908480 TRACKS--------
-------165

...

VOLUME
VOLSER------------PDBDJ2 PHYREC-SIZE---------4096 HI-A-RBA------
3949608960 EXTENT-NUMBER---------42
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
3949608960 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:
LOW-CCHH-----X'7DBB0000' LOW-RBA-------2632826880 TRACKS--------
------7875
HIGH-CCHH----X'7FC7000E' HIGH-RBA------3019898879
LOW-CCHH-----X'69810000' LOW-RBA-------3019898880 TRACKS--------

...

------1260
HIGH-CCHH----X'69D4000E' HIGH-RBA------3081830399
LOW-CCHH-----X'6AC40000' LOW-RBA-------3081830400 TRACKS--------
-------105
HIGH-CCHH----X'6ACA000E' HIGH-RBA------3086991359
LOW-CCHH-----X'64960000' LOW-RBA-------3086991360 TRACKS--------
-------975
HIGH-CCHH----X'64D6000E' HIGH-RBA------3134914559
LOW-CCHH-----X'6ACB0000' LOW-RBA-------3134914560 TRACKS--------
-------405
HIGH-CCHH----X'6AE5000E' HIGH-RBA------3154821119
LOW-CCHH-----X'4C7F0000' LOW-RBA-------3154821120 TRACKS--------
-------945

...

VOLUME
VOLSER------------PDBDN6 PHYREC-SIZE---------4096 HI-A-RBA------
4294656000 EXTENT-NUMBER----------3
DEVTYPE------X'3010200F' PHYRECS/TRK-----------12 HI-U-RBA------
4293906432 EXTENT-TYPE--------X'40'
VOLFLAG------------PRIME TRACKS/CA-------------15
EXTENTS:
LOW-CCHH-----X'1ED70000' LOW-RBA-------3949608960 TRACKS--------
------4725
HIGH-CCHH----X'2011000E' HIGH-RBA------4181852159
LOW-CCHH-----X'20CB0000' LOW-RBA-------4181852160 TRACKS--------
------1605
HIGH-CCHH----X'2135000E' HIGH-RBA------4260741119
LOW-CCHH-----X'0CED0000' LOW-RBA-------4260741120 TRACKS--------
-------690
HIGH-CCHH----X'0D1A000E' HIGH-RBA------4294655999





-----End Original Message-----



-----End Original Message-----

Attachments

  • image001.png (9.9k)
  • image002.png (14k)
  • image003.png (13.1k)
  • image004.png (11.7k)
  • image005.png (15.3k)
  • image006.png (14.2k)
  • image007.png (7.5k)

Roy Boxwell

[DB2 ZOS DSN11015] Getting less extent for DB2 VSAM
(in response to Sam Bo)
Check with the storage people first... I guess it was once „new and dangerous“ now it is old and quiet!!!

Roy Boxwell
SOFTWARE ENGINEERING GmbH and SEGUS Inc.
-Product Development-
Vagedesstrasse 19
40479 Dusseldorf/Germany
Tel. +49 (0)211 96149-675
Fax +49 (0)211 96149-32
Email: [login to unmask email]
http://www.seg.de
Link zur Datenschutzerklärung https://www.seg.de/corporate/rechtliche-hinweise/datenschutz

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

On 23 Jan 2020, at 14:15, Sam Bo <[login to unmask email]> wrote:




In Reply to Roy Boxwell:

The limit of 255 Extents disappeared years ago...



VSAM Extent Constraint Relief in z/OS V1R7

- New support allowed for 123x59 extents (previous limit was 255)

In previous releases, there was a 255-extent limit for VSAM data sets and, for striped VSAM data sets, a limit of 255 extents per stripe. Now, using the VSAM extent constraint removal enhancement, these extent limits are removed for SMS-managed volumes, if the extent constraint removal parameter in the data class is set to Y (yes). For non SMS-managed volumes, the previous extent limits still apply.


A VSAM data set can be expanded to 123 extents per volume. This is unchanged from previous releases.



I bet you are at a z/OS release well above 1.7.... I know of no shops that do not have Extent Constraint relief active!



Roy Boxwell

SOFTWARE ENGINEERING GmbH and SEGUS Inc.
-Product Development-

Vagedesstrasse 19
40479 Dusseldorf/Germany
Tel. +49 (0)211 96149-675
Fax +49 (0)211 96149-32
Email: <mailto:[login to unmask email]> [login to unmask email]
Web http://www.seg.de http://www.seg.de

https://www.seg.de/corporate/rechtliche-hinweise/datenschutz Link zur Datenschutzerklärung


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

Hello,



i've just checked the dataclass and the option "Extent Constraint Removal' is set to NO.

I can't anderstand why, but certainly it's a mistake.

I don't think it is not safe to set it to YES. What do you think about it ?

I think i will ste the PRIQTY et SECQTY to -1 to be quiet.

-----End Original Message-----

Russell Peters

RE: [DB2 ZOS DSN11015] Getting less extent for DB2 VSAM
(in response to Raymond Bell)

Make sure your zparm MGEXTSZ is set to YES.

Sam Bo

RE: [DB2 ZOS DSN11015] Getting less extent for DB2 VSAM
(in response to Russell Peters)

Hello Russel, please could you explain me why we have to set MGEXTSZ to YES

When i read the documentation, i can see :

https://www.ibm.com/support/knowledgecenter/en/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_mgextsz.html

 

Db2 automatically optimizes the secondary extent allocations of data sets for table spaces and index spaces that have a SECQTY value of greater than zero. When all secondary extents are exhausted for the first data set of a nonpartitioned table space or a nonpartitioned index space that has a SECQTY value of greater than zero, the primary space allocation of each subsequent data set is the larger of the SECQTY setting and the value that is derived from the sliding scale algorithm.

But in my case, i hjave to set PRIQTY and SECQTY to -1.

So what is the point to set MGEXTSZ to YES in this case ?

 

 

 

 

 

 

steen rasmussen

[DB2 ZOS DSN11015] Getting less extent for DB2 VSAM
(in response to Sam Bo)
That is the DB2 sliding scheme so you don’t have to monitor pqty and Saturday - using -1 instead. DB2 will then increase the Saturday for every extent until you hit the VSAM limit

Steen

Sent from my iPhone

> On Jan 30, 2020, at 2:29 PM, Sam Bo <[login to unmask email]> wrote:
>
> Hello Russel, please could you explain me why we have to set MGEXTSZ to YES
>
> When i read the documentation, i can see :
>
> https://www.ibm.com/support/knowledgecenter/en/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_mgextsz.html
>
>
>
> Db2 automatically optimizes the secondary extent allocations of data sets for table spaces and index spaces that have a SECQTY value of greater than zero. When all secondary extents are exhausted for the first data set of a nonpartitioned table space or a nonpartitioned index space that has a SECQTY value of greater than zero, the primary space allocation of each subsequent data set is the larger of the SECQTY setting and the value that is derived from the sliding scale algorithm.
> But in my case, i hjave to set PRIQTY and SECQTY to -1.
>
> So what is the point to set MGEXTSZ to YES in this case ?
>
>
>
>
>
>
>
>
>
>
>
>
>
>
> Site Links: View post online View mailing list online Start new thread via email Unsubscribe from this mailing list Manage your subscription
>
> This email has been sent to: [login to unmask email]
> Try BCV5, the BCV5 Masking Tool, & XDM a rapid Refresh/Clone/TDM Suite for Db2 z & distributed.
> DBARS -Audit,record,& block Db2 accesses to sensitive data real-time, NO audit trace or log required
> http://www.ESAIGroup.com/IDUG
>
>
> Use of this email content is governed by the terms of service at:
> http://www.idug.org/p/cm/ld/fid=2
>

Raymond Bell

[DB2 ZOS DSN11015] Getting less extent for DB2 VSAM
(in response to steen rasmussen)
Sounds like a Zparm I need to fiddle with; my Saturdays could do with being extended. :o)

Cheers,


Raymond

From: steen rasmussen <[login to unmask email]>
Sent: 30 January 2020 14:34
To: [login to unmask email]
Subject: [DB2-L] - RE: [DB2 ZOS DSN11015] Getting less extent for DB2 VSAM


*********************************************
"This is an external email. Do you know who has sent it? Can you be sure that any links and attachments contained within it are safe? If in any doubt, use the Phishing Reporter Button in your Outlook client or forward the email as an attachment to ~ I've Been Phished"
*********************************************
That is the DB2 sliding scheme so you don’t have to monitor pqty and Saturday - using -1 instead. DB2 will then increase the Saturday for every extent until you hit the VSAM limit

Steen
Sent from my iPhone

On Jan 30, 2020, at 2:29 PM, Sam Bo <[login to unmask email]<mailto:[login to unmask email]>> wrote:

Hello Russel, please could you explain me why we have to set MGEXTSZ to YES

When i read the documentation, i can see :

https://www.ibm.com/support/knowledgecenter/en/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_mgextsz.html


Db2 automatically optimizes the secondary extent allocations of data sets for table spaces and index spaces that have a SECQTY value of greater than zero. When all secondary extents are exhausted for the first data set of a nonpartitioned table space or a nonpartitioned index space that has a SECQTY value of greater than zero, the primary space allocation of each subsequent data set is the larger of the SECQTY setting and the value that is derived from the sliding scale algorithm.

But in my case, i hjave to set PRIQTY and SECQTY to -1.

So what is the point to set MGEXTSZ to YES in this case ?













-----End Original Message-----

-----End Original Message-----
The Royal Bank of Scotland plc. Registered in Scotland No 83026. Registered Office: 36 St Andrew Square, Edinburgh EH2 2YB. The Royal Bank of Scotland is authorised by the Prudential Regulation Authority, and regulated by the Financial Conduct Authority and Prudential Regulation Authority. The Royal Bank of Scotland N.V. is authorised and regulated by the De Nederlandsche Bank and has its seat at Amsterdam, the Netherlands, and is registered in the Commercial Register under number 33002587. Registered Office: Gustav Mahlerlaan 350, Amsterdam, The Netherlands. The Royal Bank of Scotland N.V. and The Royal Bank of Scotland plc are authorised to act as agent for each other in certain jurisdictions.

National Westminster Bank Plc. Registered in England No. 929027. Registered Office: 135 Bishopsgate, London EC2M 3UR. National Westminster Bank Plc is authorised by the Prudential Regulation Authority, and regulated by the Financial Conduct Authority and the Prudential Regulation Authority.

The Royal Bank of Scotland plc and National Westminster Bank Plc are authorised to act as agent for each other.

This e-mail message is confidential and for use by the addressee only. If the message is received by anyone other than the addressee, please return the message to the sender by replying to it and then delete the message from your computer. Internet e-mails are not necessarily secure. The Royal Bank of Scotland plc, The Royal Bank of Scotland N.V., National Westminster Bank Plc or any affiliated entity (RBS or us) does not accept responsibility for changes made to this message after it was sent. RBS may monitor e-mails for business and operational purposes. By replying to this message you understand that the content of your message may be monitored.

Whilst all reasonable care has been taken to avoid the transmission of viruses, it is the responsibility of the recipient to ensure that the onward transmission, opening or use of this message and any attachments will not adversely affect its systems or data. No responsibility is accepted by RBS in this regard and the recipient should carry out such virus and other checks as it considers appropriate.

Visit our website at www.rbs.com http://www.rbs.com

Phil Grainger

[DB2 ZOS DSN11015] Getting less extent for DB2 VSAM
(in response to steen rasmussen)
Isn’t autocorrect wonderful :)

Sent from my iPad

On 30 Jan 2020, at 14:33, steen rasmussen <[login to unmask email]> wrote:

 That is the DB2 sliding scheme so you don’t have to monitor pqty and Saturday - using -1 instead. DB2 will then increase the Saturday for every extent until you hit the VSAM limit

Steen

Sent from my iPhone

On Jan 30, 2020, at 2:29 PM, Sam Bo <[login to unmask email]<mailto:[login to unmask email]>> wrote:


Hello Russel, please could you explain me why we have to set MGEXTSZ to YES

When i read the documentation, i can see :

https://www.ibm.com/support/knowledgecenter/en/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_mgextsz.html



Db2 automatically optimizes the secondary extent allocations of data sets for table spaces and index spaces that have a SECQTY value of greater than zero. When all secondary extents are exhausted for the first data set of a nonpartitioned table space or a nonpartitioned index space that has a SECQTY value of greater than zero, the primary space allocation of each subsequent data set is the larger of the SECQTY setting and the value that is derived from the sliding scale algorithm.

But in my case, i hjave to set PRIQTY and SECQTY to -1.

So what is the point to set MGEXTSZ to YES in this case ?













-----End Original Message-----

-----End Original Message-----

steen rasmussen

[DB2 ZOS DSN11015] Getting less extent for DB2 VSAM
(in response to steen rasmussen)
Bloody iPhone spell check - not Saturday but sqty

Steen

Sent from my iPhone

> On Jan 30, 2020, at 2:33 PM, steen rasmussen <[login to unmask email]> wrote:
>
> That is the DB2 sliding scheme so you don’t have to monitor pqty and Saturday - using -1 instead. DB2 will then increase the Saturday for every extent until you hit the VSAM limit
>
> Steen
>
> Sent from my iPhone
>
>> On Jan 30, 2020, at 2:29 PM, Sam Bo <[login to unmask email]> wrote:
>>
>> Hello Russel, please could you explain me why we have to set MGEXTSZ to YES
>>
>> When i read the documentation, i can see :
>>
>> https://www.ibm.com/support/knowledgecenter/en/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_mgextsz.html
>>
>>
>>
>> Db2 automatically optimizes the secondary extent allocations of data sets for table spaces and index spaces that have a SECQTY value of greater than zero. When all secondary extents are exhausted for the first data set of a nonpartitioned table space or a nonpartitioned index space that has a SECQTY value of greater than zero, the primary space allocation of each subsequent data set is the larger of the SECQTY setting and the value that is derived from the sliding scale algorithm.
>> But in my case, i hjave to set PRIQTY and SECQTY to -1.
>>
>> So what is the point to set MGEXTSZ to YES in this case ?
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> -----End Original Message-----
>
> Site Links: View post online View mailing list online Start new thread via email Unsubscribe from this mailing list Manage your subscription
>
> This email has been sent to: [login to unmask email]
> Try BCV5, the BCV5 Masking Tool, & XDM a rapid Refresh/Clone/TDM Suite for Db2 z & distributed.
> DBARS -Audit,record,& block Db2 accesses to sensitive data real-time, NO audit trace or log required
> http://www.ESAIGroup.com/IDUG
>
>
> Use of this email content is governed by the terms of service at:
> http://www.idug.org/p/cm/ld/fid=2
>

Larry Jardine

[DB2 ZOS DSN11015] Getting less extent for DB2 VSAM
(in response to Phil Grainger)
I am definitely in favor of more Saturdays.

Larry Jardine
Database Advisor, Aetna, a CVS Health Company

[CVS]
CONFIDENTIALITY NOTICE: This communication and any attachments may contain confidential and/or privileged information for the use of the designated recipients named above. If you are not the intended recipient, you are hereby notified that you have received this communication in error and that any review, disclosure, dissemination, distribution or copying of it or its contents is prohibited. If you have received this communication in error, please notify the sender immediately by email or telephone and destroy all copies of this communication and any attachments.



Proprietary
From: Phil Grainger <[login to unmask email]>
Sent: Thursday, January 30, 2020 9:44 AM
To: [login to unmask email]
Subject: [EXTERNAL] [DB2-L] - RE: [DB2 ZOS DSN11015] Getting less extent for DB2 VSAM

**** External Email - Use Caution ****
Isn’t autocorrect wonderful :)
Sent from my iPad

On 30 Jan 2020, at 14:33, steen rasmussen <[login to unmask email]<mailto:[login to unmask email]>> wrote:
 That is the DB2 sliding scheme so you don’t have to monitor pqty and Saturday - using -1 instead. DB2 will then increase the Saturday for every extent until you hit the VSAM limit

Steen
Sent from my iPhone

On Jan 30, 2020, at 2:29 PM, Sam Bo <[login to unmask email]<mailto:[login to unmask email]>> wrote:

Hello Russel, please could you explain me why we have to set MGEXTSZ to YES

When i read the documentation, i can see :

https://www.ibm.com/support/knowledgecenter/en/SSEPEK_11.0.0/inst/src/tpc/db2z_ipf_mgextsz.html https://urldefense.proofpoint.com/v2/url?u=https-3A__www.ibm.com_support_knowledgecenter_en_SSEPEK-5F11.0.0_inst_src_tpc_db2z-5Fipf-5Fmgextsz.html&d=DwMFaQ&c=wluqKIiwffOpZ6k5sqMWMBOn0vyYnlulRJmmvOXCFpM&r=wfE0VOZJYg9uIjc5BuTMYexNGrByDwh1giBA3sSm6qo&m=mMHEjHrbxityuOna7DX7MsP8nE6w80LthOxIcMPuO4Y&s=1iTNcMnBkqXxs6Uo8pufvtOWM-sEAjVc_WxGJVnCiyM&e=


Db2 automatically optimizes the secondary extent allocations of data sets for table spaces and index spaces that have a SECQTY value of greater than zero. When all secondary extents are exhausted for the first data set of a nonpartitioned table space or a nonpartitioned index space that has a SECQTY value of greater than zero, the primary space allocation of each subsequent data set is the larger of the SECQTY setting and the value that is derived from the sliding scale algorithm.

But in my case, i hjave to set PRIQTY and SECQTY to -1.

So what is the point to set MGEXTSZ to YES in this case ?













-----End Original Message-----

-----End Original Message-----

-----End Original Message-----

NOTICE TO RECIPIENT OF INFORMATION:
This e-mail may contain confidential or privileged information. If you think you have received this e-mail in error, please advise the sender by reply e-mail and then delete this e-mail immediately.
This e-mail may also contain protected health information (PHI) with information about sensitive medical conditions, including, but not limited to, treatment for substance use disorders, behavioral health, HIV/AIDS, or pregnancy. This type of information may be protected by various federal and/or state laws which prohibit any further disclosure without the express written consent of the person to whom it pertains or as otherwise permitted by law. Any unauthorized further disclosure may be considered a violation of federal and/or state law. A general authorization for the release of medical or other information may NOT be sufficient consent for release of this type of information.
Thank you. Aetna
Attachments

  • image003.png (3.8k)

Russell Peters

RE: [DB2 ZOS DSN11015] Getting less extent for DB2 VSAM
(in response to Sam Bo)

As Steen stated, it lets db2 increase the secondary allocation if secondary extents keep happening. You may not end up with less extents necessarily but since implementing MGEXTSZ years ago I have never had an issue of any tablespace or index running out of room. That used to be a real problem. Funny how those issues would always come up in the middle of the night.