On 2016-05-22, at 14:31, R.S. wrote: > W dniu 2016-05-20 o 18:33, Paul Gilmartin pisze: >>> >> My quick check for this is (IIRC): >> >> cp -B "//'DSN(MEMBER)'" /dev/fd/1 | cksum >> >> ... at both ends of the transfer and compare the checksums and lengths. >> > I remember how I spent half a day on such problem. > I had to download PTF package then move it from one PC to another, using > pendrive, then upload it to z/OS and do SMPE tasks. > I took a lot of time to recognize the reason is failing pendrive (nota bene > with IBM logo! ;-))) ). It simply changed some bytes within the file with no > CRC32 error or so. It was the last thing on the list of suspects. > Ouch! Do you mean the pendrive reported no error, or that you got the same CRC32 on the originating PC and the destination PC?
Windows is woefully deficient in checksum utilities. One must install one. I use Cygwin. But my suggestion was elliptical. I should have mentioned the need to use TRANSMIT with the OUTDSN option; FTP/SFTP/IND$FILE; then compare checksums; then RECEIVE with the INDSN option. Can TRANSMIT use IND$FILE for the TCP/IP challenged? Can IND$FILE transfer z/OS to z/OS? -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
