Hi Karen,
No, I do not have any insight into that KB; I avoid ELIBs whenever
possible.
My immediate reaction is to copy it to a PDSE instead. PDSE is now the
recommended format for Delta libs. Do a dry run copying from ELIB to a
'throw-away' PDSE to see how long it'll take.
*Dave Harding *
Client Services Consultant • Mainframe Software Division
Broadcom Software
Mobile 317-403-1740 |
dave.harding@broadcom.comUpcoming vacation:
September 2 - September 10
October 4 - October 8
On Mon, Sep 18, 2023 at 12:06 PM Karen Turner via Broadcom <
Mail@broadcom.com> wrote:
> Long ago and far away JvK added this paragraph to the Elib maintenance KD:
> Note: When dealing with large VSAM ELIBs that are in multiple... -posted
> to the "Endevor" community
> [image: Broadcom] <https: community.broadcom.com="">
> Endevor
> <https: community.broadcom.com/mainframesoftware/communities/community-home/digestviewer?communitykey="592eb6c9-73f7-460f-9aa9-e5194cdafcd2">
> Post New Message <
broadcom-caendevor@connectedcommunity.org>
> Large VSAM ELIB Reorg: REPRO VSAM > BDAM
> <https: community.broadcom.com/mainframesoftware/discussion/large-vsam-elib-reorg-repro-vsam-bdam#bmdae16646-bea3-4d24-81dd-97b8cc1776fd="">
> Reply to Group
> <
broadcom_caendevor_dae16646-bea3-4d24-81dd-97b8cc1776fd@connectedcommunity.org?subject=re:+large+vsam+elib+reorg:+repro+vsam+%3e+bdam> Reply
> to Sender
> <https: community.broadcom.com/mainframesoftware/communities/all-discussions/postreply?messagekey="dae16646-bea3-4d24-81dd-97b8cc1776fd&ListKey=6c02d13b-c28e-4794-b86a-c8b767e00498&SenderKey=434cbcf1-f6ec-4fa2-b1d5-23006686c9e2">
> [image: Karen Turner]
> <https: community.broadcom.com/network/members/profile?userkey="434cbcf1-f6ec-4fa2-b1d5-23006686c9e2">
> Sep 18, 2023 12:06 PM
> Karen Turner
> <https: community.broadcom.com/network/members/profile?userkey="434cbcf1-f6ec-4fa2-b1d5-23006686c9e2">
>
> Long ago and far away JvK added this paragraph to the Elib maintenance KD:
>
> Note: When dealing with large VSAM ELIBs that are in multiple physical
> extents, BC1PNCPY can take a long time to run. Although IDCAMS repro use is
> discouraged as the permanent resolution to your fragmented file it can be
> used as an intermediate step to speed up the BC1PNCPY process, by reducing
> the number of physical extents. So following the advice above: Allocate
> 2 new ELIBs: 1 VSAM and 1 BDAM, ensuring both are large enough to fit the
> existing file into a single extent. Use BC1PNLIB to INIT the VSAM file. Use
> IDCAMS to REPRO the fragmented ELIB to the un-initialized BDAM file, then
> use BC1PNCPY to copy the BDAM ELIB file to the newly initialized VSAM ELIB.
>
> Has anyone done this successfully?
>
> I have a 2000 cyl production delta in 2 vsam extents and 5 elib extents.
> I do not have a 20 hour window to BC1PNCPY it from old VSAM to new VSAM.
>
> Testing with a smaller file I get an error on the VSAM to BDAM repro:
>
> REPRO INFILE(VSAM) OUTFILE(BDAM)
> IDC3300I ERROR OPENING TTAP.END.TPROD.OTHDELTA
> IDC3351I ** VSAM OPEN RETURN CODE IS 118
> IDC3302I ACTION ERROR ON TTAP.END.TPROD.TSTDELTA.BDAM
> IDC3309I ** RECORD X'0000000100' NOT WRITTEN. LENGTH INVALID
> IDC3302I ACTION ERROR ON TTAP.END.TPROD.TSTDELTA.BDAM
> IDC3309I ** RECORD X'0000000200' NOT WRITTEN. LENGTH INVALID
> IDC3302I ACTION ERROR ON TTAP.END.TPROD.TSTDELTA.BDAM
> IDC3309I ** RECORD X'0000000300' NOT WRITTEN. LENGTH INVALID
> IDC3302I ACTION ERROR ON TTAP.END.TPROD.TSTDELTA.BDAM
> IDC3309I ** RECORD X'0000000400' NOT WRITTEN. LENGTH INVALID
> IDC31467I MAXIMUM ERROR LIMIT REACHED.
> IDC0005I NUMBER OF RECORDS PROCESSED WAS 0
> IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12
>
> BDAM JCL:
>
> //BDAMBR14 EXEC PGM=IEFBR14
> //BDAM DD DSN=TTAP.END.TPROD.TSTDELTA.BDAM,DISP=(NEW,CATLG,DELETE),
> // SPACE=(CYL,(10,10)),MGMTCLAS=MCPERMMB,
> // DCB=(RECFM=FBS,LRECL=4096,BLKSIZE=4096,DSORG=DA)
>
> REPRO JCL:
>
> //REPRO EXEC PGM=IDCAMS
> //SYSPRINT DD SYSOUT=*
> //SYSOUT DD SYSOUT=*
> //VSAM DD DSN=TTAP.END.TPROD.OTHDELTA,DISP=OLD
> //BDAM DD DSN=TTAP.END.TPROD.TSTDELTA.BDAM,DISP=OLD
> //SYSIN DD *
> REPRO INFILE(VSAM) OUTFILE(BDAM)
>
> Any insight is greatly appreciated!
>
> Thanks!
>
> kt
>
>
>
> ------------------------------
> Karen Turner
> ------------------------------
> *Reply to Group Online
> <https: community.broadcom.com/mainframesoftware/communities/all-discussions/postreply?messagekey="dae16646-bea3-4d24-81dd-97b8cc1776fd&ListKey=6c02d13b-c28e-4794-b86a-c8b767e00498">*
> *Reply to Group via Email
> <
broadcom_caendevor_dae16646-bea3-4d24-81dd-97b8cc1776fd@connectedcommunity.org?subject=re:+large+vsam+elib+reorg:+repro+vsam+%3e+bdam>*
> *View Thread
> <https: community.broadcom.com/mainframesoftware/discussion/large-vsam-elib-reorg-repro-vsam-bdam#bmdae16646-bea3-4d24-81dd-97b8cc1776fd="">*
> *Recommend
> <https: community.broadcom.com:443/mainframesoftware/discussion/large-vsam-elib-reorg-repro-vsam-bdam?messagekey="dae16646-bea3-4d24-81dd-97b8cc1776fd&cmd=rate&cmdarg=add#bmdae16646-bea3-4d24-81dd-97b8cc1776fd">*
> *Forward
> <https: community.broadcom.com/mainframesoftware/communities/all-discussions/forwardmessages?messagekey="dae16646-bea3-4d24-81dd-97b8cc1776fd&ListKey=6c02d13b-c28e-4794-b86a-c8b767e00498">*
> *Flag as Inappropriate
> <https: community.broadcom.com/mainframesoftware/discussion/large-vsam-elib-reorg-repro-vsam-bdam?markappropriate="dae16646-bea3-4d24-81dd-97b8cc1776fd#bmdae16646-bea3-4d24-81dd-97b8cc1776fd">*
>
>
>
>
> You are subscribed to "Endevor" as
dave.harding@broadcom.com. To change
> your subscriptions, go to My Subscriptions
> <http: community.broadcom.com/preferences?section="Subscriptions">. To
> unsubscribe from this community discussion, go to Unsubscribe
> <http: community.broadcom.com/higherlogic/egroups/unsubscribe.aspx?userkey="f0102c8e-2c1c-47ba-9f18-e9e6816f2ae3&sKey=KeyRemoved&GroupKey=6c02d13b-c28e-4794-b86a-c8b767e00498">.
>
>
> Copyright © 2005-2023 Broadcom. All Rights Reserved. The term "Broadcom"
> refers to Broadcom Inc. and/or its subsidiaries.
>
> Hosted by Higher Logic, LLC on the behalf of Broadcom - Privacy Policy
> <https:
www.broadcom.com/company/legal/privacy-policy=""> | Cookie Policy
> <https:
www.higherlogic.com/legal/privacy=""> | Supply Chain Transparency
> <https:
www.broadcom.com/company/citizenship/governance-and-ethics#supply="">> | Terms of Use <http: termsandconditions="">
>
--
This electronic communication and the information and any files transmitted
with it, or attached to it, are confidential and are intended solely for
the use of the individual or entity to whom it is addressed and may contain
information that is confidential, legally privileged, protected by privacy
laws, or otherwise restricted from disclosure to anyone else. If you are
not the intended recipient or the person responsible for delivering the
e-mail to the intended recipient, you are hereby notified that any use,
copying, distributing, dissemination, forwarding, printing, or copying of
this e-mail is strictly prohibited. If you received this e-mail in error,
please return the e-mail to the sender, delete it from your computer, and
destroy any printed copy of it.
Original Message:
Sent: 9/18/2023 12:06:00 PM
From: Karen Turner
Subject: Large VSAM ELIB Reorg: REPRO VSAM > BDAM
Long ago and far away JvK added this paragraph to the Elib maintenance KD:
Note: When dealing with large VSAM ELIBs that are in multiple physical extents, BC1PNCPY can take a long time to run. Although IDCAMS repro use is discouraged as the permanent resolution to your fragmented file it can be used as an intermediate step to speed up the BC1PNCPY process, by reducing the number of physical extents. So following the advice above: Allocate 2 new ELIBs: 1 VSAM and 1 BDAM, ensuring both are large enough to fit the existing file into a single extent. Use BC1PNLIB to INIT the VSAM file. Use IDCAMS to REPRO the fragmented ELIB to the un-initialized BDAM file, then use BC1PNCPY to copy the BDAM ELIB file to the newly initialized VSAM ELIB.
Has anyone done this successfully?
I have a 2000 cyl production delta in 2 vsam extents and 5 elib extents. I do not have a 20 hour window to BC1PNCPY it from old VSAM to new VSAM.
Testing with a smaller file I get an error on the VSAM to BDAM repro:
REPRO INFILE(VSAM) OUTFILE(BDAM)
IDC3300I ERROR OPENING TTAP.END.TPROD.OTHDELTA
IDC3351I ** VSAM OPEN RETURN CODE IS 118
IDC3302I ACTION ERROR ON TTAP.END.TPROD.TSTDELTA.BDAM
IDC3309I ** RECORD X'0000000100' NOT WRITTEN. LENGTH INVALID
IDC3302I ACTION ERROR ON TTAP.END.TPROD.TSTDELTA.BDAM
IDC3309I ** RECORD X'0000000200' NOT WRITTEN. LENGTH INVALID
IDC3302I ACTION ERROR ON TTAP.END.TPROD.TSTDELTA.BDAM
IDC3309I ** RECORD X'0000000300' NOT WRITTEN. LENGTH INVALID
IDC3302I ACTION ERROR ON TTAP.END.TPROD.TSTDELTA.BDAM
IDC3309I ** RECORD X'0000000400' NOT WRITTEN. LENGTH INVALID
IDC31467I MAXIMUM ERROR LIMIT REACHED.
IDC0005I NUMBER OF RECORDS PROCESSED WAS 0
IDC3003I FUNCTION TERMINATED. CONDITION CODE IS 12
BDAM JCL:
//BDAMBR14 EXEC PGM=IEFBR14
//BDAM DD DSN=TTAP.END.TPROD.TSTDELTA.BDAM,DISP=(NEW,CATLG,DELETE),
// SPACE=(CYL,(10,10)),MGMTCLAS=MCPERMMB,
// DCB=(RECFM=FBS,LRECL=4096,BLKSIZE=4096,DSORG=DA)
REPRO JCL:
//REPRO EXEC PGM=IDCAMS
//SYSPRINT DD SYSOUT=*
//SYSOUT DD SYSOUT=*
//VSAM DD DSN=TTAP.END.TPROD.OTHDELTA,DISP=OLD
//BDAM DD DSN=TTAP.END.TPROD.TSTDELTA.BDAM,DISP=OLD
//SYSIN DD *
REPRO INFILE(VSAM) OUTFILE(BDAM)
Any insight is greatly appreciated!
Thanks!
kt
------------------------------
Karen Turner
------------------------------
</http:></https:></https:></https:></http:></http:></https:></https:></https:></https:></broadcom_caendevor_dae16646-bea3-4d24-81dd-97b8cc1776fd@connectedcommunity.org?subject=re:+large+vsam+elib+reorg:+repro+vsam+%3e+bdam></https:></https:></https:></https:></broadcom_caendevor_dae16646-bea3-4d24-81dd-97b8cc1776fd@connectedcommunity.org?subject=re:+large+vsam+elib+reorg:+repro+vsam+%3e+bdam></https:></broadcom-caendevor@connectedcommunity.org></https:></https:>