I'm trying to NOT have files that *are* EBCDIC tagged wrong, so FTP works. If I FTP that "banana" file, I get untranslated EBCDIC. If I say TYPE E, I get an error saying "Dude, that's ASCII, use ASCII".
This manifested with Python scripts in our automation that did FTPs and got errors saying "record too long" from larger files, presumably because it was transferring as ASCII/binary and thus looking for linends that just aren't there in the EBCDIC data. -----Original Message----- From: IBM Mainframe Discussion List <IBM-MAIN@LISTSERV.UA.EDU> On Behalf Of Jon Perryman Sent: Wednesday, August 20, 2025 1:17 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: USS file tagging question On Wed, 20 Aug 2025 12:25:20 -0400, Phil Smith III <li...@akphs.com> wrote: >> export _BPXK_AUTOCVT=OFF >> chtag -p j* >t ISO8859-1 T=on j.txt > >So setting that OFF doesn't seem to help? >I'm still missing something...? Auto-conversion off defines when automatic file conversion will be bypassed. This has nothing to do with changing filetag. You can clear the filetag but why would you want to disable or lock chtag for a session or specific file? ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
