Phil, I can't answer for the emulator-controlled transfer with or without their configured CR/LF option, but I would ask the client what happens if they use the native Windows FTP command to do the transfer in binary to a pre-allocated RECFM=FB,LRECL=80 file or PDS member and then use that file or member as input to the TSO RECEIVE. I have done that myself thousands of times and never had a problem with the RECEIVE on the z/OS side.
I must admit I agree with you, I can't see any scenario where adding CR/LF on a binary transfer makes any sense at all. Peter From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Phil Smith III Sent: Thursday, January 16, 2025 11:24 AM To: [email protected] Subject: File transfer question A customer just had a problem uploading some service we'd released. It was an XMIT file, and they did transfer it as binary F 80, but TSO RECEIVE was failing. After some tinkering and comparing screenshots of the file, they eventually found that they had "the CR/LF option" checked in their emulator, which they called "the Rocket emulator" (I suspect that is/was BlueZone). They sent a screenshot that shows the file transfer options: Binary vs. text, plus checkboxes for Append and CR/LF. My question is: Can you devise a scenario where a binary transfer "with CR/LF" makes sense? I can't even think how it would decide where to put them in--it's just a byte stream! The only linends are whatever the native platform uses, but if it's binary those wouldn't seem to me to be meaningful. And of course a binary file could well have those bytes in the data. Maybe I'm missing something obvious [as usual]? -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
