Hi,
A few things that come to the top of my head is that the size of PDSEs, Member names and PDSE sharing across the LPAR. Make sure that you allocate the PDSE with version 2. This will give you better performance.
PDSE space: Take care when you allocate in regards to space allocation and the future. If your ELIB is huge (over 4gb) you would have the split the file up. KSDS(with
Extended Addressability) can be over 4gb PDSEs can't be over 4gb.
Member name: PDSE members are limited to 8 characters.
PDSE sharing: make sure that you have
PDSESHARING(EXTENDED) in the SMS definition.
some links:
https://knowledge.broadcom.com/external/article/141081/how-to-convert-from-an-endevor-elib-to-a.html
https://community.broadcom.com/communities/community-home/digestviewer/viewthread?MID=810322
Hope it helps
Richard
Original Message:
Sent: 07-06-2021 02:38 PM
From: Jackie Barnes
Subject: Converting ELIB datasets to PDSE datasets
Happy Tuesday!
We are discussing the possibility of converting our VSAM ELIB datasets to PDSE. I wanted to hear from some of you that have been down this road and what advice you can offer. Did you run into any issues that could save us time? Any regrets? Are you and the development teams you support happy with the conversion?
Thank you in advance for any information you can share.