> SAdump never writes short blocks. When it wants to write a block > which is not full, it pads the block with dummy records (which IPCS > knows to ignore). Then I don't understand why the utility used produced a copy significantly smaller than the full dump. Once it was initialized on the full 63000cyls I could see that sadump had successfully completed, so what chance of an I/O error is there? Any utility would not care about the content of a 'short' block padded to full length.
The statistics at the end of the sadump messages were clearly showing that each of the volumes was between 30% and 35% full (they are mod27 and I forgot the real usage number). The copy was terminated after the third volume, is my guess. > SAdump does not support data sets whose stripe count is greater than 1. My bad for using the wrong terminology. Thanks for reminding us about the reasons for using copydump. Barbara ps: IBM was sent this sadump, too. It is 66181,077,724 and has a 'nice' SYSIEFSD Q10 deadlock intermixed with PDSE latch contention. Since I never saw the full sadump, I was unable to determine why Q10 was held and not released, effectively preventing SMSPDSE1 restart. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
