The following files must be created by users:

• User program files
  Such files store execution form UAPs.
  
• MCF communication process program file and MCF application startup process program file
  These files store the executable programs of the MCF communication process and the MCF application startup process that you create to use the message control facility.
  
• Various definition files
  Such files store various types of OpenTP1 definition information. The OS text editor must be used to create a definition file as a text file.
  

The files list above are created under user-created directories. The $DCDIR/aplib and $DCDIR/conf directories are created during OpenTP1 installation.

The following table lists the files and directories that are created by users.

Table 1-4 User-created files and directories

Name		Directory	File name	File type
User program file		$DCDIR/aplib/#1	Name of execution form program#2	Execution form file
MCF communication process program file and MCF application startup process program file		$DCDIR/lib/servers/	Name of the executable program	Executable file
Definition files	System environment definition	$DCDIR/conf/	env	Text file
	Definitions other than system environment definition	$DCCONFPATH/	Name of definition file	Text file
	System service information definition file	$DCDIR/lib/sysconf/	Name of system service information definition file	Text file
	System service common information definition#3	$DCDIR/lib/sysconf/	mcf	Text file

#1

Can be changed by the process service definition.

#2

Can be changed by the user service definition.

#3

This file is created when OpenTP1 is installed or registered into the OS. However, you need to change the contents of the definition depending on the operation environment.

The files listed below must be created during installation.

• OpenTP1 program files
  These files store OpenTP1 programs.
  The two types of files are OpenTP1 execution form files and the files used to create UAPs.
  
  • OpenTP1 execution form files
    System services and commands
    
  • Files used to create UAPs
    Header files and archive files
    
• Definition analysis file
  This file is used internally by OpenTP1 to analyze definitions.
  
• Message object file
  This file stores message texts.
  

The files listed above are created under directories created by OpenTP1.

The directories that are created when OpenTP1 is installed or cataloged into the OS are:

• User program file directory
  This directory stores user program files.
  
• Definition file directory
  This directory stores various OpenTP1 definition information files.
  
• System management information directory
  This directory stores system management information.
  
• Core file directory
  This directory stores core files.
  
• Command log directory
  This directory stores command log files.
  
• Deadlock information file directory
  This directory stores deadlock information and timeout information files.
  
• Transaction information directory
  This directory stores transaction information.
  
• Transaction journal directory
  This directory stores transaction journal information.
  
• Process service information directory
  This directory stores process service information.
  
• Journal information directory
  This directory stores journal information.
  
• Server recovery journal directory
  This directory stores server recovery journal information.
  
• Directory for storing transaction control objects
  This directory stores transaction control object files.
  
• Directory for online testers
  This directory stores files that are used by the online tester.
  
• Directory for system internal lock control
  This directory stores information for OpenTP1 internal lock control.
  
• Directory for system internal synchronization control
  This directory stores information for OpenTP1 internal synchronization control.
  

The following table lists the files and directories that are created when OpenTP1 is installed or cataloged into the OS.

Table 1-5 Files and directories created at installation or cataloging into OS

Name		Directory	File name
OpenTP1 program file	OpenTP1 servers	$DCDIR/lib/servers/	--#
	Commands	$DCDIR/bin/	--
	Header file	$DCDIR/include/	--
	Archive file	$DCDIR/lib/	--
Definition analysis file		$DCDIR/lib/sysconf/	--#
		$DCDIR/lib/sysdef/	--
Message object file		$DCDIR/lib/	emsgtxt, jmsgtxt
User program file directory		$DCDIR/aplib/	None
Definition file directory		$DCDIR/conf/	None
System management information directory		$DCDIR/etc	--
Core file directory		$DCDIR/spool/save/	None
Command log directory		$DCDIR/spool/cmdlog/	--
Deadlock information file directory		$DCDIR/spool/dclckinf/	None
Transaction information directory		$DCDIR/spool/dctrninf/	None
Journal information directory		$DCDIR/spool/dcjnlinf/errinf/	None
Process service information directory		$DCDIR/spool/dcprcinf/	None
Transaction journal directory		$DCDIR/spool/dctjlinf/	--
Server recovery journal directory		$DCDIR/spool/dcsjl/	--
Directory for storing transaction control objects		$DCDIR/spool/trnrmcmd/userobj/	None
Directory for online testers		$DCDIR/spool/uto/	None
Directory for system internal lock control		$DCDIR/spool/olkfifs/	--
Directory for system internal synchronization control		$DCDIR/spool/olkrsfs/	--

