Lenny, I can't recall the issue with XCOM. We run ZPSAVER SYNCSORT. This does not work with EF files, so the sorting falls back to BSAM I believe, and there is a corresponding increase in MIPs. We installed ZPSAVER to save MIPS and EF files throw these savings away. We are talking to SYNCSORT folks. With FIELAID, I found that if I encrypted a VSAM file, and then edited the VSAM file using FIELAID, the updates were not actually saved to the file. After doing a SAVE, and reopening the file, the updates were not there. We are talking to CA FILEAID folks now.
The ISPW issue was not really related to encryption. The issue is related to the sheer number of artifacts that are changing in support of encryption. I created a container with 20,000+ artifacts supporting the IDCAMS DEFINE changes alone. It took hours just to check out the items. Now when I look at my container I can only see a subset of the actual artifacts. The items are all in the PDS library. It is just the ISPW system parm setting is something like 1,000 items for me. I could chop the work into multiple containers. Eventually I will need to manage 100,000+ artifacts for JCL and PROCs. I don't know how I will deal with that just yet. Hope that helps. On Thu, Jan 16, 2020 at 11:42 AM Lennie Dymoke-Bradshaw < lenni...@rsmpartners.com> wrote: > Cameron, > > Sadly I have no dataclas with extended specified and I do not want to have > to produce more dataclas specifications at the moment. > > When you say " We have seen some issues with XCOM, SYNCSORT, FILEAID and > ISPW" could you be more specific please? > > Thanks, > > Lennie Dymoke-Bradshaw | Security Lead | RSM Partners Ltd > Web: www.rsmpartners.com > ‘Dance like no one is watching. Encrypt like everyone is.’ > > -----Original Message----- > From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf > Of Cameron Conacher > Sent: 16 January 2020 16:00 > To: IBM-MAIN@LISTSERV.UA.EDU > Subject: Re: [IBM-MAIN] Creating VSAM data sets with DSNTYPE=EXTREQ > > For IDCAMS DEFINE I added DATACLAS(extended dataclas name) > > For JCL and PROCs I added DATACLAS(...) as well > > If DATACLAS was already specified I just changed the name to an extended > format name > > Don’t get me wrong. You can change the members but you still need to test > and promote. > > We have seen some issues with XCOM, SYNCSORT, FILEAID and ISPW. > > > > Sent from my iPhone > > > On Jan 16, 2020, at 9:48 AM, Lennie Dymoke-Bradshaw < > lenni...@rsmpartners.com> wrote: > > > > I am doing planning for the encryption of application data. I have a > need to encrypt some fairly large numbers of VSAM datasets. > > > > I am trying to develop some tooling to help with the allocation and > > encryption of the VSAM data sets. I need to define replacement data > > sets which are extended format (DSNTYPE=EXTREQ in JCL terms). I can > > allocate new data sets using the following methods, > > > > > > 1. IDCAMS: DEFINE CLUSTER with MODEL pointing at existing cluster. > Using this method I can specify the names of the VSAM index and data > components. However, I cannot see how to specify that I want extended > format. > > 2. IDCAMS: ALLOCATE with LIKE specifying the original cluster name. > Using this method I can specify DSNTYPE(EXTREQ), but I cannot specify the > names of the data and index components. > > 3. IKJEFT01: ALLOCATE with LIKE specifying the original cluster name. > This is identical to option 2 as IDCAMS will be invoking IKJEFT01 to do the > allocation. > > 4. JCL: With this method I can again specify DSNTYPE=EXTREQ, but I > cannot specify the names of the index and data components. > > > > At this stage I do not want to alter the existing SMS ACS routines. Is > there any way I can specify both the data and index component names and > EXTREQ? > > > > Lennie Dymoke-Bradshaw | Security Lead | RSM Partners Ltd > > Web: www.rsmpartners.com<http://www.rsmpartners.com/> > > 'Dance like no one is watching. Encrypt like everyone is.' > > > > > > ---------------------------------------------------------------------- > > For IBM-MAIN subscribe / signoff / archive access instructions, send > > email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, send email > to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > > ---------------------------------------------------------------------- > For IBM-MAIN subscribe / signoff / archive access instructions, > send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
