Can't get a trace file written

[jeff44]

We're having trouble getting a trace file on z/os.
Our  config file has   

Code Select Expand


ARS_TRACE_SETTINGS=/etc/ars/trace.settings
ARSSOCK=/var/arspvb/tmp/server.trace
(The arssock line was new and did not seem to have any effect)

Our /etc/ars/trace.settings has:

Code Select Expand


[TRACE]
TRACE_FILE=/var/arspvb/tmp/server.trace
TRACE_LEVELS=ALL=15
APPEND=0
TRACE_FORMAT=TEXT
COMPONENT_LEVEL=777777777777777777777777

We Activated the system trace in the Administrator Client with parameters ALL=3
yet we still never seem to get a server.trace file. We do have a basic arssock.err.
Any ideas?

Thanks!

[jsquizz]

Perms on the directory being written to? I've ran into that a few times using trace on 8.5

[Greg Ira]

The only differences we have on our z/OS system is we have �TRACE� instead of [TRACE].  I know that was required versions ago, not sure if it's still relevant. We also don't have the TRACE_LEVELS= set in trace.settings.

[Ed_Arnold]

A colleague had this write up which I think is still accurate:

https://www.ibm.com/developerworks/community/blogs/e8206aad-10e2-4c49-b00c-fee572815374/entry/cmod_trace?lang=en

There's also the -1 and -2 trace parms - am curious as to why you're not using those?

Ed