Legend:

--: Need not be specified by the user.

#

The file needs to be created when you use the MCF.

The files listed below are created dynamically by OpenTP1 during online execution.

(a) Files created during normal operation

The files listed below are created during normal OpenTP1 operation.

• Message log file
  This file stores system messages issued by OpenTP1.
  
• MCF trace file
  This file stores TP1/Message Control trace information.
  
• Scheduling queue information file
  This file is used internally by OpenTP1 to store scheduling queue information.
  
• RPC trace file
  This file stores RPC trace information.
  
• Trace information dump file
  This file stores OpenTP1 internal trace information.
  
• Performance verification trace information file
  The file stores trace information for verification.
  
• Backup file for performance verification trace information file
  This file serves as a backup of the performance verification trace information file.
  
• XAR performance verification trace information file
  This file stores trace information for events linked to transactions that use the XA resource service (transaction requests from application servers and transaction processing by OpenTP1).
  
• Backup file for XAR performance verification trace information file
  This file serves as a backup of the XAR performance verification trace information file.
  
• JNL performance verification trace information file
  This file stores trace information for the journal service.
  
• Backup file for JNL performance verification trace information file
  This file serves as a backup of the JNL performance verification trace information file.
  
• LCK performance verification trace information file
  This file stores trace information for various lock events that use the lock service.
  
• Backup file for LCK performance verification trace information file
  This file serves as a backup of the LCK performance verification trace information file.
  
• MCF performance verification trace information file
  This file stores trace information for MCF performance verification.
  
• Backup file for MCF performance verification trace information file
  This file serves as a backup of the MCF performance verification trace information file.
  
• TRN event trace information file
  This file stores traces of various events of the XA functions and transaction services that are called in transaction branches (transaction management service, transaction recovery service, and resource manager monitoring service).
  
• Backup file for TRN event trace information file
  This file serves as a backup of the TRN event trace information file.
  
• NAM event trace information file
  This file stores trace information for events relating to the name service, including communication invoked by the name service and the registration and deletion of service information from the cache.
  
• Backup file for NAM event trace information file
  This file serves as a backup of the NAM event trace information file.
  
• Process service event trace information file
  This file stores process service trace information.
  
• Backup file for process service event trace information file
  This file serves as a backup of the process service event trace information file.
  
• FIL event trace information file
  This file stores event information for when an OpenTP1 file access request required more processing time than the specified value.
  
• Backup file for FIL event trace information file
  This file serves as a backup of the FIL event trace information file.
  
• RTS log file
  The file stores real-time statistics.
  
• MCF statistics file
  This file stores MCF statistics.
  
• UAP trace data file
  This file stores UAP trace information. It is created only when Y is specified in the uap_trace_file_put operand. You specify the uap_trace_file_put operand in the following definitions:
  
  • System common definition
  • User service default definition
  • User service definition
• Backup file for UAP trace data file
  This file serves as a backup file of UAP trace data file.
  

The current working directory for the system service and user server is also created during OpenTP1 execution.

During execution, OpenTP1 creates files in directories it has created. The following table lists the files and directories created in the course of OpenTP1 operation.

Table 1-6 Files and directories created during normal operation

