My guess is the use case is that you have an ASCII text file, with ASCII CR/LF, and you want to upload it as ASCII, but have the CR/LR determine the records. I can think of one example right now: uploading .JSON files. When I’ve used them in Enterprise COBOL, they have to be ASCII.
So the Binary option is because you don’t want it to convert ASCII to EBCDIC, but the CR/LF is because you don’t have fixed length data; it really is a text file. From: IBM Mainframe Discussion List <[email protected]> on behalf of Phil Smith III <[email protected]> Reply-To: IBM Mainframe Discussion List <[email protected]> Date: Thursday, January 16, 2025 at 10:24 AM To: "[email protected]" <[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]? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected]<mailto:[email protected]> with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
