The files that must be created by the user are:

• User program file
  This file stores execution-form UAPs. The archive-journal target node need not have this file.
  
• 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
  These files store definition information. They must be created as text files using the OS text editor.
  The above files are stored under the directories created by the user. The following table lists the files and directories that are created by the user. The directories $DCDIR/aplib and $DCDIR/conf are to be created during installation of OpenTP1.
  

  Table 7-3 Files and directories created by the user

  File		Directory	File name	File type
  User program file		$DCDIR/aplib/#1	Executable program name#2	Executable file
  MCF communication process program file and MCF application startup process program file		$DCDIR/lib/servers/	Executable program name	Executable file
  Definition files	System environment definition	$DCDIR/conf	env	Text file
  	Other definitions	$DCCONFPATH/	Definition file name
  	System service information definition	$DCDIR/lib/sysconf/	System service information definition file name
  	System service common information definition#3	$DCDIR/lib/sysconf/	mcf

#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 following table lists the files and directories created at installation or cataloging into OS.

Table 7-4 Files and directories created at installation or cataloging into OS

Name		Directory	File name
OpenTP1 program files	OpenTP1 server	$DCDIR/lib/servers/	--#
	Commands	$DCDIR/bin/	--
	Header file	$DCDIR/include/	--
	Archive file	$DCDIR/lib/	--
Definition analysis files		$DCDIR/lib/sysconf/	--#
		$DCDIR/lib/sysdef/	--
Message object file		$DCDIR/lib/	msgtxt, jmsgtxt
User program file directory		$DCDIR/aplib/	None
Directory for definition files		$DCDIR/conf/	None
System management information directory		$DCDIR/etc/	--
Evacuated core file		$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/	--
Transaction control object storage directory		$DCDIR/spool/trnrmcmd/userobj/	dc_trn_allrm.0
Online tester directory		$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.

Note

Note that some directories and files are not used for archive-journal target nodes.

#

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

The following table lists the files and directories created at execution of OpenTP1.

Table 7-5 Files and directories created at execution of OpenTP1 (when using the multi-node facility)

