Question & Answer
Question
Although I am using traceFormat="BASIC" in our server.xml configuration, my z/OS Connect Enterprise Edition (zCEE) trace.log file is unreadable. It is tagged as UTF-8 with T=on, but looks like garbage if I try to view it as UTF-8 or ASCII from =3.17. How can we view the trace file from z/OS or UNIX System Services (USS)?
Answer
This problem happens when the trace.log file is too large for the ISPF editor. When a file that is too large is opened, ISPF will "browse" the file rather than Viewing (or View-ASCII) as shown by the "Browse substituted" text that should be displayed in the view window. The browse cannot handle UTF8 or ASCII and will just print the characters it finds which appear garbled, despite HEX ON showing the correct characters are there.
To view large UTF8 files such as a z/OS Connect EE trace file (or a message file that has grown over a period of time), an alternative solution is required because using the z/OS UNIX Directory List Utility will not work. For example, z/OS Explorer, viascii, or running iconv.
Regards, Chris Carlin
IBM z/OS Connect EE Support
Product Synonym
zCEE
Was this topic helpful?
Document Information
Modified date:
14 February 2023
UID
dwa1505256