We have very busy z/OS Connect instances and tracing 'all' is not a good option so is there a way to specify the apiRequester?

• IBM z/OS Connect API requester: zosConnectApiRequester=all

Hi Jeff,

You can limit the trace to only API requester by using zosConnectApiRequester=all and leave all other trace specification entries as *=info. You can see more about gathering diagnostic information here Collecting troubleshooting data for z/OS Connect Enterprise Edition (ibm.com)

What is it you're trying to find out by turning on trace?

Mark

Is it possible to isolate the trace to a specific ApiRequester instead of all?

Hi Jeff,

Sadly not and there has been a previous idea on this topic here z/OS Connect EE - Allow enablement of TRACE at | IBM Z Software.

Trace is dynamic though so you could modify the trace specification in the server.xml, issue a modify refresh command to enable it, ensure the API requester ran, and then quickly disable trace again (by removing the trace statement and refreshing the server again).

Alternatively, you could setup a separate server instance with trace enabled that just has the single API requester running in it. They you could target that server for a single request to perform debugging.

What do you want to try and find out about the API requester? Perhaps there is another way to get what you're after.

Mark