Name	Directory	File name
Message log file	$DCDIR/spool/	dclog1 and dclog2
MCF trace file#1	$DCDIR/spool/	mcftAXXZZ#2
Scheduling queue information file	$DCDIR/spool/	scdqid1 and scdqid2
RPC trace file	$DCDIR/spool/	rpctr1 and rpctr2#3
Trace information dump file	$DCDIR/spool/save/	dcmtrdpl and dcmtrdp2
Performance verification trace information file	$DCDIR/spool/dcprfinf/	prf_nnn#4
Backup file for performance verification trace information file	$DCDIR/spool/save/	prf_nnn.bk1#5, and prf_nnn.bk2#5
XAR performance verification trace information file	$DCDIR/spool/dcxarinf/	_xr_nnn#4
Backup file for XAR performance verification trace information file	$DCDIR/spool/save/	_xr_nnn.bk1#5, and _xr_nnn.bk2#5
JNL performance verification trace information file	$DCDIR/spool/dcjnlinf/prfinf/	_jl_nnn#4
Backup file for JNL performance verification trace information file	$DCDIR/spool/save/	_jl_nnn.bk1#5, and _jl_nnn.bk2#5
LCK Performance verification trace information file	$DCDIR/spool/dclckinf/prf/	_lk_nnn#4
Backup file for LCK performance verification trace information file	$DCDIR/spool/save/	_lk_nnn.bk1#5, and _lk_nnn.bk2#5
MCF performance verification trace information file	$DCDIR/spool/dcmcfinf/	_mc_nnn#4
Backup file for MCF performance verification trace information file	$DCDIR/spool/save/	_mc_nnn.bk1#5, and _mc_nnn.bk2#5
TRN event trace information file	$DCDIR/spool/dctrninf/trace/prf/	_tr_nnn#4
Backup file for TRN event trace information file	$DCDIR/spool/save/	_tr_nnn.bk1#5, and _tr_nnn.bk2#5
NAM event trace information file	$DCDIR/spool/dcnaminf/	_nm_001, _nm_002, and _nm_003
Backup file for NAM event trace information file	$DCDIR/spool/save/	_nm_nnn.bk1#5, and _nm_nnn.bk2#5
Process service event trace information file	$DCDIR/spool/dcprcinf/	_pr_001, _pr_002, and _pr_003
Backup file for process service event trace information file	$DCDIR/spool/save/	_pr_nnn.bk1#5, and _pr_nnn.bk2#5
FIL event trace information file	$DCDIR/spool/dcfilinf/	_fl_001, _fl_002, and _fl_003
Backup file for FIL event trace information file	$DCDIR/spool/save/	_fl_nnn.bk1#5, and _fl_nnn.bk2#5
RTS log file	$DCDIR/spool/dcrtsinf/#6	rtslog[1] to rtslog[10]#6, #7
MCF statistics file	$DCDIR/spool/#8	mcfstc#8
Current working directory#9	$DCDIR/tmp/home/server-name.ID#10/	--
UAP trace data file	$DCDIR/tmp/home/server-name.ID	dcuat.map
Backup file for UAP trace data file	$DCDIR/spool/save/trc/#11	server-namen.uatmap#12, and server-name_n.uatmap#12

Legend:

--: Need not be specified by the user.

#1

Required only when TP1/Message Control is used.

#2

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.

#3

The file name can be changed in the system common definition.

#4

Value ranging from 001 to the value specified in the prf_file_count operand in the following definition:

• Performance verification trace: Performance verification trace definition
• XAR performance verification trace: XAR performance verification trace definition
• JNL performance verification trace: JNL performance verification trace definition
• LCK performance verification trace: LCK performance verification trace definition
• MCF performance verification trace: MCF performance verification trace definition
• TRN event trace: TRN event trace definition

#5

nnn: Value corresponding to the name of the backup source file.

#6

If you do not specify the rts_log_file_name operand in the real-time statistics service definition, RTS log files are created in this directory.

#7

The number of created files is the number specified in the rts_log_file_count operand in the real-time statistics service definition.

#8

The mcfstc file is created in the $DCDIR/spool/ directory if you do not specify the output file name in the operation command (mcfstats).

#9

You can change the current working directory by setting the prc_current_work_path operand in the system common definition.

#10

For user environment setting commands, _usrcmd is displayed as the server name.

"ID" is a serial number not less than 1. ID is not added to operation commands (dcstart, dcstop, dcsvstart, and dcsvstop) and user environment setting commands.

#11

