DB2 11 for z/OS - pros and cons of ZPARM of COMPRESS_SPT01

Brian Laube

DB2 11 for z/OS - pros and cons of ZPARM of COMPRESS_SPT01

Enabling compression of SPT01 via the ZPARM of COMPRESS_SPT01 seems like a simple way to reduce the size of the SPT01 dataset for our non-prod DB2 subsystems.

We have several "large" SPT01. But they are not near 64GB. Still... they are large.
Compression seems like a simple way to reduce the dataset size.
And making large stuff smaller is a measure that I work towards. Apparently it saves some money.

But what are the pros and cons of SPT01.
The benefit is reduced dataset size.
Is the "cost" of compression and un-compression noticeable for SPT01 usage? Has anyone measured?

Why not compress SPT01?

I am not considering compression for our PROD DB2 SPT01. They are not large. And they are important. So no need to worry about compression.

Maybe the intent is to ONLY compress SPT01 if it is approaching the 64GB dataset size limit. Otherwise... leave it alone...



Regards,
Brian Laube


STATEMENT OF CONFIDENTIALITY The information contained in this email message and any attachments may be confidential and legally privileged and is intended for the use of the addressee(s) only. If you are not an intended recipient, please: (1) notify me immediately by replying to this message; (2) do not use, disseminate, distribute or reproduce any part of the message or any attachment; and (3) destroy all copies of this message and any attachments.

Jim Tonchick

DB2 11 for z/OS - pros and cons of ZPARM of COMPRESS_SPT01
(in response to Brian Laube)

I compressed SPT01 in all subsystems as soon as the Zparm was made available. My COPY run time and space use dropped 70%. Any time you can get more data into a physical page or bufferpool page you save time. RECOV time at the DR site was also sped up.

-----Original Message-----
From: Brian Laube <[login to unmask email]>
To: DB2-L <[login to unmask email]>
Sent: Thu, Nov 16, 2017 03:20 PM
Subject: [DB2-L] - DB2 11 for z/OS - pros and cons of ZPARM of COMPRESS_SPT01



<div id="AOLMsgPart_2_69073961-25dd-417b-b97e-498558b373d9">
<style scoped="">#AOLMsgPart_2_69073961-25dd-417b-b97e-498558b373d9 td{color: black;} @font-face {font-family:"Cambria Math"; panose-1:2 4 5 3 5 4 6 3 2 4;}@font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;}.aolReplacedBody p.aolmail_MsoNormal,.aolReplacedBody li.aolmail_MsoNormal,.aolReplacedBody div.aolmail_MsoNormal {margin:0in; margin-bottom:.0001pt; font-size:11.0pt; font-family:"Calibri",sans-serif;}.aolReplacedBody a:link,.aolReplacedBody span.aolmail_MsoHyperlink {mso-style-priority:99; color:#0563C1; text-decoration:underline;}.aolReplacedBody a:visited,.aolReplacedBody span.aolmail_MsoHyperlinkFollowed {mso-style-priority:99; color:#954F72; text-decoration:underline;}.aolReplacedBody span.aolmail_EmailStyle17 {mso-style-type:personal-compose; font-family:"Calibri",sans-serif; color:windowtext;}.aolReplacedBody .aolmail_MsoChpDefault {mso-style-type:export-only; font-family:"Calibri",sans-serif;}@page WordSection1 {size:8.5in 11.0in; margin:1.0in 1.0in 1.0in 1.0in;}.aolReplacedBody div.aolmail_WordSection1 {page:WordSection1;}</style><div lang="EN-US" class="aolReplacedBody">
<div class="aolmail_WordSection1">
<p class="aolmail_MsoNormal"> </p>
<p class="aolmail_MsoNormal">Enabling compression of SPT01 via the ZPARM of COMPRESS_SPT01 seems like a simple way to reduce the size of the SPT01 dataset for our non-prod DB2 subsystems.</p>
<p class="aolmail_MsoNormal"> </p>
<p class="aolmail_MsoNormal">We have several “large” SPT01. But they are not near 64GB. Still… they are large.</p>
<p class="aolmail_MsoNormal">Compression seems like a simple way to reduce the dataset size.
</p>
<p class="aolmail_MsoNormal">And making large stuff smaller is a measure that I work towards. Apparently it saves some money.</p>
<p class="aolmail_MsoNormal"> </p>
<p class="aolmail_MsoNormal">But what are the pros and cons of SPT01.</p>
<p class="aolmail_MsoNormal">The benefit is reduced dataset size.</p>
<p class="aolmail_MsoNormal">Is the “cost” of compression and un-compression noticeable for SPT01 usage? Has anyone measured?
</p>
<p class="aolmail_MsoNormal"> </p>
<p class="aolmail_MsoNormal">Why not compress SPT01?</p>
<p class="aolmail_MsoNormal"> </p>
<p class="aolmail_MsoNormal">I am not considering compression for our PROD DB2 SPT01. They are not large. And they are important. So no need to worry about compression.</p>
<p class="aolmail_MsoNormal"> </p>
<p class="aolmail_MsoNormal">Maybe the intent is to ONLY compress SPT01 if it is approaching the 64GB dataset size limit. Otherwise… leave it alone…</p>
<p class="aolmail_MsoNormal"> </p>
<p class="aolmail_MsoNormal"> </p>
<p class="aolmail_MsoNormal"> </p>
<p class="aolmail_MsoNormal">Regards,</p>
<p class="aolmail_MsoNormal">Brian Laube</p>
<p class="aolmail_MsoNormal"> </p>
</div>

