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
