After further research I see that the 'corruption' is the insertion of carriage control characters. This is being done by SDSF when using line command XDC, even if the correct data set attributes are specified for the output data set.
Instead, I created an appropriate data set, allocated it to some DD in my TSO session, then used SDSF's XFC line command and pointed to that DD. This copies it as is, without carriage control characters. Now it is usable. Thanks Wayne and Ed. Don Imbriale -- On Tue, 11 Sep 2007 09:47:45 -0700, Edward Jaffe <[EMAIL PROTECTED]> wrote: >Imbriale, Donald wrote: >> Thanks Wayne. I had searched the archives. My tests show that SYSMDUMP >> directed to SYSOUT, then copied to a dataset (via SDSF for example), >> results in a partially corrupted SYSMDUMP. >> > >I look at many such dumps and have never experienced any corruption >using this technique. The dump on spool will be byte-for-byte exactly >correct. When copying to DASD for IPCS use, you need to use a tool that >will not change the contents of the data. And, you must copy it to a >RECFM=FBS data set. > >-- ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
