> Look at Init & Tuning to see the current default. Um. Where/what? I spent a bunch of time in that book this morning and didn't find anything meaningful.
I've sent df output for the filesystem before, but here it is again: df -v . Mounted on Filesystem Avail/Total Files Status /u/vendor (VOLTAGE.VENDOR1.ZFS) 3944722/17244000 4294894937 Available ZFS, Read/Write, Device:62, ACLS=Y File System Owner : S0W1 Automove=Y Client=N Filetag : T=off codeset=0 Aggregate Name : VOLTAGE.VENDOR1.ZFS Does that tell you anything useful? Not sure whether this thickens the plot (hmm, we never use that idiom in the form!) but "touch" doesn't seem to be the same as ">": > rm j* > touch j.bad > touch j.c > touch j.txt chtag -p j* - untagged T=off j.bad - untagged T=off j.c - untagged T=off j.txt > echo banana > j2.txt > chtag -p j* - untagged T=off j.bad - untagged T=off j.c - untagged T=off j.txt t ISO8859-1 T=on j2.txt > Someone mentioned "AUTOCVT" which I suspect has documented this change. Documented where/how? I haven't found it. I don't care about a COBOL program, when > does the tagging by itself. Something is doing this, and it's different from our old 2.4 system. I can't ask IBM because we aren't that kind of customer--we don't have the ability to ask such questions, alas. -----Original Message----- From: IBM Mainframe Discussion List <[email protected]> On Behalf Of Jon Perryman Sent: Wednesday, August 20, 2025 3:03 PM To: [email protected] Subject: Re: USS file tagging question On Wed, 20 Aug 2025 13:20:13 -0400, Phil Smith III <[email protected]> wrote: >Our 3.1 (new) test system is definitely different from the old 2.4 system: >if I do the "echo banana > j.txt" on the 2.4 system, it's untagged; on 3.1, >it's ISO8859-1. You are asking why 3.1 is tagging files ISO8859-1 >I can't find any of those (or at least, none that have a CCSID) in any of our >PARMLIBs. I don't believe it is being set by your filesystem default. I assume you mean PARMLIB(BPXPRM##). If you DF the filesystem where you stored the file, then it will tell you the default for that filesystem. It's extremely unlikely the default is not still NOTEXT as you seen in previous posts. Look at Init & Tuning to see the current default. Most likely is a change in C defaults or LE. Do a touch for a.bad, a.c and a.txt and see how they are tagged. I would hope a.bad does not get tagged because bad is not a valid file type. I suggest writing a cobol program that writes to b.txt. If it's tagged, then most likely LE but this is not definitive although it does give you a starting point for your search. Someone mentioned "AUTOCVT" which I suspect has documented this change. Worse case, ask IBM support. This will certainly be a discussion point with those affected by this change. ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
