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 iWay environments supply a standard client test application called RDAAPP; On MVS, RDAAPP traces are activated by the detection of an IBITRACE DD name. Customer written applications must explicitly code EDACALLBACK methods to activate traces (see the EDAAPP C example which is a sample client application that includes EDACALLBACK trace coding).
When reproducing behavior that needs tracing, generally it may be done via RDAAPP and activating the IBITRACE DD name 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.
A sample of a client configuration file using maximum trace level (TRACE=31) is shown below:
NAME = iWay 7.1 Client Using ODIN
TRACE = 31
;
; The Protocol block is needed to find the started task for TCP/IP.
; For IBM's tcp the default name is TCPIP.
; For Interlink's tcp this is the name of the subsystem (no default).
;
;PROTOCOL = TCP
; BEGIN
; TCP NAME = name
; END
;
NODE = MYSERVE
BEGIN
PROTOCOL = TCP
CLASS = CLIENT
HOST = IP_address_of_host_server
SERVICE = Port_#_server_is_listening_on
END
The server build procedure, gencpgm.com, must be edited to specify your EDAHOME and EDACONF locations.
| iWay Software |