On Mon, 25 Aug 2025 19:44:18 -0500, Paul Edwards <[email protected]> wrote:
> I am interested in the "artificial device" described on page 330 here: > > (for use by iebcopy). > > I am actually interested in PDSes, not PDSE Partially related question. I would actually like (like, not need - if necessary I can tie myself down to 3390) to create IEBCOPY unload files that can be restored to (almost) any device - so long as it supports a block size of 6144 bytes. There has been a suggestion that TTRs mean that IEBCOPY files can't be loaded to a different device type. I'm (the pdld author, actually) constructing an artificial IEBCOPY unload, so I am in a position to put one record per track for the TTRs if that would be helpful. I don't mind wasting space if it is restored to a 3390. But ideally IEBCOPY (at least modern versions) would reblock to be optimal for a 3390. I want the MVS 3.8J version of IEBCOPY to handle my files too (I don't care if it is wasteful of track space). Page 44 here: https://publib.boulder.ibm.com/epubs/pdf/dgt2u140.pdf describes a COPYMOD statement which may be helpful. It doesn't exist on MVS 3.8J, but that may be OK. It may mean that if someone on z/OS doesn't like a track-wasting load, they can replace COPY with COPYMOD. Any suggestions on where I stand? Thanks. Paul. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
