Cross-posting this to MVS-OE as a fup to earlier note. TL;DR is that FTPing a text file back to Windows was getting binary (unreadable) no matter what I'd tried.
Sorta figured this out, mostly: > echo woof > txt > chtag -p txt t ISO8859-1 T=on txt That file transfers fine as *binary*, which makes sense, since it's apparently 8859-1 on disk. I have other files: > chtag -p logs/build.log - untagged T=off logs/build.log .that have to be transferred as ASCII, so apparently they're "native" (EBCDIC, presumably 1047) on disk. The remaining mystery is what's making a random file created via echo (or various other things) be ISO8859-1 instead of native EBCDIC?! From: Phil Smith III <li...@akphs.com> Sent: Monday, October 30, 2023 6:13 PM To: 'ibm-m...@bama.ua.edu' <ibm-m...@bama.ua.edu> Subject: RE: FTP problem Off-list reply pointed out that I meant "z/OS FTP server", not "Windows". Braincheck. I fire up Windows FTP client, do GETs. And yes, I was specifying ASCII. That's what was so weird: it sometimes said 125-Tagged ASCII file translated with current data connection translation table .which is what got me tinkering with chtag. But sometimes it didn't say 'translated', and the resulting file was STILL borked! Annotated: * FTPed file, it was borked. Let's tinker with chtag. > chtag -p gskinterop.txt t ISO8859-1 T=on gskinterop.txt * Hmm, 8859-1, that's weird. OK, let's untag it > chtag -r gskinterop.txt > chtag -p gskinterop.txt - untagged T=off gskinterop.txt * FTPed it again, still borked. Even with explicit ASCII. * Let's tag it explicitly > chtag -t -c ibm-1047 gskinterop.txt > chtag -p gskinterop.txt t IBM-1047 T=on gskinterop.txt * Still borked. I started to think something was going on on the Windows side, so I replaced the file contents with a * before retrying the above. No change: the borked version was full-size, just not translated, apparently. Yes, when I look at it on z/OS it looks fine. Yes I could use scp but that's not how I normally do this. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
