The tables in this section list the information you must collect to identify the cause of problem in an OpenTP1 system.

The information described here is the basic information required to investigate various problems. It can be used to identify the cause of problems not specifically mentioned in 11.2 Troubleshooting procedures.

Tables 11-1 through 11-6 list the information that is needed to identify the cause of a problem. If the remote system is also an OpenTP1 system, collect the information described in the tables both on the affected node and on the remote system node.

Table 11-1 Information required for troubleshooting (for TP1/Server Base, TP1/LiNK, TP1/FS/Direct Access, TP1/FS/Table Access, etc.)

Information to acquire	Remarks
betran.log (OpenTP1 standard output and standard error output destination file) on the affected node	In the UNIX version, information is output to the file specified in $DCDIR/bin/prcout. If no file is specified, information is output to the following files: $DCDIR/spool/prclog1 $DCDIR/spool/prclog2 In the Windows version, acquire the event logs (application log and system log). Also, if the standard output redirecting facility is used, acquire the file specified in the redirect_file_name operand of the system environment definition. If no file is specified, information is output to the following files: %DCDIR%\spool\prclog1 %DCDIR%\spool\prclog2
syslog file on the affected node	Not required when using Windows.
$DCDIR directory information of the affected node	In the UNIX version, execute the following command to acquire information: ls -laR $DCDIR
Files under $DCDIR/spool on the affected node	If you are unable to acquire all of the files under spool for some reason, back up the files in the directory and then acquire the following files: $DCDIR/spool/rpclog* $DCDIR/spool/errlog/errlog* $DCDIR/spool/cmdlog/cmdlog*
Files under $DCDIR/tmp on the affected node	If the prc_current_work_path operand of the system common definition is specified, also acquire the files on this path.
Files under $DCDIR/conf and $DCCONFPATH on the affected node	If $DCUAPCONFPATH is set, also acquire the files under $DCUAPCONFPATH. When acquiring definition files, make sure that you also acquire the user service definition.

You use the dcrasget command to acquire the information. Note, however, that Windows event logs are not acquired by this command; to acquire Windows event logs, follow the procedure described in the documentation for your operating system.

Table 11-2 Information required for troubleshooting (for TP1/Client/P)

Information to acquire	Remarks
Client environment definition file (%WINDIR%\betran.ini)	If the defpath argument is specified for the dc_clt_cltin_s function, acquire the files specified by the argument. When acquiring data from PCs that use the Windows Terminal Service or MetaFrame, %WINDIR% corresponds to the respective user directories under \Documents and Settings\.
dcerr*.trc (error traces) dcuap*.trc (UAP traces) dcsoc*.trc (socket traces) dcmdl*.trc (module traces)	These files are output to the directory specified for DCTRCPATH in the client environment definition. If DCTRCPATH is not specified, they are output to the current directory of the CUP.

Table 11-3 Information required for troubleshooting (for TP1/Client/W)

Information to acquire	Remarks
Client environment definition file (Log in as the user who starts the CUP, and acquire the execution results of the OS's env command.)	If the defpath argument is specified for the dc_clt_cltin_s function, acquire the files specified by the argument.
dcerr*.trc (error traces) dcuap*.trc (UAP traces) dcsoc*.trc (socket traces) dcmdl*.trc (module traces)	These files are output to the directory specified for DCTRCPATH in the client environment definition. If DCTRCPATH is not specified, they are output to the current directory of the CUP.

Table 11-4 Information required for troubleshooting (for TP1/Client/J)

Information to acquire	Remarks
Client environment definition (file names and locations depend on the configuration of the client)	If the deffilename argument is specified for the rpcOpen method, acquire the files specified by the argument.
dcerr*.trc (error traces) dcuap*.trc (UAP traces) dcmtd*.trc (method traces) dcdat*.trc (data traces)	Information is output to the following locations: Error traces: Directory specified by the dcerrtracepath operand (information is output only when dcerrtrace=Y is specified) UAP traces: Directory specified by the dcuaptracepath operand (information is output only when dcuaptrace=Y is specified) Method traces: Directory specified by the dcmethodtracepath operand (information is output only when dcmethodtrace=Y is specified) Data traces: Directory specified by the dcdatatracepath operand (information is output when dcdatatrace=Y is specified)
Debug traces (dcCltxxxxxxxxxxxxx.dmp) (where xxxxxxxxxxxxx is the timestamp of the trace)	This data is output to the TP1clientJ directory in the home directory of the user who executed the CUP (or the user who executed JavaVM).

Table 11-5 Information required for troubleshooting (for TP1/Client for .NET Framework)

Information to acquire	Remarks
Client configuration definition	Acquire application configuration files or machine configuration files (for example CUP.exe.config).
dcerr*.trc (error traces) dcuap*.trc (UAP traces) dcmtd*.trc (method traces) dcdat*.trc (data traces)	This data is output to the following locations: Error traces: the directory specified for the path attribute of the <errTrace> element (if use="true") UAP traces: the directory specified for the path attribute of the <uapTrace> element (if use="true") Method traces: the directory specified for the path attribute of the <methodTrace> element (if use="true") Data traces: the directory specified for the path attribute of the <dataTrace> element (if use="true")
Debug traces (dcCltxxxxxxxxxxxxx.dmp) (where xxxxxxxxxxxxx is the timestamp of the trace)	This data is output to the following locations: When the path attribute of the <debugTrace> element is specified: value-specified-by-path-attribute\Hitachi\OpenTP1\TP1ClientNET When the path attribute of the <debugTrace> element is omitted: C:\Document and Settings\user-name\Application Data\Hitachi\OpenTP1\TP1ClientNET

Table 11-6 Information required for troubleshooting (for TP1/Message Control and TP1/NET/***)

Information to acquire	Remarks
Information listed in Table 11-1	--
The following definitions: MCF manager definition MCF communication configuration definition (common definition and individual definition) MCF application definition	Any storage destinations can be specified for the definitions and files. Although the definition files used online are object files, acquire the definition files before object generation.
System service information definition (files under $DCDIR/lib/sysconf/ with names beginning with mcfu)	--
System service common information definition ($DCDIR/lib/sysconf/mcf)	--
MCF traces ($DCDIR/spool/mcftXXXnn, where XXX is the MCF identifier and nn is a sequentially assigned number)	--

Legend:

-- None.

For details of the information required to troubleshoot errors relating to TP1/Message Queue, TP1/Message Queue - Access, and Message Queue - Operation, see the relevant manual for each program product.