CLI uses these environment variables to decide whether to collect any CLI trace.
- Minimal tracing without parcel dumps
- Tracing with parcel dumps
- Tracing on a thread basis (Windows platforms only)
COPANOMLOG should be set to the file name in which the user intends to collect the trace. On Windows platforms, the trace file name provided in the COPANOMLOG is appended with a .txt extension.
my_copalog, my_copalog_0001, my_copalog_0002, my_copalog_0003
my_copalog.txt, my_copalog_0001.txt, my_copalog_0002.txt, my_copalog_0003.txt
The COPANOMLOG_SIZE environment variable can change the maximum size of copanomlog. Most operating systems support files up to 2 GB.
- NETRACE = 0: (or environment variable not set) incoming/outgoing parcel dumps are disabled, only minimal tracing enabled.
- NETRACE = 1: incoming/outgoing parcel dumps are enabled. This is the most detailed logging option.
- NETRACE = 3: incoming/outgoing parcel dumps are enabled, timestamps are disabled.
- NETRACE = 5, 9, 17, etc. reserved for future options.
where 3fc0, 3fc1, and 3fc2 are thread IDs.
where 3fc0, 3fc1, and 3fc2 are thread IDs, and 23fc is a process ID.
If data encryption is enabled by applications for a request, then request and response messages printed for that particular request in the trace will be encrypted.
On Windows platforms, the COPANOMLOG file names contain thread IDs. On Non-Windows platforms, the COPANOMLOG file names contain a thread ID and a process ID.
where 3fc0 is a thread ID.
where 3fc0 is a thread ID, and 23fc is a process ID.