Ok, yes. Then that is correct and the way I things should be working. My friend is the REDBOOK VSAM Demystified…it has a nice section for each of the two Extended Addressable VS Extended Format.
So, Extended Addressable is typically required to be Extended Format (and therefore SMS), except for non-SMS LDS (apparently) which can be Extended Addressable and non-SMS. So, the 32-byte larger physical block size for extended format data sets still holds true on why we cannot copy between them. 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: Tuesday, September 13, 2022 at 10:50 AM To: IBM-MAIN@LISTSERV.UA.EDU <IBM-MAIN@LISTSERV.UA.EDU> Subject: [EXTERNAL] Re: ADR971E RC 8 Let me rephrase that. The LISTC command on the non-SMS managed VSAM LDS has an attribute of EXT-ADDR, whereas the SMS managed VSAM LDS has both EXT-ADDR and EXTENDED. I had assumed that EXT-ADDR requires EXTENDED. I'm a tad confused. Mark Jacobs Sent from ProtonMail, Swiss-based encrypted email. GPG Public Key - https://api.protonmail.ch/pks/lookup?op=get&search=markjac...@protonmail.com ------- Original Message ------- On Tuesday, September 13th, 2022 at 1:29 PM, Ernesto Figueroa <erfig...@us.ibm.com> wrote: > Hi Mark, as far as I know SMS is a requirement for extended-format data sets. > > If you were able to create a non-SMS extended format, it would indeed be news > to me. > Can you show me how you created them and the catalog entries that reflect > that EA/EF status. > > 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: Tuesday, September 13, 2022 at 9:14 AM > To: IBM-MAIN@LISTSERV.UA.EDU IBM-MAIN@LISTSERV.UA.EDU > > Subject: [EXTERNAL] Re: ADR971E RC 8 > 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://api.protonmail.ch/pks/lookup?op=get&search=markjac...@protonmail.com > > > > > ------- 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://api.protonmail.ch/pks/lookup?op=get&search=markjac...@protonmail.com > > > > ---------------------------------------------------------------------- > > 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 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