<style>#AOLMsgPart_2_69073961-25dd-417b-b97e-498558b373d9 td{color: black;} @font-face {font-family:Calibri; panose-1:2 15 5 2 2 2 4 3 2 4;} .aolReplacedBody p.aolmail_MsoNormal,.aolReplacedBody li.aolmail_MsoNormal,.aolReplacedBody div.aolmail_MsoNormal {margin-top:0cm; margin-right:0cm; margin-bottom:10.0pt; margin-left:0cm; line-height:115%; font-size:11.0pt; font-family:"Calibri",sans-serif;}.aolReplacedBody p.aolmail_msonormal0,.aolReplacedBody li.aolmail_msonormal0,.aolReplacedBody div.aolmail_msonormal0 {mso-style-name:msonormal; margin-right:0cm; margin-left:0cm; font-size:12.0pt; font-family:"Times New Roman",serif;}.aolReplacedBody p.aolmail_msochpdefault,.aolReplacedBody li.aolmail_msochpdefault,.aolReplacedBody div.aolmail_msochpdefault {mso-style-name:msochpdefault; margin-right:0cm; margin-left:0cm; font-size:12.0pt; font-family:"Calibri",sans-serif;}.aolReplacedBody p.aolmail_msopapdefault,.aolReplacedBody li.aolmail_msopapdefault,.aolReplacedBody div.aolmail_msopapdefault {mso-style-name:msopapdefault; margin-right:0cm; margin-bottom:10.0pt; margin-left:0cm; line-height:115%; font-size:12.0pt; font-family:"Times New Roman",serif;}.aolReplacedBody .aolmail_MsoChpDefault {font-size:10.0pt; font-family:"Calibri",sans-serif;}.aolReplacedBody .aolmail_MsoPapDefault {margin-bottom:10.0pt; line-height:115%;}@page WordSection1 {size:612.0pt 792.0pt; margin:72.0pt 72.0pt 72.0pt 72.0pt;}.aolReplacedBody div.aolmail_WordSection1 {page:WordSection1;}</style>
<div class="aolmail_WordSection1">
<p class="aolmail_MsoNormal" style="margin-bottom:0cm;margin-bottom:.0001pt;line-height:normal">
<span lang="EN-US" style="font-family:"Arial",sans-serif"> </span></p>
<p class="aolmail_MsoNormal" style="margin-bottom:0cm;margin-bottom:.0001pt;line-height:normal">
<span lang="EN-US" style="font-family:"Arial",sans-serif">STATEMENT OF CONFIDENTIALITY The information contained in this email message and any attachments may be confidential and legally privileged and is intended for the use of the addressee(s) only. If you
are not an intended recipient, please: (1) notify me immediately by replying to this message; (2) do not use, disseminate, distribute or reproduce any part of the message or any attachment; and (3) destroy all copies of this message and any attachments.</span></p>
</div>

<hr size="1" style="color:#ccc"><div id="aolmail_socfooter" style="font-size:80%"><span style="font-weight:bold">Site Links: </span>
<a target="_blank" rel="noopener noreferrer" href="http://www.idug.org/p/fo/st/?post=183768&anc=p183768#p183768">View post online</a>
<a target="_blank" rel="noopener noreferrer" href="http://www.idug.org/p/fo/si/?topic=19">View mailing list online</a>
<a target="_blank" rel="noopener noreferrer" href="mailto:[login to unmask email]">Start new thread via email</a>
<a target="_blank" rel="noopener noreferrer" href="mailto:[login to unmask email]?Subject=Unsubscribe">Unsubscribe from this mailing list</a>
<a target="_blank" rel="noopener noreferrer" href="http://www.idug.org/p/us/to/">Manage your subscription</a>


