At my previous life, we were using BMC's IAM VSAM interface. I think IAM could use zEDC. But I was told by then IDP support, that IAM's internal compression was Moe (as in Moe Howard) better than even zEDC.
Regarding coding for PS datasets opened in/out, I think DAF will show how a PS dataset is being opened. We chose to use zEDC compression for new,catlg,delete GDGs because we were very confident that no one was going to process that combination as in/out. And does not the IBM zBNA tool highlight good candidates? We did not want to clutter up our SMS ACS DC routines with too many actions to put certain PS datasets into zEDC compression. But in the end, we did put certain large PS, not opened in/out, datasets in the ACS DC routine. Sent with Proton Mail secure email. On Tuesday, April 16th, 2024 at 1:58 PM, Farley, Peter <[email protected]> wrote: > I could be wrong about VSAM compression here then. Maybe that is all CP > compressed and I misunderstood by what mechanism that is done. We could not > survive here without VSAM compression. Many of our VSAM files are > 4G space > even compressed. > > > I do know we ARE using zEDC based on various internal communications I have > seen. I just do not know the exact details. > > Peter > > From: IBM Mainframe Discussion List [email protected] On Behalf Of > Jousma, David > > Sent: Tuesday, April 16, 2024 1:13 PM > To: [email protected] > Subject: Re: Anyone exploiting ZEDC? > > > Peter, > > > > Interesting. IBM says VSAM does NOT exploit ZEDC. VSAM can be compressed, but > it must all be done on CP, which would be expensive. Within a VSAM LINEAR > dataset used as ZFS, ZFS will engage ZEDC. > > > > Dave Jousma > > Vice President | Director, Technology Engineering > > > > From: IBM Mainframe Discussion List > <[email protected]mailto:[email protected]> on behalf of > Farley, Peter > <[email protected]mailto:[email protected]> > > > Date: Tuesday, April 16, 2024 at 1:10 PM > > To: [email protected]mailto:[email protected] > <[email protected]mailto:[email protected]> > > > Subject: Re: Anyone exploiting ZEDC? > > > > I do not know what criteria the sysprogs here set things up. But we are > successfully using zEDC here especially for our huge VSAM and GDG production > files. > > > > I wish I could tell you more, but the sysprogs here are outsourced and > getting answers from them requires official paperwork and bureaucracy that I > have no business reason to cover. > > > > From: IBM Mainframe Discussion List > <[email protected]mailto:[email protected]> On Behalf Of > Jousma, David > > > > > Sent: Tuesday, April 16, 2024 12:39 PM > > > > To: [email protected]mailto:[email protected] > > > > > Subject: Re: Anyone exploiting ZEDC? > > > > Thank-you for this feedback. I’m starting to feel like this is a half-baked > solution looking for a problem. I know of no way to systematically code for > open for update…. > > > > Dave Jousma > > Vice President | Director, Technology Engineering > > > > From: IBM Mainframe Discussion List > <[email protected]mailto:[email protected]> on behalf of > rpinion865 > <[email protected]mailto:[email protected]> > > > > > Date: Tuesday, April 16, 2024 at 12:29 PM > > > > To: [email protected]mailto:[email protected] > <[email protected]mailto:[email protected]> > > > > > Subject: Re: Anyone exploiting ZEDC? > > > > At a prior life, we got the zEDC cards on a z15, and turned that on for PS > datasets. But like you, we quickly learned that PS datasets opened for in/out > processing (update in place) did not work. As a compromise, we narrowed down > to new PS > > > > At a prior life, we got the zEDC cards on a z15, and turned that on for PS > datasets. But like you, we quickly learned that PS datasets opened for in/out > processing (update in place) did not work. As a compromise, we narrowed down > to new PS GDG datasets. Also we looked at new PS GDG datasets over a certain > size. We picked an arbitrary number of tracks/cylinders to apply the zEDC > compression to. Once we did that, our production job abends disappeared and > we started seeing a reduction in space usage on the storage groups where > these datasets were being allocated on. > > > > Sent with Proton Mail secure email. > > > > > On Tuesday, April 16th, 2024 at 12:16 PM, Jousma, David > <[email protected]mailto:[email protected]> > wrote: > > > Is anyone exploiting ZEDC data compression accelerator in your > > environments? We recently licensed the enablement and are working through > > the issues in our DEV environment. > > > We initially enabled Extended Format/COMPACT ZP, for all DSORG PS datasets, > > but are quickly finding that DFSORT, SAS, ISPF recovery datasets all have > > issues. We’ve turned back off for now. > > > There is no central location in any IBM doc(including recent REDBOOKS) that > > discusses where we can and cannot leverage ZEDC. As it stands now, we had > > to back out, and looking at taking a new approach in our ACS routines > > checking for DSORG=PS, and then if not temp-dataset, or tape assign a DC > > with the right options. > > > What I am wondering is if anyone is further along that can share how they > > rolled out? I really don’t want to have to make the applications teams have > > to “opt-in” by coding a DC in their JCL or other dataset allocations. > > > Dave Jousma > > > Vice President | Director, Technology Engineering > > > > > -- > > This message and any attachments are intended only for the use of the > addressee and may contain information that is privileged and confidential. If > the reader of the message is not the intended recipient or an authorized > representative of the intended recipient, you are hereby notified that any > dissemination of this communication is strictly prohibited. If you have > received this communication in error, please notify us immediately by e-mail > and delete the message and any attachments from your system. > > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to [email protected] with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