Name	Directory	File name	Node 1#1	Node 2#2
Message log file	$DCDIR/spool/	dclogl or dclog2	Y	Y
MCF trace file#3	$DCDIR/spool/	mcft0XXZZ#4	N	Y
Scheduling queue information file	$DCDIR/spool/	scdqidl or scdqid2	N	Y
RPC trace file	$DCDIR/spool/	rpctrl or rpctr2#5	Y	Y
Trace information dump file	$DCDIR/spool/save/	dcmtrdpl or dcmtrdp2	Y	Y
Performance verification trace information file	$DCDIR/spool/dcprfinf/	prf_001, prf_002, prf_003	Y	Y
Backup file for performance verification trace information file	$DCDIR/spool/save/	prf_nnn.bk1#6 and prf_nnn.bk2#6	Y	Y
XAR performance verification trace information file	$DCDIR/spool/dcxarinf/	_xr_nnn#7	Y	Y
Backup file for XAR performance verification trace information file	$DCDIR/spool/save/	_xr_nnn.bk1#6 and _xr_nnn.bk2#6	Y	Y
JNL performance verification trace information file	$DCDIR/spool/dcjnlinf/prfinf/	_jl_nnn#7	Y	Y
Backup file for JNL performance verification trace information file	$DCDIR/spool/save/	_jl_nnn.bk1#6 and _jl_nnn.bk2#6	Y	Y
LCK performance verification trace information file	$DCDIR/spool/dclckinf/prf/	_lk_nnn#7	Y	Y
Backup file for LCK performance verification trace information file	$DCDIR/spool/save/	_lk_nnn.bk1#6 and _lk_nnn.bk2#6	Y	Y
MCF performance verification trace information file	$DCDIR/spool/dcmcfinf/	_mc_nnn#7	Y	Y
Backup file for MCF performance verification trace information file	$DCDIR/spool/save/	_mc_nnn.bk1#6 and _mc_nnn.bk2#6	Y	Y
TRN event trace information file	$DCDIR/spool/dctrninf/trace/prf/	_tr_nnn#7	Y	Y
Backup file for TRN event trace information file	$DCDIR/spool/save/	_tr_nnn.bk1#6 and _tr_nnn.bk2#6	Y	Y
NAM event trace information file	$DCDIR/spool/dcnaminf/	_nm_001, _nm_002, and _nm_003	Y	Y
Backup file for NAM event trace information file	$DCDIR/spool/save/	_nm_nnn.bk1#6 and _nm_nnn.bk2#6	Y	Y
Process service event trace information file	$DCDIR/spool/dcprcinf/	_pr_001, _pr_002, and _pr_003	Y	Y
Backup file for process service event trace information file	$DCDIR/spool/save/	_pr_nnn.bk1#6 and _pr_nnn.bk2#6	Y	Y
FIL event trace information file	$DCDIR/spool/dcfilinf/	_fl_001, _fl_002 and _fl_003	Y	Y
Backup file for FIL event trace information file	$DCDIR/spool/save/	_fl_nnn.bk1#6 and _fl_nnn.bk2#6	Y	Y
RTS log file	$DCDIR/spool/dcrtsinf/#8	rtslog[1-10]#8, #9	Y	Y
MCF statistics file	$DCDIR/spool/#10	mcfstc#10	N	Y
Current working directory#11	$DCDIR/tmp/home/server-name.ID#12/	--	Y	Y
UAP trace data file	$DCDIR/tmp/home/server-name.ID/	dcuat.map#13	Y	Y
Backup file for UAP trace data file	$DCDIR/spool/save/trc/#14	server-namen.uatmap#15 and server-name_n.uatmap#15	Y	Y
Shared memory dump file	$DCDIR/spool/	Linux: shmdump[1-3].gz, and shmdump.XXX#16[1-3].gz Other operating systems: shmdump[1-3].Z, and shmdump.XXX#16[1-3].Z	Y	Y
Core file	$DCDIR/spool/save/	server-namen#17	Y	Y
Deadlock and timeout information files	$DCDIR/spool/dclckinf/	file-name#18	N	Y
MCF dump file#3	$DCDIR/spool/	mcfdKAXXNN#19	N	Y
MCF common memory dump file#3	$DCDIR/spool/	mcfsAXXY#18	N	Y
Undetermined transaction information file	$DCDIR/spool/dctrninf/	file-name#21	N	Y
Invalid journal information file for archive journal node	$DCDIR/spool/dcjnlinf/errinf/	an_X#22	Y	N
Invalid journal information file for archive-journal source node	$DCDIR/spool/dcjnlinf/errinf/	r_n#23	N	Y
Copy file of input/output queue contents	$DCDIR/spool/	file-name#24	N	Y
UAP trace edit/output file	$DCDIR/spool/save/	server-nameN#15.uat	N	Y
OpenTP1 debug information file	$DCDIR/spool/save/	server-nameN#15.deb	Y	Y

Legend:

Y: Created.

N: Not created.

--: Need not be specified by the user.

#1

Archive-journal target node

#2

Archive-journal source node

#3

Required only when MCF is used.

#4

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

#5

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

#6

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

#7

nnn: Value in the range of 001 to the value specified in the prf_file_count operand in the definitions listed below:

• 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

#8

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.

#9

Files are created for the number of files specified in the rts_log_file_count operand in the real-time statistics service definition.

#10

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

#11

You can use the prc_current_work_path operand in the system common definition to change the current working directory.

#12

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.

#13

This file is created only when Y is specified in the uap_trace_file_put operand. This operand can be specified in one of the following definitions:

• System common definition
• User service default definition
• User service definition

#14

When the prc_coresave_path operand of the process service definition is specified, the directory is (prc_coresave_path-value)/trc/.

#15

n: File serial number (1-3)

#16

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

#17

n

Core file serial number (1-3)

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

#18

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

#19

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)

#20

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)

#21

rl+transaction service start time (8 hexadecimal characters)

#22

n: Resource group serial number of the journal in which invalid data was detected

This serial number is assigned sequentially to the resource groups specified in the -a option of the jnldfsv command of the global archive journal service definition.

X: Generation number of the journal in which invalid data was detected

#23

n

Generation number of the journal in which incorrect data was detected

#24

File name specified by the mcfdmpqu command (to copy the contents of input/output queues)

In addition to the files listed in these tables, there are files for OpenTP1 internal processing under the directories $DCDIR/spool/ and $DCDIR/tmp/. This must not be changed the user's discretion. All files for OpenTP1 internal processing under $DCDIR/tmp/ are cleared when OpenTP1 starts.