This email has been sent to: <a href="mailto:[login to unmask email]">[login to unmask email]</a>
<p>
Setup a data refresh task in less time than it takes to make a cup of coffee + save up to 90% in CPU

ESAi's BCV5 & XDM fast data refresh & Test Data Mgmt products will make you a hero to users. See

<a target="_blank" rel="noopener noreferrer" href="http://www.ESAIGroup.com/idug">http://www.ESAIGroup.com/idug</a>

</p>
<p>
Use of this email content is governed by the terms of service at:
<a target="_blank" rel="noopener noreferrer" href="http://www.idug.org/p/cm/ld/fid=2">http://www.idug.org/p/cm/ld/fid=2</a></p>

</div><hr size="1" style="color:#ccc">

</div>
</div>

Brian Laube

DB2 11 for z/OS - pros and cons of ZPARM of COMPRESS_SPT01
(in response to Jim Tonchick)
HI Jim,
Thank you for your sharing your experience of enabling SPT01 compression with this ZPARM.

Did you compress in your prod DB2 too?

Regards,
Brian


________________________________
Brian Laube | Database Administrator (DB2), Integration Technology Services - DB Services
500 King Street North | Waterloo, Ontario | 500-3B | T. 519 593-8817 Ext. 238817 | M. 519 575-2786
[login to unmask email]<mailto:[login to unmask email]> | manulife.com http://www.manulife.com

IBM Certified Database Administrator - DB2 11 for z/OS
IBM Certified Application Developer - DB2 11 for z/OS

Service Requests for the CDN DBA team must be registered as TASKS in the BTS Service Request Intake tool: Notes://MLILAPP04/85257AAD005BAA60/<notes://MLILAPP04/85257AAD005BAA60/>
Methods for contacting CDN DBAS: see http://centralsharepoint/cdndivis/sharserv/DBA/Pages/ContactMethods.aspx

DB2 for z/OS – documentation and Knowledge Center: http://www.ibm.com/support/knowledgecenter/en/SSEPEK_11.0.0/home/src/tpc/db2z_11_prodhome.html

Upcoming vacation alert for Brian Laube : Aug 11 -19

[cid:[login to unmask email]


From: Jim Tonchick [mailto:[login to unmask email]
Sent: Thursday, November 16, 2017 7:34 PM
To: [login to unmask email]
Subject: [DB2-L] - RE: DB2 11 for z/OS - pros and cons of ZPARM of COMPRESS_SPT01


I compressed SPT01 in all subsystems as soon as the Zparm was made available. My COPY run time and space use dropped 70%. Any time you can get more data into a physical page or bufferpool page you save time. RECOV time at the DR site was also sped up.

-----Original Message-----
From: Brian Laube <[login to unmask email]<mailto:[login to unmask email]>>
To: DB2-L <[login to unmask email]<mailto:[login to unmask email]>>
Sent: Thu, Nov 16, 2017 03:20 PM
Subject: [DB2-L] - DB2 11 for z/OS - pros and cons of ZPARM of COMPRESS_SPT01




Enabling compression of SPT01 via the ZPARM of COMPRESS_SPT01 seems like a simple way to reduce the size of the SPT01 dataset for our non-prod DB2 subsystems.



We have several “large” SPT01. But they are not near 64GB. Still… they are large.

Compression seems like a simple way to reduce the dataset size.

And making large stuff smaller is a measure that I work towards. Apparently it saves some money.



But what are the pros and cons of SPT01.

The benefit is reduced dataset size.

Is the “cost” of compression and un-compression noticeable for SPT01 usage? Has anyone measured?



Why not compress SPT01?



I am not considering compression for our PROD DB2 SPT01. They are not large. And they are important. So no need to worry about compression.



Maybe the intent is to ONLY compress SPT01 if it is approaching the 64GB dataset size limit. Otherwise… leave it alone…







Regards,

Brian Laube





STATEMENT OF CONFIDENTIALITY The information contained in this email message and any attachments may be confidential and legally privileged and is intended for the use of the addressee(s) only. If you are not an intended recipient, please: (1) notify me immediately by replying to this message; (2) do not use, disseminate, distribute or reproduce any part of the message or any attachment; and (3) destroy all copies of this message and any attachments.

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

STATEMENT OF CONFIDENTIALITY The information contained in this email message and any attachments may be confidential and legally privileged and is intended for the use of the addressee(s) only. If you are not an intended recipient, please: (1) notify me immediately by replying to this message; (2) do not use, disseminate, distribute or reproduce any part of the message or any attachment; and (3) destroy all copies of this message and any attachments.
Attachments

  • image001.gif (5k)