Connect:Direct transfer completes, byte count looks right on our side. Partner opens the file and says zero records. Same process worked Friday.
Encoding? CRLF? They changed something and did not tell us? How do you usually divide the blame?
Hash the file before send and ask them to hash what they landed. If hashes differ, network/process issue. If hashes match, it is their reader (record format, code page, or they are looking at the wrong path).
We had this when they switched to a UTF-8 expect and we still sent EBCDIC without a step to convert. Bytes were there. Their app read garbage and showed empty.
Hashes matched. They were browsing a different inbound folder. Cool cool cool.
You must be signed in to reply to this thread