Three methods are provided for collecting error information and adjusting facilities: setTraceArray, setDccltextend, and setRpcextend. The value specified in each method takes effect when the method is called. When these methods are called, the values specified in their arguments take effect during execution and remain in effect as long as the instance of the TP1Client class exists (until the rpcClose method is called) or until the same method is called with a different argument value specified.

setTraceArray method

For Java applets, you cannot create a file in its execution environment due to Java security limitations. This makes it impossible to collect error information as trace information in files. In such a case, use the memory trace facility to collect trace information. If you specify a String type array with the setTraceArray method, the TP1Client class stores error information in the specified array. In the event of a Java applet or application error, you can view the contents of the String array with a browser in order to determine the cause of the error and take appropriate action. For details about memory traces, see 2.11.4 Error trace and memory trace.

setDccltextend method

Specifies whether or not you wish to use a facility that depends on the execution environment. You specify whether or not the dc_rpc_get_callers_address function of the SPP in the TP1/Server system is to be used to view the IP address of TP1/Client/J. With Microsoft Internet Explorer 3.0J, you cannot check the local IP in the TP1/Client/J system. In a Windows 95 multi-homed host environment, this operation results in an internal OS error. Therefore, the default is that the local IP is not checked.

setRpcextend method

Specifies functional extension options of RPCs that are issued from TP1/Client/J. To specify multiple extension levels of the RPC facility, specify the disjunction of each value.