Answered, I think: When I try to create a DATACLAS for non-SMS-managed VSAM clusters with extended addressability, ISMF seems to tell me that if the cluster will not be in extended format, the cluster must be a linear dataset. That is, it cannot be, for instance, a KSDS cluster.
-----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Michael Watkins Sent: Tuesday, September 13, 2022 1:14 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ADR971E RC 8 CAUTION: This email originated from outside of the Texas Comptroller's email system. DO NOT click links or open attachments unless you expect them from the sender and know the content is safe. To create a non-SMS-managed VSAM cluster with extended addressability, what is required other than assigning a DATACLAS with column 27 (EXTENDED ADDRESSABILITY) specified as 'YES'? -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Mark Jacobs Sent: Tuesday, September 13, 2022 11:14 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: ADR971E RC 8 CAUTION: This email originated from outside of the Texas Comptroller's email system. DO NOT click links or open attachments unless you expect them from the sender and know the content is safe. I can define an EA/EF VSAM Linear dataset on both SMS and Non-SMS volumes. Both are usable and the catalog entries for both reflect their EA/EF status. Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapi.protonmail.ch%2Fpks%2Flookup%3Fop%3Dget%26search%3Dmarkjacobs%40protonmail.com&data=05%7C01%7Cmichael.watkins%40CPA.TEXAS.GOV%7Cce30a1b17839419bce7908da95b3d94a%7C2055feba299d4d0daa5a73b8b42fef08%7C0%7C0%7C637986896933815126%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjoiV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=9FizR75U%2FUgDbxdeEixQ%2B5ye87wDx7riOJD0d5nBnsw%3D&reserved=0 ------- Original Message ------- On Tuesday, September 13th, 2022 at 12:05 PM, Ernesto Figueroa <erfig...@us.ibm.com> wrote: > Hi Mark, > > The reason ADRDSSU cannot copy/restore non-SMS extended addressable VSAM LDS > data sets to SMS managed extended addressable VSAM LDS is because the non-SMS > EA is not an extended-format data set, which requires it to be SMS. The SMS > EA is extended-format, and therefore it has an additional 32bytes per > physical block. Since the blocks are not the same, we cannot copy/restore > tracks between them. > > I hope this answers your question, > Thanks! > > Ernesto E. Figueroa > DFSMSdss Product Owner > > > > From: IBM Mainframe Discussion List IBM-MAIN@LISTSERV.UA.EDU on behalf > of Mark Jacobs 00000224d287a4b1-dmarc-requ...@listserv.ua.edu > > Date: Monday, September 12, 2022 at 10:55 AM > To: IBM-MAIN@LISTSERV.UA.EDU IBM-MAIN@LISTSERV.UA.EDU > > Subject: [EXTERNAL] ADR971E RC 8 > I got around the problem a different way, but I'd really like to understand > why ADRDSSU won't restore(logically dumped) or copy a non-SMS extended > addressable VSAM LDS dataset to an SMS managed extended addressable VSAM LDS. > Is there something within the physical dataset that's different between it > being SMS managed vs not being SMS managed? > > Mark Jacobs > > Sent from ProtonMail, Swiss-based encrypted email. > > GPG Public Key - > https://gcc02.safelinks.protection.outlook.com/?url=https%3A%2F%2Fapi. > protonmail.ch%2Fpks%2Flookup%3Fop%3Dget%26search%3Dmarkjacobs%40proton > mail.com&data=05%7C01%7Cmichael.watkins%40CPA.TEXAS.GOV%7Ca87ac70e > 107c4a816c2208da95a31004%7C2055feba299d4d0daa5a73b8b42fef08%7C0%7C0%7C > 637986824836113089%7CUnknown%7CTWFpbGZsb3d8eyJWIjoiMC4wLjAwMDAiLCJQIjo > iV2luMzIiLCJBTiI6Ik1haWwiLCJXVCI6Mn0%3D%7C3000%7C%7C%7C&sdata=mJHJ > wSHMqVq4GEqbNCa9wNgSN1HddqdKXNOv9fvvVW0%3D&reserved=0 > > ---------------------------------------------------------------------- > 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
