[OT] [DB2 ZOS DSN11015] Getting less extent for DB2 VSAM

Philip Sevetson

[OT] [DB2 ZOS DSN11015] Getting less extent for DB2 VSAM
Second the motion. Also, renaming the thread.


Philip Sevetson
Computer Systems Manager
FISA-OPA
5 Manhattan West
New York, NY 10001
[login to unmask email]<mailto:[login to unmask email]>
212-857-1688 w
917-991-7052 m
212-857-1659 f
[cid:[login to unmask email]

From: Jardine, Lawrence J <[login to unmask email]>
Sent: Thursday, January 30, 2020 10:33 AM
To: [login to unmask email]
Subject: [DB2-L] - RE: [DB2 ZOS DSN11015] Getting less extent for DB2 VSAM

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]<mailto:[login to unmask email]>>
Sent: Thursday, January 30, 2020 9:44 AM
To: [login to unmask email]<mailto:[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

-----End Original Message-----
**This e-mail, including any attachments, may be confidential, privileged, or otherwise legally protected. It is intended only for the addressee. If you received this e-mail in error or from someone who was not authorized to send it to you, do not disseminate, copy, or otherwise use this e-mail or its attachments. Please notify the sender immediately by reply e-mail and delete the e-mail from your system.**
Attachments

  • image001.png (3.3k)