Hi John, Yep, your explanation was clear. Simple work-around, and the simple ones are the best. We do something similar here. We have a small subset of our DASD sharable across both LPARs and if we need to share data between them, make a copy of the original data on the shared volumes, then either grab it on the other one or just use it from the shared location.
By the way, if you "really" want to allow your backups to get copied to disk, you can override the 256K block size on your initial dump tape. I tried it just now and it does work with a 27998 block size on the initial dump, to then copy the dump tape to disk. However, I wouldn't recommend it for several reasons. First, in my little, incomplete test, setting the block size to 27998 resulted in almost double the I/Os of leaving it at 256K. Second, CPU time and elapsed time increased. Third, tape utilization decreases due to inter block gaps. Fourth, the solution you came up with is a much more efficient one regarding the restore of the dataset, i.e. you only needed to restore one dataset as opposed to restoring the entire tape volume then extracting one dataset from the copied tape. Have a great day! Rex -----Original Message----- From: IBM Mainframe Discussion List [mailto:[email protected]] On Behalf Of John Dawes Sent: Friday, July 14, 2017 6:10 AM To: [email protected] Subject: Re: COPYING DFDSS TAPE TO DASD USING COPYDUMP - ADR331E Rex, Thanks for the help. I checked. The system default for DFDSS is set at 256K. The reason why I cannot restore the datasets is because the volumes are SMS managed LPAR(A) and the backup is done from another LPAR(B). The SMS configurations are not the same on LPAR A & B. However the disks are visible from both the LPARs. Why is the backup not taken on LPAR(A) pray tell? This is because of CPU constraints. A work around I devised is that I restored the dataset to a new name on LPAR(B) then I did a copy of the dataset to the original name from LPAR(A). Oh! What a tangled web we weave ...... I hope that I was able to explain myself clearly. G'day. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN The information contained in this message is confidential, protected from disclosure and may be legally privileged. If the reader of this message is not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any disclosure, distribution, copying, or any action taken or action omitted in reliance on it, is strictly prohibited and may be unlawful. If you have received this communication in error, please notify us immediately by replying to this message and destroy the material in its entirety, whether in electronic or hard copy format. Thank you. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
