Apologies; haven't read the entire thread. Can I assume you have already tried the FORCE with DFSMSdss COPY command?
z/OS 3.2 DFSMSdss Storage Administration, (SC23-6868-70) p. 339: FORCE specifies that DFSMSdss copy one or more unmovable data sets to a like or unlike device type. Unmovable data sets are those allocated as absolute track (ABSTR) or as unmovable (PSU, POU, DAU, or ISU). The allocation attribute, unmovable or ABSTR, is carried over to the output volume. When copying to like devices, DFSMSdss copies the data sets to the same track locations on the target volume. In this case, FORCE is not required if the target volume uses an indexed VTOC, and the space where the unmovable data set is to reside is available. If any of these conditions is not true, DFSMSdss does not copy any unmovable data sets unless FORCE is specified. In this case, DFSMSdss places the unmovable data sets in any available location. You must specify FORCE when copying unmovable data sets to unlike devices. DFSMSdss places the unmovable data sets in any available location. -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Jon Perryman Sent: Tuesday, December 30, 2025 4:59 PM To: [email protected] Subject: Re: Multi volume dataset copy 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. On Mon, 29 Dec 2025 23:02:25 +0100, Radoslaw Skorupka <[email protected]> wrote: >PSU or POU did not solve issues related to single extent (and contiguous >space). Realize that "unmoveable" does not solve a problem. Instead, it simply guarantees that DFDSS, HSM and other such utilities will only restore the dataset to the same exact extents thus guaranteeing a physical copy or restore will survive intact. On the other hand, logical copy or restore, may or may not be intact. >Personally I would not expect plethora of DSORGs, just single flag used >as warning. Reason: plenty of different requirements and possible new >ones in the future. "unmoveable" is that single flag that makes a dataset device & location dependent in some way for DFDSS but has no effect on OPEN. How to move it is completely dependent upon it's creator. Over the last 20 years, how many new special datasets have been added to the list? My guess is it's extremely small (most likely less than 5). ---------------------------------------------------------------------- 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
