Warning: Tracing adds significant overhead and should only be used for application debugging.
The activation of traces will depend on the application tool being used. All environments (UNIX, OS/390, z/OS, OpenVMS, OS/400, and Windows) supply a standard client test application called RDAAPP that supports a "-traceon" command time switch to activate traces. Customer written applications must explicitly code EDACALLBACK methods to activate tracing (see the EDAAPP C example which is a sample client application that includes EDACALLBACK trace coding).
When reproducing a behavior that needs tracing, generally it may be done via RDAAPP and activated with the "-traceon" switch without having to code explicit tracing. The specifics of what to trace when tracing is on is a separate function as described in Configuring Tracing.
| iWay Software |