If the prc_coresave_path operand is specified in the process service definition, the directory will be prc_coresave_path-value/trc/.

#12

n: File serial number (1-3).

(b) Files created in the event of an error

The files listed below are created when errors occur.

• Shared memory dump file
  This file stores the contents of the shared memory output by OpenTP1.
  
• Core file
  This file saves the core file of an abnormally terminated process.
  
• Deadlock and timeout information file
  This file stores deadlock and timeout information.
  Delete unnecessary files.
  
• MCF dump file
  This file stores a dump of TP1/Message Control.
  
• MCF shared memory dump file
  This file stores the contents of the shared memory pool that were output by TP1/Message Control when errors occurred in the system service associated with sending and receiving messages.
  
• Undecided-transaction information file
  This file stores undecided transaction information in the event of an error.
  Delete unnecessary files.
  
• Incorrect journal information file
  This file stores incorrect data contained in an incorrect journal detected during reading of journals.
  
• Copy file of input/output queue contents
  This file stores the contents of input/output queues when the mcftdmpqu command (copy contents of input/output queues) is executed.
  
• UAP trace edit/output file
  The file stores UAP trace information that is edited and output automatically when a UAP terminated abnormally.
  
• OpenTP1 debug information file
  The file stores OpenTP1 debug information when a UAP terminated abnormally.
  

All files created during OpenTP1 execution are placed under an OpenTP1-created directory. The following table lists the files and directories that are created when an error occurs.

Table 1-7 Filesand directories created when an error occurs

Name	Directory	File name
Shared memory dump file	$DCDIR/spool/	Linux: shmdump[1 to 3].gz and shmdump.XXX#1[1 to 3].gz Other operating systems: shmdump[1 to 3].Z and shmdump.XXX#1[1 to 3].Z
Core file	$DCDIR/spool/save/	server-namen#2
Deadlock and timeout information file	$DCDIR/spool/dclckinf/	file-name#3
MCF dump file#4	$DCDIR/spool/	mcfdKAXXNN#5
MCF shared memory dump file#4	$DCDIR/spool/	mcfsAXXY#6
Undecided-transaction information file	$DCDIR/spool/dctrninf/	file-name#7
Incorrect journal information file	$DCDIR/spool/dcjnlinf/ errinf/	r_n#8
Copy file of input/output queue contents	$DCDIR/spool/	file-name#9
UAP trace edit output file	$DCDIR/spool/save	server-namen#10.uat
OpenTP1 debug information file	$DCDIR/spool/save	server-namen#10.deb

#1

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

#2

n

Core file serial number (1-3).

No serial number is assigned to a core file that is output when OpenTP1 is forced to terminate (that is, when the dcsvstop -df command or prckill command is executed or real time monitoring is timed out). A process service core file may be acquired in the directory under the name core. If a user environment setup command terminates abnormally, the core file is saved under the name _usrcmd followed by a sequential number (1-3).

#3

The file name is determined on the basis of the deadlock detection date and time. The length of the file name depends on whether the date is one digit or two digits.

Example

6: 29: 56 on October 3: Oct3062956

18: 06: 00 on October 10: Oct10180600

#4

Required only when TP1/Message Control is used.

#5

KAXXNN:

K: Process type.

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

NN: Dump serial number (01-99).

#6

AXXY:

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

Y: File serial number (1-3).

#7

The file name is rl + transaction service start time (eight hexadecimal digits).

#8

Generation number of a journal in which incorrect data was detected (hexadecimal)

#9

File name specified by the mcftdmpqu command (copy file of input/output queue contents).

#10

n: File serial number (1-3).

(c) Files for OpenTP1 internal processing

In addition to the files listed in (a) and (b) above, files for OpenTP1 internal processing are placed under $DCDIR/spool/ and $DCDIR/tmp/. Users must not change these files without authorization. All files placed under $DCDIR/tmp/ for internal processing are cleared when OpenTP1 is started.

(d) OS files that OpenTP1 uses

OpenTP1 uses /dev/console and /dev/null for standard input and output. Do not change the permissions for /dev/console and /dev/null. The operation may not be assured if the permissions are changed.