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](https://protonmail.com ), 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
