Hi,

I'd like to know if any of you knows how to configure traces using ibitrace.fex or edasprof.prf

I know it is possible to activate certain trace components and set their trace options.

I could not find the documentation on this.

Thanks.

This message has been edited. Last edited by: Pascal Bellerose,

Perhaps this will be of help: Server Administration for UNIX, Windows, OpenVMS, i5/OS, and z/OS V7.6.1 > Troubleshooting > Tracing Server Activity

Already read this and it's no use because the configuration tools crashes the http listener. (about to open a case on this)

I need to understand traces components in order to know which traces I can start without to much impact on the system.

For example, If it's possible, I'd like to start a trace that will monitor incoming requests only.

The main reason for this is we have a setup made of Reporting servers connecting to Full Function Servers. We may get an email stating that a Full Function Server's agent crashed. Since edaprint does not show the incoming request, we can't figure out which reporting server sent it.

Sometimes we don't even get an ibisnap. And when we have one, the call stack is useless without the context.

Thanks

Hi Pascal,

For installation and configuration issues, the best channel for assistance would be to open a case with Information Builders' Customer Support Services. The phone number is 1-800-736-6130, or access online at InfoResponse.

Cheers,

Kerry