OpenTP1 Version 7 Operation

[Contents][Index][Back][Next]

10.8 Information collection when error occurs

The following table lists the information that is collected when an error occurs.

Table 10-2 Information collection when error occurs

Collected information Output information Referencing method Notes
Message log file ($DCDIR/spool/ dclog1, dclog2) Message output from OpenTP1 or a UAP Execute the logcat command. To retain an old message log file, copy its contents before they are lost by using message log file swapping.
Console messages System information output from OpenTP1 Look at the console. Output to a printer and output to the centralized console are OS functions.
Standard output and standard error output during command execution OpenTP1 operation commands' output information and error messages Check the screen used to enter the operation commands. To retain this information, redirect it as required.
Core file (./core) OpenTP1-related process data and stack -- The core file of an OpenTP1-activated process is saved under the server name n#1 in the $DCDIR/spool/save directory. A maximum of three core files can be saved per server. To retain them, they must be copied.
UAP trace Execute the uatdump command.
Shared memory dump file (In Linux: $DCDIR/spool/shmdump[1-3].gz,
$DCDIR/spool/shmdump.XXX#2[1-3].gz;
Other operating systems: $DCDIR/spool/shmdump[1-3].Z
$DCDIR/spool/shmdump.XXX#2[1-3].Z)
Data retained in the shared memory by OpenTP1 -- To retain an old dump file, it must be copied.
MCF dump file ($DCDIR/spool/ mcfdPXXYY)#3 Data related to MCF -- Delete any unnecessary files.
Deadlock and timeout information file ($DCDIR/spool/ dclckinf/file-name)#4 Information about resource wait status Execute the OS's cat or vi command. Any unneeded file must be deleted by executing the lckrminf command or by specifying the lck_deadlock_ info_remove_level operand of the lock service definition.
MCF trace file ($DCDIR/spool/ mcftAXXZZ)#5 MCF trace -- To retain an old MCF trace file, it must be copied.
RPC trace file ($DCDIR/spool/ rpctr1,rpctr2) Text transferred by a UAP using RPC Execute the rpcdump command. A receive text may be output to an RPC trace file before a send text. If the size specified for the RPC trace file is too small, data is quickly overwritten in the file, and an adequate amount of information cannot be accumulated.
UAP trace edit/output file ($DCDIR/spool/ save/server-namen#6.uat) UAP trace Execute the OS's cat or vi command. A maximum of three files can be created per server. To retain them, they must be copied.
OpenTP1 debug information file ($DCDIR/spool/ save/server-namen#6.deb) OpenTP1 internal information -- A maximum of three files can be created per server. To retain them, they must be copied.
XAR event trace information file ($DCDIR/spool/dcxarinf/trace/xarevtr1, xarevtr2) Event trace of the XA resource service Execute the xarevtr
command.
To retain old XAR event trace files, they must be copied.
XAR performance verification trace information file
($DCDIR/spool/dcxarinf/_xr_nnn#7)
Performance verification trace of the XA resource service Execute the prfget and prfed commands. To retain old XAR performance verification trace information files, copy these files.
JNL performance verification trace information file
($DCDIR/spool/dcjnlinf/prfinf/_jl_nnn#7)
Event trace of the journal service Execute the prfget and prfed commands. To retain old JNL performance verification trace information files, copy these files.
LCK performance verification trace information file
($DCDIR/spool/dclckinf/prf/_lk_nnn#7)
Event trace of the lock service Execute the prfget and prfed commands. To retain old LCK performance verification trace information files, copy these files.
MCF performance verification trace information file
($DCDIR/spool/dcmcfinf/_mc_nnn#7)
MCF performance verification trace Execute the prfget and prfed commands. To retain old MCF performance verification trace information files, copy these files.
Process service event trace information file
($DCDIR/spool/dcprcinf/_pr_001, _pr_002, _pr_003)
Event trace of the process service Execute the prfget and prfed commands. To retain old process service event trace information files, copy these files.
FIL event trace information file
($DCDIR/spool/dcfilinf/_fl_001, _fl_002, _fl_003)
Event trace for the OpenTP1 file Execute the prfget and prfed commands. To retain old FIL event trace information files, copy these files.

Legend:

#1
n
Evacuate core file serial number (1-3)
No serial numbers are appended to core files to be output when OpenTP1 is terminated abnormally (that is, when the dcsvstop -df command or prckill command is executed or a real-time monitoring timeout error occurs).

#2
XXX: Resource manager name (dam, tam, ist, ism)

#3
PXXYY:
P: One of the following as the type of process from which the dump file was output:
m: MCF manager process
c: MCF communication service or MCF application start service
u: User service, etc.
XX: MCF communication process identifier specified in the -s option of the mcftenv definition command of the MCF communication configuration definition
YY: File serial number (01-99)

#4
A file name is determined on the basis of the deadlock detection time and date. The length of the file name depends on whether the date consists of one or two digits.
Example:
06: 29: 56 on October 3: Oct3062956
18: 06: 00 on October 10: Oct10180600

#5
AXXZZ:
AXX: MCF identifier
A: MCF manager process identifier specified in the id operand of mcfmenv -m in the MCF manager definition
XX: MCF communication process identifier specified in mcftenv -s in the MCF communication configuration definition
ZZ: Trace swap file identifier

#6
n
File Serial number (1-3)

#7
nnn: Value in the range from 001 to the value specified in the prf_file_count operand in the following definitions:
  • XAR performance verification trace information file: XAR performance verification trace definition
  • JNL performance verification trace information file: JNL performance verification trace definition
  • LCK performance verification trace information file: LCK performance verification trace definition
  • MCF performance verification trace information file: MCF performance verification trace definition