Appendix F. List of Files Output by OpenTP1

This appendix lists the files output by OpenTPI organized by product.

Organization of this section
(1) TP1/Server Base (common to both UNIX and Windows versions)
(2) TP1/Server Base (applicable to UNIX version only)
(3) TP1/Server Base (applicable to Windows version only)
(4) TP1/FS/Direct Access
(5) TP1/FS/Table Access
(6) TP1/Online Tester
(7) TP1/Message Control

(1) TP1/Server Base (common to both UNIX and Windows versions)

The table below lists the files that are output by TP1/Server Base (common to both UNIX and Windows versions). For details about each file, see Table F-2 Descriptions of the files output by TP1/Server Base (common to both UNIX and Windows versions).

Table F-1 List of files output by TP1/Server Base (common to both UNIX and Windows versions)

No.NameFile name or directory nameVersionTypeFile formatAcquisition timingDeletable
1Audit log filelog_audit_path-operand-value/audit.log
Default:
$DCDIR/auditlog/audit.log
07-02D, F, HTextWhen an audited event occursY
2Backup file for audit log filelog_audit_path-operand-value/auditNNN.log
(NNN: 001-255)
Default:
$DCDIR/auditlog/auditNNN.log
(NNN: 001-255)
07-02KTextWhen the size of the audit log file exceeds the log_audit_size operand valueY
3OpenTP1 automatic start checking file$DCDIR/spool/.automodeInitialJBinaryWhen OpenTP1 startsN
4Current work path control file 1UNIX version:
$DCDIR/spool/.dccurrent_path
Windows version:
$DCDIR\spool\dccurrent_path
UNIX version:
06-02
Windows version:
07-00
JBinaryWhen prcd starts (not when the dcstart command is executed)N
5prcd port information storage file$DCDIR/spool/.portidInitialJBinaryWhen prcd starts (not when the dcstart command is executed)N
6Command log$DCDIR/spool/cmdlog/cmdlogN
(N: 1 or 2)
UNIX version:
07-00
Windows version:
06-50
C, E, HTextWhen the target command is executedNE
7
  • Trace information dump file
  • Lock file (internal file)
$DCDIR/spool/dcdfmtrN, $DCDIR/spool/dcdfmtrl
(N: 1 or 2)
07-00JBinaryWhen the dcdefchk command is executedN
8FIL event trace information file$DCDIR/spool/dcfilinf/_fl_NNN
(NNN: 001-003)
07-03D, F, HBinaryWhen Y is specified in the prf_trace operand, 1 is specified in the fil_prf_trace_option operand, and the time required for file access processing is equal to or greater than the fil_prf_trace_delay_time operand valueNE
9Core file for jnlchgfg command$DCDIR/spool/dcjnlinf/errinf/chgfg_N
(N: PID of the command that shut down)
07-03ABinaryWhen the jnlchgfg command terminates abnormallyNE
10Core file for jnlcuef process$DCDIR/spool/dcjnlinf/errinf/cuef_N
(N: PID of the process that shut down)
07-03ABinaryWhen the internal command's process terminates abnormallyNE
11Invalid journal information file for journal file$DCDIR/spool/dcjnlinf/errinf/cuef_N
(N: PID of the command process that detected the invalid journal)
07-03ABinaryWhen the jnlunlfg, jnlchgfg, or jnlls command detects an invalid journalNE
12Core file for jnlls command$DCDIR/spool/dcjnlinf/errinf/ls_N
(N: PID of the command that shut down)
07-03ABinaryWhen the jnlls command terminates abnormallyNE
13Invalid journal information file for archive-journal source node$DCDIR/spool/dcjnlinf/errinf/r_N
(N: Generation number of the journal that contains invalid data)
InitialJTextWhen OpenTP1 is re-run and an error is detected in a loaded blockN
14Core file for jnlunlfg command$DCDIR/spool/dcjnlinf/errinf/unlfg_N
(N: PID of the command that shut down)
07-03ABinaryWhen the jnlunlfg command terminates abnormallyNE
15Journal message queue management file$DCDIR/spool/dcjnlinf/jnlqidInitialJBinaryWhen the journal service creates a message queueN
16JNL performance verification trace information file$DCDIR/spool/dcjnlinf/prfinf/_jn_NNN
(NNN: 001-256)
07-03D, F, HBinaryWhen Y is specified in the prf_trace operand and 00000001​ or 00000002​ is specified in the jnl_prf_event_trace_level operandNE
17Deadlock and timeout information files$DCDIR/spool/dclckinfInitialBTextWhen TAM, DAM, or the dc_lck_xxx function is used and a deadlock or lock timeout occursNE
18LCK performance verification trace information file$DCDIR/spool/dclckinf/_lk_NNN
(NNN: 001-256)
07-03D, F, HBinaryWhen transaction processing or lock processing is underwayNE
19Socket file for the message log notification function$DCDIR/spool/dcloginf/.logntf03-03JBinaryWhen the message log notification function is usedN
20Message log file$DCDIR/spool/dclogN
(N: 1 or 2)
InitialC, E, HTextWhen OpenTP1 is runN
21NAM event trace information file$DCDIR/spool/dcnaminf/_nm_NNN
(NNN: 001-003)
07-02D, F, HBinaryWhen Y is specified in the prf_trace operand and a value other than 00000000​ is specified in the nam_prf_trace_level operandNE
22Process service event trace information file$DCDIR/spool/dcprcinf/_pr_NNN
(NNN: 001-003)
07-02D, F, HBinaryWhen Y is specified in the prf_trace operand while Y is specified in the prc_prf_trace operandNE
23prfget command inheritance fileEarlier than 06-01 (earlier than 06-50 for Windows version):
$DCDIR/spool/dcprfinf/getinf
06-01 to 07-02:
$DCDIR/spool/dcprfinf/getinf, _trinf
07-02 or later:
$DCDIR/spool/dcprfinf/getinf, _trinf, _nminf, _prinf, _xrinf
InitialJBinaryWhen the prfget command is executed without the -a option specifiedN
24Performance verification trace information fileEarlier than 06-01 (earlier than 06-50 for Windows version):
$DCDIR/spool/dcprfinf/prf00N
(N: 1-3)
06-01 or later:
$DCDIR/spool/dcprfinf/prf_NNN
(NNN: 001-256)
InitialD, F, HBinaryWhen OpenTP1 is runNE
25Lock file for RAP-processing$DCDIR/spool/dcrapinf/RAP-processing-listener-nameInitialJBinaryWhen the remote API service startsN
26Invalid message file for RAP-processing03-05-/T, 03-06-/R, 05-03-/J or later:
$DCDIR/spool/dcrapinf/RAP-processing-listener-name.msg
05-04-/G, 06-00 or later:
$DCDIR/spool/dcrapinf/RAP-processing-listener-name.msg, RAP-processing-client-manager-name.msg
Earlier than 06-00 that is not included in the above versions:
$DCDIR/spool/dcrapinf/server-name_process-ID
InitialJ, ETextWhen an invalid message is received by the remote API serviceNE
27RTS log filerts_log_file_name-operand-valueN
(N: 1-10)
Default:
$DCDIR/spool/dcrtsinf/rtslogN
(N: 1-10)
07-00D, F, HBinaryWhen RTSSUP is started with Y specified in the rts_log_file operandNE
28Backup file for RTS log filerts_log_file_name-operand-valueN.bk
(N: 1-10)
Default:
$DCDIR/spool/dcrtsinf/rtslogN.bk
(N: 1-10)
07-02KBinaryWhen RTSSUP is startedNE
29Server recovery journal$DCDIR/spool/dcsjlInitialJBinaryAnytime during online operationN
30Transaction recovery journal$DCDIR/spool/dctjlinfInitialJBinaryAnytime during online operationN
31Undetermined-transaction information file$DCDIR/spool/dctrninf/file-nameInitialBTextWhen OpenTP1 is started for re-runNE
32TRN event trace information file (PRF trace)$DCDIR/spool/dctrninf/trace/prf/_tr_NNN
(NNN: 001-256)
UNIX version:
06-01
Windows version:
07-00
D, F, HBinaryWhen transaction processing is underwayNE
33TRN event trace file$DCDIR/spool/dctrninf/trace/trnevtrN
(N: 1 or 2)
InitialD, F, HBinaryWhen an error has occurred in an XA functionN
34Multiple-file management file (internal file)$DCDIR/spool/dcusmctlInitialJBinaryWhen the OpenTP1 system is shut down and a shared memory dump file is output due to intentional collection of data and forced termination specified by the -f and -d options in the dcstop commandN
35XAR performance verification trace information file$DCDIR/spool/dcxarinf/_xr_NNN
(NNN: 001-256)
07-02D, F, HBinaryWhen the XA resource service is used by specifying Y in the prf_trace operand and a value other than 00000000​ in the xar_prf_trace_level operandNE
36XAR event trace information file$DCDIR/spool/dcxarinf/trace/xarevtrN
(N: 1 or 2)
06-00D, F, HBinaryWhen the XA resource service is usedNE
37Backup file for XAR event trace information file$DCDIR/spool/dcxarinf/trace/xarevtrM.bkN
(M: 1 or 2, N: 1-3)
06-00KBinaryWhen the XA resource service is usedNE
38Error log information$DCDIR/spool/errlog/errlogN
(N: 1 or 2)
InitialC, E, HTextWhen OpenTP1 is runN
39Directory for system internal lock control$DCDIR/spool/olkfifsInitialJTextWhen the dcmakeup command is executed or when OpenTP1 startsN
40Directory for system internal synchronization control$DCDIR/spool/olkrsfsInitialJTextWhen the dcmakeup command is executed or when OpenTP1 startsN
41Control file for resources for internal control (FIFO file)$DCDIR/spool/oslcntlInitialJBinaryWhen the dcmakeup command is executed or when OpenTP1 startsN
42RPC log file$DCDIR/spool/rpclogN
(N: 1 or 2)
InitialC, E, HTextWhen a communication error (including internal communications) occursN
43RPC trace filerpc_trace_name-operand-value
Default:
$DCDIR/spool/rpctrN
(N: 1 or 2)
InitialC, E, HBinaryWhen the dc_rpc_call or dc_rpc_call_to function is issuedY
44Backup file for FIL event trace information file$DCDIR/spool/save/_fl_MMM.bkN
(MMM: 001-003, N: 1 or 2)
07-03KBinaryWhen OpenTP1 is shut downNE
45Backup file for JNL performance verification trace information file$DCDIR/spool/save/_jl_MMM.bkN
(MMM: 001-256, N: 1 or 2)
07-03KBinaryWhen OpenTP1 is shut downNE
46Backup file for LCK performance verification trace information file$DCDIR/spool/save/_lk_MMM.bkN
(MMM: 001-256, N: 1 or 2)
07-03KBinaryWhen OpenTP1 is shut downNE
47Backup file for NAM event trace information file$DCDIR/spool/save/_nm_MMM.bkN
(MMM: 001-003, N: 1 or 2)
07-02KBinaryWhen OpenTP1 is shut downNE
48Backup file for process service event trace information file$DCDIR/spool/save/_pr_MMM.bkN
(MMM: 001-003, N: 1 or 2)
07-02KBinaryWhen OpenTP1 is shut downNE
49Backup file for TRN event trace information file (PRF trace)$DCDIR/spool/save/_tr_MMM.bkN
(MMM: 001-256, N: 1 or 2)
UNIX version:
06-01
Windows version:
07-00
KBinaryWhen OpenTP1 is shut downNE
50Backup file for XAR performance verification trace information file$DCDIR/spool/save/_xr_MMM.bkN
(MMM: 001-256, N: 1 or 2)
07-02KBinaryWhen OpenTP1 is shut downNE
51Core fileprc_coresave_path-operand-value/server-nameN
(N: 1-3)
Default:
$DCDIR/spool/save/server-nameN
(N: 1-3)
InitialC, HBinaryWhen the process is shut down#NE
52OpenTP1 debug information fileprc_coresave_path-operand-value/server-nameN.deb
(N: 1-3)
Default:
$DCDIR/spool/save/server-nameN.deb
(N: 1-3)
InitialC, HTextWhen the process is shut down#NE
53
  • Trace information dump file
  • Lock file (internal file)
$DCDIR/spool/save/dcmtrdpN, dcmtrdpl
(N: 1 or 2)
InitialC, E, HBinaryWhen OpenTP1 is runN
54Backup file for performance verification trace information fileEarlier than 06-01:
$DCDIR/spool/save/prf_MMM.bkN
(MMM: 001-003, N: 1 or 2)
06-01 or later:
$DCDIR/spool/save/prf_MMM.bkN
(MMM: 001-256, N: 1 or 2)
07-00KBinaryWhen OpenTP1 is shut downNE
55Schedule queue information file$DCDIR/spool/scdqidN
(N: 1 or 2)
InitialC, E, HBinaryWhen the queue-receiving server is started, terminated, shut down, or released from shutdownN
56Shared memory dump file$DCDIR/spool/output-file-name-specified-for-usmdump-command-execution
Default:
$DCDIR/spool/shmdump
When DAM, TAM, IST, RTS, or TP1/Message Queue is used and the -i option is specified, the file names are as follows:
shmdump.dam.Z, shmdump.tam.Z, shmdump.ist.Z, shmdump.rts.Z, shmdump.mXX.Z
(XX: 00-ff)
InitialLBinaryWhen a file name is omitted in the argument during execution of the usmdump commandY
57Shared memory dump file$DCDIR/spool/shmdumpN
(N: 1-3)
When DAM, TAM, IST, RTS, or TP1/Message Queue is used and the -i option is specified, the file names are as follows:
shmdump.damN.Z, shmdump.tamN.Z, shmdump.istN.Z, shmdump.rtsN.Z, shmdump.mXXN.Z
(N: 1-3, XX: 00-ff)
InitialEBinaryWhen the system is shut down and when the dcstop command is executed with the -f and -d options specifiedNE
58Transaction control object$DCDIR/spool/trnrmcmd/userobjInitialJBinaryWhen the dcsetup, trnlnkrm, or trnmkobj command is executedNY
59Shared memory information file$DCDIR/tmp/dcommenvInitialJBinaryWhen OpenTP1 startsN
60Resources for internal control (FIFO file)$DCDIR/tmp/olkmsgInitialJTextWhen namedpipe is specified in the schedule_method operand in the user service default definition or user service definitionN
61jnlcolc command inheritance filecurrent-path-where-jnlcolc-command-executed/jnlcolcNNN
(NNN: 001-999)
InitialJBinaryWhen the jnlcolc command is executed without the -l option specifiedY
62Backup file for jnlcolc command inheritance filecurrent-path-where-jnlcolc-command-executed/jnlcolcNNN.bak
(NNN: 001-999)
InitialJBinaryWhen the jnlcolc command is executed without the -l option specified and the specified inheritance file already existsY
63jnlrput command inheritance filecurrent-path-where-jnlrput-command-executed/jnlrputNNN
(NNN: 001-999)
InitialJBinaryWhen the jnlrput command is executed with the -e option specified and the -l option omittedY
64Backup file for jnlrput command inheritance filecurrent-path-where-jnlrput-command-executed/jnlrputNNN.bak
(NNN: 001-999)
InitialJBinaryWhen the following conditions are met:
  • The jnlrput command is executed with the -e operand specified and the -l option omitted
  • The specified inheritance file already exists
Y
65Current work path control file 2UNIX version:
current-work-path/.dcdir_path
Windows version:
current-work-path/dcdir_pat
UNIX version:
06-02
Windows version:
07-00
JBinaryWhen prcd starts (not when the dcstart command is executed)N
66Work file for dcrasget commandtarget-directory/workUNIX version:
06-01
Windows version:
06-50
JBinaryWhen the dccspool command is executedAD
(dcrasget)
Legend:
A: Monotonic increase (with no deletion function)
B: Monotonic increase (with a deletion function)
C: Round-robin (with no backup acquisition function)
D: Round-robin (with a backup acquisition function)
E: Round-robin (data is output immediately after a specified amount is reached and then a new file is used)
F: Round-robin (data is output immediately before a specified amount is reached and then a new file is used)
H: Round-robin (existing data is deleted from the target file and then new data is written from the beginning)
J: Control file or temporary file
K: Backup file
L: File whose maximum size is predetermined and to which data is output each time by a method such as command execution
Y: Can be deleted at the user's discretion
NE: Must not be deleted, unless error checking is not required.
NY: Must not be deleted, with the exception of user-created files.
AD: Deleted when the command is terminated (parentheses enclose the name of the relevant command)
N: Must not be deleted
#
Includes process shutdown when the command is executed under the following conditions:
[Figure]The -f and -d options are specified in the dcstop command.
[Figure]The -f and -d options are specified in the dcsvstop command.

The table below describes the files that are output by TP1/Server Base (common to both UNIX and Windows versions).

Table F-2 Descriptions of the files output by TP1/Server Base (common to both UNIX and Windows versions)

No.NameRelated definitionSizeMax filesDescription
1Audit log file<Log service definition>
  • log_audit_out operand
    Whether to use the audit log function
  • log_audit_path operand
    Output directory for the audit log file
  • log_audit_size operand
    Maximum size of audit log file
  • log_audit_count operand
    Maximum number of audit log files
  • log_audit_message operand
    Message ID for an item for which an audit log is collected
<User service definition>
<User service default definition>
  • log_audit_out_suppress operand
    Suppress output of audit logs by this user server
  • log_audit_message operand
    Message ID for an item for which an audit log is collected
<RAP-processing listener service definition>
  • log_audit_out_suppress operand
    Suppress output of audit logs by RAP-processing listener and RAP-processing server
  • log_audit_message operand
    Message ID for an item for which an audit log is collected
<RAP-processing client manager service definition>
  • log_audit_out_suppress operand
    Suppress output of audit logs by the RAP-processing client manager.
  • log_audit_message operand
    Message ID for an item for which audit log is collected
log_audit_size operand value1 generationThis is an audit log file that is obtained when Y is specified in the log_audit_out operand.
For details about the events that are subject to audit log collection, see the description of the definition for acquiring audited events in the manual OpenTP1 System Definition.
2Backup file for audit log fileSame as for audit log file (No. 1)log_audit_size operand valueThe maximum value is the log_audit_count operand value - 1 generationThis is a backup file for the audit log file.
3OpenTP1 automatic start checking fileNoneSeveral bytes (fixed)1 fileThis file is used to control OpenTP1 operation.
4Current work path control file 1NoneSeveral bytes (variable)1 fileThis file is used to control OpenTP1 operation.
5prcd port information storage fileNoneSeveral bytes (fixed)1 fileThis file is used to control OpenTP1 operation.
6Command logNone1024 kilobytes2 generationsThis file is used to output command logs that are collected during command execution. For details about the operation commands for which command logs are output, see 12.1.4 List of operation commands.
Note that the default is that command logs are not collected for MCF commands. To collect command logs, specify Y in the DCMCFCMDLOG environment variable.
7
  • Trace information dump file
  • Lock file (internal file)
None64 kilobytes (dump file), 272 bytes (lock file)3 files (dump file: 2 generations, lock file: 1 file)These files are used to control OpenTP1 operation. They are the module trace storage file and lock file used during execution of the dcdefchk command.
8FIL event trace information file<System common definition>
  • prf_trace operand
    Whether performance verification trace information is to be acquired
  • fil_prf_trace_option operand
    Whether FIL event traces are to be acquired
  • fil_prf_trace_delay_time operand
    Threshold value for file access processing time that is used as the condition for acquiring FIL event traces
<Performance verification trace definition>
  • prf_trace_backup operand
    Acquires a backup of the trace file
Maximum 1 megabyte3 generationsThis is a FIL event trace information file. It is used to acquire FIL event trace information when Y is specified in the prf_trace operand and 1 in the fil_prf_trace_option operand.
If N is specified in the prf_trace_backup operand, the backup file is not acquired.
9Core file for jnlchgfg commandNoneSize of memory used for process#1Monotonic increaseThis is a core file of the jnlchgfg command. It is acquired when the jnlchgfg command terminates abnormally.
10Core file for jnlcuef processNoneSize of memory used for process#1Monotonic increaseThis is a core file of the jnlcuef process. It is acquired when the jnlcuef process terminates abnormally.
11Invalid journal information file for journal files<System journal service definition>
  • jnl_max_datasize operand
    Maximum length of record data
jnl_max_datasize operand valueMonotonic increaseThis is an invalid journal information file for journal files. It is acquired when the jnlls command detects an invalid journal.
12Core file for jnlls commandNoneSize of memory used for process#1Monotonic increaseThis is a core file of the jnlls command. It is acquired when the jnlls command terminates abnormally.
13Invalid journal information file for archive-journal source node<System journal service definition>
  • jnl_max_datasize operand
    Maximum length of record data
  • jnl_dual operand
    Whether dual journal files are to be used
jnl_max_datasize operand valuejnl_dual=N:
1 file
jnl_dual=Y:
2 files
This is an invalid journal information file for the archive-journal source node. It is acquired when there is an error in a block that was read when OpenTP1 started the re-run (abnormal).#2
14Core file for jnlunlfg commandNoneSize of memory used for process#1Monotonic increaseThis is a core file of the jnlunlfg command. It is acquired when the jnlunlfg command terminates abnormally.
15Journal message queue management file<System journal service definition>
  • jnl_dual operand
    Whether dual journal files are to be used
  • jnl_max_file_dispersion operand
    Maximum number of dispersions for enabling parallel access
<Archive journal service definition>
  • jnl_dual operand
    Whether dual journal files are to be used
  • jnl_max_file_dispersion operand
    Maximum number of dispersions for enabling parallel access
  • For archive-journal source node
    16 bytes x (jnl_max_file_dispersion operand value x n + 1)
    (n: 2 for jnl_dual=Y, 1 for jnl_dual=N)
  • For archive journal node
    16 bytes x (jnl_max_file_dispersion operand value x n x r + 1)
    (n: 2 for jnl_dual=Y, 1 for jnl_dual=N)
    (r: Number of resource groups specified in -a in jnldfsv definition command in global archive journal service definition)
1 fileThis file is used to control OpenTP1 operation.
16JNL performance verification trace information file<System common definition>
  • prf_trace operand
    Whether performance verification trace information is to be acquired
  • jnl_prf_event_trace_level operand
    Whether JNL performance verification traces are to be acquired
<JNL performance verification trace definition>
  • prf_file_size operand
    Size of the trace file
  • prf_file_count operand
    Number of trace file generations
  • prf_trace_backup operand
    Acquires a backup of trace file
prf_file_size operand valueprf_file_count operand valueThis is a JNL performance verification trace information file. The trace information is acquired when Y is specified in the prf_trace operand and 00000001​ or 00000002​ is specified in the jnl_prf_event_trace_level operand.
In version 07-03 or later, a backup file is not acquired when N is specified in the prf_trace_backup operand.
17Deadlock and timeout information files<Lock service definition>
  • lck_deadlock_info operand
    Whether deadlock and timeout information is to be output
  • lck_deadlock_info_remove operand
    Whether the deadlock information file and timeout information file are to be deleted at system startup
  • lck_deadlock_info_remove_level operand
    Deletion level of the deadlock information file and timeout information file
Several kilobytes (variable)VariableThese are the deadlock and timeout information files. Deadlock information and lock wait timeout information are acquired when Y is specified in the lck_deadlock_info operand. The files are deleted during OpenTP1 startup if the lck_deadlock_info_remove and lck_deadlock_info_remove_level operands are specified. The default is that the files are not deleted.
18LCK performance verification trace information file<System common definition>
  • prf_trace operand
    Whether performance verification trace information is to be acquired
<Lock service definition>
  • lck_prf_trace_level operand
    Acquisition level for LCK performance verification trace information
<Performance verification trace definition>
  • prf_trace_backup operand
    Acquires a backup of the trace file
<LCK performance verification trace definition>
  • prf_file_size operand
    Size of LCK performance verification trace information file
  • prf_information_level operand
    Display level for messages related to LCK performance verification traces
  • prf_file_count operand
    Number of generations of LCK performance verification trace information files
prf_file_size operand valueprf_file_count operand valueThis is an LCK performance verification trace information file. Trace information is acquired for various types of lock control associated with transaction processing when Y is specified in the prf_trace operand. The default is that this information is acquired.
In version 07-03 or later, a backup file is not acquired when N is specified in the prf_trace_backup operand.
19Socket file for message log notification function<Log service definition>
  • log_notify_out operand
    Whether the message log notification function is to be used
  • log_notify_xxx operand
    Whether information corresponding to log_notify_xxx is to be added
01 fileThis is a socket file used by the message log notification function.
20Message log file<Log service definition>
  • log_filesize operand
    Maximum size of message log file
log_filesize operand value2 generationsThis is an OpenTP1 message log file.
21NAM event trace information file<System common definition>
  • prf_trace operand
    Whether performance verification trace information is to be acquired
  • nam_prf_trace_level operand
    Acquisition level for NAM event trace information
<Performance verification trace definition>
  • prf_trace_backup operand
    Acquires a backup of the trace file
Maximum 10 megabytes3 generationsThis is a NAM event trace information file. NAM event trace information is acquired when Y is specified in the prf_trace operand and a value other than 00000000​ is specified in the nam_prf_trace_level operand.
In version 07-02 or later, a backup file is not acquired when N is specified in the prf_trace_backup operand.
22Process service event trace information file<System common definition>
  • prf_trace operand
    Whether performance verification trace information is to be acquired
<Performance verification trace definition>
  • prf_trace_backup operand
    Acquires a backup of the trace file
<Process service definition>
  • prc_prf_trace operand
    Whether event traces are to be acquired for the process service
Maximum 1 megabyte3 generationsThis is a process service event trace information file. Process service event trace information is acquired when Y is specified in both prf_trace and prc_prf_trace operands.
In version 07-02 or later, a backup file is not acquired when N is specified in the prf_trace_backup operand.
23prfget command inheritance fileNone128 bytesEarlier than 06-01:
1 file
06-01 to earlier than 07-02:
2 files
07-02 or later:
5 files
This file is used to control OpenTP1 operation. This is an internal file used to record the location of trace data that has already been acquired during execution of the prfget command.
24Performance verification trace information file<System common definition>
  • prf_trace operand
    Whether performance verification trace information is to be acquired
<Performance verification trace definition>
  • prf_file_size operand
    Size of the trace file
  • prf_information_level operand
    Output level of trace file-related messages
  • prf_file_count operand
    Number of trace file generations
  • prf_trace_backup operand
    Acquires a backup of the trace file
prf_file_size operand valueEarlier than 06-01:
3 generations
06-01 or later:
prf_file_count operand value
This is a performance verification trace information file. Performance verification trace information is acquired when Y is specified in the prf_trace operand. The default is that this file is acquired.
In version 07-02 or later, the backup file is not acquired when N is specified in the prf_trace_backup operand.
25Lock file for RAP-processingNone16 bytes x (1 + number of RAP-processing servers)Number of RAP-processing listenersThis file is used to control OpenTP1 operation. It is a lock file used to synchronize the RAP-processing listener and server.
26Invalid message file for RAP-processingNone03-05-/T, 03-06-/R, 05-03-/J, 05-04-/G, 06-00 or later:
Maximum 1 megabyte.
Earlier than 06-00 that is not included in the above versions:
Monotonic increase
Depends on the version.#3This is a troubleshooting file that is created when an invalid message is received by the API service.
27RTS log file<Real-time statistics service definition>
  • rts_log_file operand
    Whether acquired statistical information is to be output to the RTS log file
  • rts_log_file_name operand
    Name of the RTS log file
  • rts_log_file_size operand
    Size of the RTS log file
  • rts_log_file_count operand
    Number of RTS log file generations
  • rts_log_file_backup operand
    Whether a backup of the RTS log file is to be created
Maximum value is the rts_log_file_size operand valuerts_log_file_count operand valueThis is a real-time statistics log file. Real-time statistics are acquired when Y is specified in the rts_log_file operand.
In version 07-02 or later, a backup file is acquired at the time RTSSUP starts if Y is specified in the rts_log_file_backup operand.
28Backup file for RTS log fileSame as for the real-time statistics (RTS) log file (No. 27)Maximum value is the rts_log_file_size operand valuerts_log_file_count operand value x 1 generationThis is a backup file for the real-time statistics log file. This backup file is not acquired when N is specified in the rts_log_file_backup operand.
29Server recovery journalNoneSeveral bytes to kilobytes (variable)VariableThis file is used to acquire various types of journal information for each system service.
30Transaction recovery journalNoneSeveral bytes to kilobytes (variable)VariableThis file is used to acquire various types of journal information related to transactions for each transaction branch (UAP process).
31Undetermined-transaction information file<Transaction service definition>
  • trn_tran_recovery_list operand
    Whether undetermined transaction information is to be acquired during a complete recovery
  • trn_recovery_list_remove operand
    Whether the undetermined-transaction information file is to be deleted during OpenTP1 startup.
  • trn_recovery_list_remove_level operand
    Deletion level for the undetermined-transaction information file
Several kilobytes (Monotonic increase)VariableThis is an undetermined-transaction information file. Undetermined transaction information is acquired when Y is specified in the trn_tran_recovery_list operand. This file is deleted during startup of OpenTP1 if the trn_recovery_list_remove and trn_recovery_list_remove_level operands are specified. The default is that this file is not deleted.
32TRN event trace information file (PRF trace)<System common definition>
  • prf_trace operand
    Whether performance verification trace information is to be acquired
<Transaction service definition>
  • trn_prf_event_trace_level operand
    Acquisition level for TRN event trace information
  • trn_prf_event_trace_condition operand
    Type of TRN event trace to be acquired
<Performance verification trace definition>
  • prf_trace_backup operand
    Acquires a backup of the trace file
<TRN event trace definition>
  • prf_file_size operand
    Size of trace file for TRN event trace information
  • prf_information_level operand
    Display level for messages related to TRN event traces
  • prf_file_count operand
    Number of trace file generations for TRN event trace information
prf_file_size operand valueprf_file_count operand valueThis is a TRN event trace information file. TRN event trace information (various events associated with the transaction services and the XA functions issued at transaction branches) is acquired when Y is specified in the prf_trace operand. The default is that this information is acquired.
In version 07-02 or later, a backup file is not acquired when N is specified in the prf_trace_backup operand.
33TRN event trace fileNone1024 kilobytes2 generationsThis is a TRN event trace file. It is used to acquire trace information related to transaction processing. Its contents are not disclosed.
34Multiple-file management file (internal file)None16 bytes1 fileThis file is used to control OpenTP1 operation. It is a generation management file for recording the current generation of shared-memory dump files.
35XAR performance verification trace information file<System common definition>
  • prf_trace operand
    Whether performance verification trace information is to be acquired
<Performance verification trace definition>
  • prf_trace_backup operand
    Acquires a backup of the trace file
<XA resource service definition>
  • xar_prf_trace_level operand
    Acquisition level for XAR performance verification trace information
<XAR performance verification trace definition>
  • prf_file_size operand
    Size of XAR performance verification trace information file
  • prf_information_level operand
    Display level for messages related to XAR performance verification traces.
  • prf_file_count operand
    Number of generations of XAR performance verification trace information files
prf_file_size operand valueprf_file_count operand valueThis is an XAR performance verification trace information file. XAR performance verification trace information is acquired when Y is specified in the prf_trace operand and a value other than 00000000​ is specified in the xar_prf_trace_level operand. When N is specified in the prf_trace_backup operand, a backup file is not acquired.
36XAR event trace information file<Transaction service definition>
  • trn_xar_use operand
    Whether the XA resource service is to be used
<XA resource service definition>
  • xar_eventtrace_level operand
    Output level for the XAR event trace information
  • xar_eventtrace_record operand
    Maximum number of records output to the XAR event trace information file
xar_eventtrace_record operand value x 224 + 82 generationsThis is an XAR event trace information file. XAR event trace information is acquired when Y is specified in the trn_xar_use operand.
37Backup file for XAR event trace information fileSame as for the XAR event trace information file (No. 36)xar_eventtrace_record operand value x 224 + 82 x 3 generationsThis is a backup file of the XAR event trace information file.
38Error log informationNoneEarlier than 06-01:
64 kilobytes
06-01 or later:
1 megabyte
2 generationsThis is internal trace information for OpenTP1. Its contents are not disclosed.
39Directory for system internal lock control<Process service definition>
  • prc_process_count operand
    Maximum number of server processes that can be started concurrently
0prc_process_count operand value x 2This file is used to control OpenTP1 operation.
40Directory for system internal synchronization control<Process service definition>
  • prc_process_count operand
    Maximum number of server processes that can be started concurrently
0prc_process_count operand value + 83This file is used to control OpenTP1 operation.
41Control file for resources for internal control (FIFO file)None32 bytes (32 or 64 bits)1 fileThis file is used to control OpenTP1 operation.
42RPC log fileNone1 megabyte2 generationsThis is communication trace information for checking design.
43RPC trace file<System common definition>
  • rpc_trace operand
    Whether RPC traces are to be acquired
  • rpc_trace_name operand
    Name of the file for acquiring RPC traces
  • rpc_trace_size operand
    Size of the file for acquiring RPC traces
Maximum value is the rpc_trace_size operand value2 generationsThis is an RPC trace file. When Y is specified in the rpc_trace operand, RPC service request information (event information and the messages that are sent and received when the dc_rpc_call or dc_rpc_call_to function is issued) is acquired.
44Backup file for FIL event trace information fileSame as for the FIL event trace information file (No. 8)Maximum 1 megabyte3 x 2 generationsThis is a backup file for the FIL event race file. It is acquired when Y is specified in the prf_trace operand and 1 in the fil_prf_trace_option operand.
When N is specified in the prf_trace_backup operand, the backup file is not acquired.
45Backup file for JNL performance verification trace information fileSame as for the JNL performance verification trace information file (No. 16)prf_file_size operand valueprf_file_count operand value x 2 generationsThis is a backup file for JNL performance verification trace information file. It is acquired when Y is specified in the prf_trace operand and 00000001​ or 00000002​ is specified in the jnl_prf_event_trace_level operand. In version 07-03 or later, this backup file is not acquired when N is specified in the prf_trace_backup operand.
46Backup file for LCK performance verification trace information fileSame as for the LCK performance verification trace information file (No. 18)prf_file_size operand valueprf_file_count operand value x 2 generationsThis is a backup file for LCK performance verification trace information file. It is acquired when Y is specified in the prf_trace operand.
In version 07-03 or later, this backup file is not acquired when N is specified in the prf_trace_backup operand.
47Backup file for NAM event trace information fileSame as for the NAM event trace information file (No. 21)Maximum 10 megabytes3 x 2 generationsThis is a backup file for the NAM event trace file. It is acquired when Y is specified in the prf_trace operand and a value other than 00000000​ is specified in the nam_prf_trace_level operand.
In version 07-02 or later, this backup file is not acquired when N is specified in the prf_trace_backup operand.
48Backup file for process service event trace information fileSame as for the process service event trace information file (No. 22)Maximum 1 megabyte3 x 2 generationsThis is a backup file for the process service event trace file. It is acquired when Y is specified in the prf_trace operand and Y in the prc_prf_trace operand.
In version 07-02 or later, this backup file is not acquired when N is specified in the prf_trace_backup operand.
49Backup file for TRN event trace information file (PRF trace)Same as for the TRN event trace information file (PRF trace) (No. 32)prf_file_size operand valueprf_file_count operand value x 2 generationsThis is a backup file for the TRN event trace file. It is acquired when Y is specified in the prf_trace operand.
In version 07-02 or later, this backup file is not acquired when N is specified in the prf_trace_backup operand.
50Backup file for XAR performance verification trace information fileSame as for the XAR performance verification trace information file (No. 35)prf_file_size operand valueprf_file_count operand value x 2 generationsThis is a backup file for the XAR performance verification trace information file. It is acquired when Y is specified in the prf_trace operand. This backup file is not acquired when N is specified in the prf_trace_backup operand.
51Core file<Process service definition>
  • prc_coresave_path operand
    Core file storage path
  • prc_corecompress operand
    Core file is to be compressed automatically by OpenTP1 when it is stored
<User service definition>
<User service default definition>
  • core_shm_suppress operand
    Whether output of a memory dump to the core file is to be suppressed
<Environment variable>
  • CORE_NOSHM
    Suppression of output of shared memory to the core file (applicable to AIX version)
    For details about suppression of output of shared memory to the core file, see the Release Notes.
Amount of memory used for process#13 generationsThis is a core file for system and user servers that have been shut down. Note that generation management is not applicable to a core file for a user server that was terminated by the dcsvstop command with the -f and -d options specified, or by the prckill command or for a user server that was terminated because realtime monitoring resulted in a timeout.
52OpenTP1 debug information file<Process service definition>
  • prc_coresave_path operand
    Core file storage path
Variable3 generationsThis is a debugging information file for system and user servers that have been shut down.
53Trace information dump fileNone64 kilobytes (module trace), 272 bytes (file for trace control)3 files (module trace: 2 generations, trace control file: 1 file)This is a trace information dump file for internal checking.
54Backup file for performance verification trace information fileSame as for the performance verification trace information file (No. 24)prf_file_size operand valueEarlier than 06-01:
3 x 2 generations
06-01 or later:
prf_file_count operand value x 2 generations
This is a backup file for the performance verification trace information file. It is acquired when Y is specified in the prf_trace operand.
In version 07-02 or later, a backup file is not acquired when N is specified in the prf_trace_backup operand. Backup acquisition suppression is applied to the following files:
  • Performance verification trace information file
  • TRN event trace file
  • NAM event trace file
  • XAR performance verification trace information file
  • Process service event trace
55Schedule queue information file<Schedule service definition>
  • scd_server_count operand
    Maximum number of user servers
(scd_server_count operand + 4) x 16 + 32 (bytes, maximum)2 generationsThis file is used to control OpenTP1 operation.
56Shared memory dump fileNoneDepends on the machine status and OpenTP1 system operating status1 generation#4This is a dump of the shared memory allocated by OpenTIP1.
57Shared memory dump fileNoneDepends on the machine status and OpenTP1 system operating status3 generations#4This is a dump of the shared memory allocated by OpenTIP1.
58Transaction control objectNoneSeveral to dozens of kilobytes (variable)1 or more filesThis file is used to control OpenTP1 operation. This is an object (dc_trn_allrm.o) file created at the extension of the trnlnkrm command or an object file created by the user at the extension of the trnmkobj command.
A user's file is created only when the trnmkobj command is executed.
59Shared memory information fileNone544 bytes (32 or 64 bits)1 fileThis file is used to control OpenTP1 operation.
60Resources for internal control (FIFO file)<Schedule service definition>
  • scd_server_count operand
    Maximum number of user servers
0scd_server_count operand valueThis file is used to control OpenTP1 operation.
61jnlcolc command inheritance fileNoneDepends on the size of recovery journal to be extracted1 fileThis file is used to control OpenTP1 operation. It is an inheritance file that is created when the jnlcolc command is used to extract a recovery journal of multiple journals.
62Backup file for jnlcolc command inheritance fileNoneSize of the inheritance file before renaming1 fileThis file is used to control OpenTP1 operation. If the jnlcolc command is executed and the specified inheritance file already exists, this file is created by renaming the existing file as jnlcolc***.bak.
63jnlrput command inheritance fileNoneDepends on the size of the transaction-undetermined UJ1 fileThis file is used to control OpenTP1 operation. It is an inheritance file that is created when the jnlrput command is used to extract a transaction-determined UJ of multiple journals.
64Backup file for jnlrput command inheritance fileNoneSize of the inheritance file before renaming1 fileThis file is used to control OpenTP1 operation. If the jnlrput command is executed and the specified inheritance file already exists, this file is created by renaming the existing file as jnlrput***.bak.
65Current work path control file 2NoneDepends on DCDIR1 fileThis file is used to control OpenTP1 operation.
66Work file for dcrasget commandNoneDepends on the information to be collectedDepends on the information to be collectedThis file is used to control OpenTP1 operation.
Legend:
Max files: Maximum number of files
#1
The size of memory used is variable because it depends on the coding. In versions other than UP-UX and Windows, the size requirement is even larger because a shared memory dump is provided.
#2
This file is acquired even when there is no end block. Therefore, if there was no time to write the end block for a reason such as forced termination of OpenTP1, the file is output whether or not a block error occurred.
#3
The maximum number of files depends on the product version, as follows.
For 03-05-/T, 03-06-/R, 05-03-/J, 05-04-/G, or 06-00 or later:
Number of processes for which invalid messages were received by the remote API service (for the RAP-processing server, information is output to the same file as for the RAP-processing listener).
For a version earlier than 06-00 that is not one of the above versions:
Number of processes for which invalid messages were received by the remote API service.
#4
The uncompressed file is deleted after the file is compressed; however, immediately after compression, both uncompressed and compressed files exist. Therefore, the disk space required is twice the maximum size of the uncompressed file.

(2) TP1/Server Base (applicable to UNIX version only)

The table below lists the files that are output by TP1/Server Base (applicable to UNIX version only). For details about each file, see Table F-4 Descriptions of the files output by TP1/Server Base (applicable to UNIX version only).

Table F-3 List of files output by TP1/Server Base (applicable to UNIX version only)

No.NameFile name or directory nameVersionTypeFile formatAcquisition timingDeletable
1Communication control file$DCDIR/.tact/*InitialJLocal socketWhen a process is startedN
2Backup file for inittab$DCDIR/conf/Inittab/inittabN
(N: 1-3)
InitialKTextWhen dcsetup command is executedY
3Control file for dccspool$DCDIR/spool/.dccspool_time06-02JNullWhen dccspool command is executedAD (dccspool)
4Pipe file for prctee$DCDIR/spool/.prc_fifo05-00JBinaryWhen prctee command is startedN
5PID storage file for prctee process$DCDIR/spool/.prc_teeInitialJBinaryWhen prctee command is startedN
6prctee process start error output file$DCDIR/spool/.prcerr.log07-00ATextWhen prctee command startup failsNE
7PAUSE checking file for prcd$DCDIR/spool/.prcnopauseInitialJBinaryWhen OpenTP1 startsN
8PID storage file for Linux prcd$DCDIR/spool/.prcpid06-00JBinaryWhen prcd starts (not when dcstart command is executed)N
9prctee process error output file$DCDIR/spool/.prctee.log07-00ATextWhen an output error occurs on betarn.logNE
10Archive-journal source node connection information file$DCDIR/spool/dcjnlinf/coninfInitialJTextWhen connection is established with or released from the archive journal nodeNE
11Archive journal node connection information file$DCDIR/spool/dcjnlinf/coninfInitialJTextWhen connection is established with or released from the archive-journal source nodeNE
12Invalid journal information file for archive journal node$DCDIR/spool/dcjnlinf/errinf/an_X
(n: Resource group serial number for 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 definition command in the global archive journal service definition
X: Generation number of the journal in which invalid data was detected)
InitialJTextWhen OpenTP1 is re-run and an error is detected in a loaded blockN
13Invalid journal information file for archive journal file$DCDIR/spool/dcjnlinf/errinf/cuef_N
(N: PID of the command that was shut down)
07-03ABinaryWhen the jnlunlfg, jnlchgfg, or jnlls command detects an invalid journalNE
14GWF log file$DCDIR/spool/gwflogN
(N: 1 or 2)
InitialC, E, HTextWhen a gateway service-related internal function returns control with an errorN
15UAP trace edit/output fileprc_coresave_path-operand-value/server-nameN.uat
(N: 1-3)
Default:
$DCDIR/spool/save/server-nameN.uat
(N: 1-3)
InitialC, HTextWhen the process is shut down#NE
16Backup file for UAP trace data file$DCDIR/spool/save/trc/server-name_N.uatmap
(N: 1-3)
When server terminates abnormally:
$DCDIR/spool/save/trc/server-nameN.uatmap
(N: 1-3)
07-03KBinaryWhen the user server is shut down or when OpenTP1 startsNE
17Backup file for module trace data file$DCDIR/spool/save/trc/server-name_N.umtmap
(N: 1-3)
When server terminates abnormally:
$DCDIR/spool/save/trc/server-nameN.umtmap
(N: 1-3)
07-03KBinaryWhen the user server is shut down or when OpenTP1 startsNE
18PID file for prcd management process$DCDIR/tmp/home/server-name/.prc.PIDInitialJNullWhen each process is startedN
19UAP trace data file$DCDIR/tmp/home/server-name.ID/dcuat.map07-03CBinaryWhen a UAP process is startedNE
20Module trace data file$DCDIR/tmp/home/server-name.XX/dcumt.map
(XX: Serial number)
07-03CBinaryWhen a process is startedNE
21DCDIR management information in the same machineLinux version:
/opt/OpenTP1/etc/.OpenTP1
AIX or HI-UX/WE2 version:
/usr/etc/BeTRAN
InitialJTextWhen dcsetup command is executedN
22DCDIR management shell in the same machineLinux version:
/opt/OpenTP1/etc/dcpwon
AIX or HI-UX/WE2 version:
/usr/bin/dcpwon
InitialJTextWhen dcsetup command is executedN
23Communication control file1. In Linux version:
/opt/OpenTP1/etc/so_unix
2. In Solaris version whose OS version is 10 or later and whose environment is Zone (virtual server):
/etc/OpenTP1/so_unix
3. Other:
/dev/OpenTP1/so_unix
In case 1:
05-03
In case 2:
07-00
In case 3:
03-02
JLocal socketWhen a process is startedN
24Backup file for dcsetup/tmp/.admdPID/*InitialJTextWhen dcsetup command is executedAD
(dcsetup)
25Realtime output function (betran.log)HP-UX, AIX, or Solaris version:
/tmp/betran.log
Linux (IPF) version:
$DCDIR/spool/betran.log
Linux (x86):
$DCDIR/spool/prclogN
(N: 1 or 2)
HI-UX/WE2 version:
This file is not used because data is output to the console.
InitialATextWhen OpenTP1 is runN
26Temporary file used during execution of namdomainsetup command/tmp/TP1dmfilwork(PID)InitialJTextWhen namdomainsetup command is executedAD
(namdomainsetup)
27Lock file for dcsetupLinux version:
/var/spool/.OpenTP1.HiRDB/.lock
AIX or HI-UX/WE2 version:
/usr/spool/.OpenTP1.HiRDB/.lock
InitialJBinaryWhen dcsetup command is executedN
28Temporary file used during execution of jnlsort commandcurrent-path-where-jnlsort-command-executed/sort_I + process-ID
current-path-where-jnlsort-command-executed/sort_o + process-ID
InitialJTextWhen jnlsort command is executed with the -g option omittedAD
(jnlsort)
Legend:
A: Monotonic increase (with no deletion function)
C: Round-robin (with no backup acquisition function)
E: Round-robin (data is output immediately after a specified amount is reached and then a new file is used)
H: Round-robin (existing data is deleted from the target file and then new data is written from the beginning)
J: Control file or temporary file
K: Backup file
Y: Can be deleted at the user's discretion
NE: Must not be deleted, unless error checking is not required.
AD: Deleted when the command is terminated (parentheses enclose the name of the applicable command)
N: Must not be deleted
#
Includes process shutdown when the command is executed under the following conditions:
[Figure]The -f and -d options are specified in the dcstop command.
[Figure]The -f and -d options are specified in the dcsvstop command.

The table below describes the files that are output by TP1/Server Base (applicable to UNIX version only).

Table F-4 Descriptions of the files output by TP1/Server Base (applicable to UNIX version only)

No.NameRelated definitionSizeMax filesDescription
1Communication control fileNoneCommunication message sizeNumber of active processesThis file is used when communication is performed on the local machine.
2Backup file for inittabNoneSize of /etc/inittab file3 generationsThis is a backup file for the /etc/inittab file.
3Control file for dccspoolNone01 fileThis file is used to control OpenTP1 operation.
4Pipe file for prcteeNoneSeveral bytes (fixed)1 fileThis file is used to control OpenTP1 operation.
5PID storage file for prctee processNoneSeveral bytes (fixed)1 fileThis file is used to control OpenTP1 operation.
6prctee process start error output fileNoneMonotonic increase1 fileThis file is used to output prcd information in the event of a prctee process start error.
7PAUSE checking file for prcdNoneSeveral bytes (fixed)1 fileThis file is used to control OpenTP1 operation.
8PID storage file for Linux prcdNoneSeveral bytes (fixed)1 fileThis file is used to control OpenTP1 operation.
9prctee process error output fileNoneMonotonic increase1 fileThis file is used to output information about output errors on betran.log.
10Archive-journal source node connection information file<Global archive journal service definition>
  • jnldfsv definition command
    Number of resource groups for the global archive journal service
124 bytesNumber of resource groups specified in -a option of jnldfsv definition command in the global archive journal service definitionThis is a connection information file for the archive-journal source node. When the global archive journal function is used, connection information for the archive journal node is acquired.
11Archive journal node connection information fileNone124 bytes x number of archive-journal source nodes to be connected to the archive journal nodeNumber of archive-journal source nodes to be connected to the archive journal nodeThis is a connection information file for the archive journal node. When the global archive journal function is used, connection information for the archive-journal source node is acquired.
12Invalid journal information file for archive journal node<Archive journal service definition>
  • jnl_arc_max_datasize operand
    Maximum size of transfer data during archive processing
  • jnl_dual operand
    Whether dual journal files are to be used
jnl_arc_max_datasize operand valueFor jnl_dual=N:
Number of archive-journal source nodes to be connected to the archive journal node
For jnl_dual=Y:
Number of archive-journal source nodes to be connected to the archive journal node x 2
This is an invalid journal information file for the archive journal node. It is acquired when there is an error in the blocks read when OpenTP1 started the re-run (abnormal).#
13Invalid journal information file for archive journal file<Global archive journal service definition>
  • jnl_arc_max_datasize operand
    Maximum size of transfer data during archive processing
jnl_arc_max_datasize operand valueMonotonic increaseThis is an invalid journal information file for the archive journal file. It is acquired when the jnlls command detects an invalid journal.
14GWF log fileNone0.1 megabytes2 generationsThis is communication trace information for checking design. Note that the gateway service is not supported by the Linux and Solaris versions. None of the OSs supports 07-00 or later.
15UAP trace edit/output file<Process service definition>
  • prc_coresave_path operand
    Core file storage path
Variable3 generationsThis is a UAP trace information file for system and user servers that have been shut down.
16Backup file for UAP trace data file<User service definition>
<User service default definition>
<System common definition>
<Individual system service definition>
  • uap_trace_max operand
    Number of UAP trace records
  • traceinfo_output_file operand
    Whether UAP and module trace information are to be output to a file
32-bit version:
((uap_trace_max operand value + 1) x 256) + 128 (bytes)
64-bit version:
((uap_trace_max operand value + 1) x 264) + 144 (bytes)
6 generations (3 generations in the case of normal or abnormal termination)This is a backup file for the source data file for the UAP trace edit/output file to which UAP trace information for system and user servers is output.
17Backup file for module trace data file<User service definition>
<User service default definition>
<System common definition>
<Individual system service definition>
  • traceinfo_output_file operand
    Whether UAP and module trace information are to be output to a file
32-bit version:
4096 bytes (for the process server, 73696 bytes)
64-bit version:
6128 bytes (for the process server, 110528 bytes)
6 generations (3 generations in the case of normal or abnormal termination)This is a backup file for the source data file for the module trace edit/output file to which module trace information for system and user servers is output.
18PID file for prcd management processNone0As many as the number of processesThis file is used to control OpenTP1 operation.
19UAP trace data file<User service definition>
<User service default definition>
<System common definition>
<Individual system service definition>
  • uap_trace_max operand
    Number of UAP trace records
  • traceinfo_output_file operand
    Whether UAP and module trace information is to be output to a file
32-bit version:
((uap_trace_max operand value + 1) x 256) + 128 (bytes)
64-bit version:
((uap_trace_max operand value + 1) x 264) + 144 (bytes)
1 generationThis is a source data file for the UAP trace edit/output file to which UAP trace information for system and user servers is output.
20Module trace data file<User service definition>
<User service default definition>
<System common definition>
<Individual system service definition>
  • traceinfo_output_file operand
    Whether UAP and module trace information is to be output to a file
32-bit version:
4096 bytes (for the process server, 73696 bytes)
64-bit version:
6128 bytes (for the process server, 110528 bytes)
1 generationThis is a source data file for the module trace edit/output file to which module trace information for system and user servers is output.
21DCDIR management information in the same machineNoneDepends on DCDIR registered in the same machine1 fileThis file is used to control OpenTP1 operation.
22DCDIR management shell in the same machineNoneDepends on DCDIR registered in the same machine1 fileThis file is used to control OpenTP1 operation.
23Communication control file<System common definition>
  • rpc_multi_tp1_in_same_host operand
    Whether on the same host multiple OpenTP1 systems are to be run as the same global domain (group of node names specified in the all_node operand in the system common definition)
Communication message sizeNumber of active processesThis file is used when communication is performed on the local machine.
24Backup file for dcsetupNoneDepends on length of DCDIR and size of /etc/inittab12 filesThis file is used to control OpenTP1 operation.
25Realtime output function (betran.log)NoneMonotonic increase (if changed to the wraparound method, 65535 kilobytes)1 generation (2 generations if changed to the wraparound method)This is a log file used to output standard output and standard error output information. In versions earlier than 07-00, information about prctee process errors is also output to this file. You can rename the file and change its storage directory and file size. For details, see the software documentation or 3.5 Standard output file operations.
26Temporary file used during execution of namdomainsetup commandNoneSize equivalent to number of lines in the hosts file of host names that were specified in the domain data file1 fileThis file is used to control OpenTP1 operation. When the namdomainsetup command is executed, this file is created temporarily to check if host names specified in the domain data file are already registered.
27Lock file for dcsetupNone01 fileThis file is used to control OpenTP1 operation.
28Temporary file used during execution of jnlsort commandNone
  • sort_I + process ID
    256 bytes x number of blocks to be sorted
  • sort_o + process ID
    256 bytes x number of blocks to be sorted
1 file per sort_I + process ID
1 file per sort_o + process ID
This file is used to control OpenTP1 operation. It is a journal block information file before and after blocks are sorted by the OS's sort command.
Legend:
Max files: Maximum number of files
#
This file is acquired even when there is no end block. Therefore, if there was no time to write the end block for a reason such as forced termination of OpenTP1, this file is output whether or not a block error occurred.

(3) TP1/Server Base (applicable to Windows version only)

The table below lists the files that are output by TP1/Server Base (applicable to Windows version only). For details about each file, see Table F-6 Descriptions of the files output by TP1/Server Base (applicable to Windows version only).

Table F-5 List of files output by TP1/Server Base (applicable to Windows version only)

No.NameFile name or directory nameVersionTypeFile formatAcquisition timingDeletable
1Patch log fileTP1/Server Base:
%DCDIR%\patchlogbase.txt
DAM:
%DCDIR%\patchlogdam.txt
TAM:
%DCDIR%\patchlogtam.txt
EXT1:
%DCDIR%\patchlogext1.txt
HAF:
%DCDIR%\patchloghaf.txt
07-00ATextAcquired at the extension of patch executionNE
2prctee process error output file%DCDIR%\spool\betran.err05-00-/EATextWhen OpenTP1 startsN
3Lock file for raw device%DCDIR%\spool\dcntbinf\rawlock_N
(N: Drive letter)
06-50JNullWhen raw device is opened for the first timeN
4Backup module (UMT) trace file%DCDIR%\spool\save\trc\_zx.umt
(z: server name of 1-8 characters, x: serial number)
InitialIBinaryWhen OpenTP1 startsY
5Backup UAP trace file%DCDIR%\spool\save\trc\server-nameN.uat
(N: 1-10)
InitialC, IBinaryWhen a process is shut down# and when OpenTP1 startsNE
6Shared memory file%DCDIR%\spool\shm\N
(N: numeric character beginning at 1)
InitialJBinaryWhen OpenTP1 starts. The next time online operation begins, the file is deleted and then re-created.N
7Lock file for GUI%DCDIR%\tp1_tools\Control.lck
%DCDIR%\tp1_tools\Environment.lck
06-50JNullWhen the GUI function is used. The file is deleted when the GUI function is terminated.N
8admshowpp log file%temp%\admshowpp.log07-01JTextAcquired at the extension of the dcsetup commandN
9dcsetup log file%temp%\dcsetup.logInitialATextAcquired at the extension of the installer and patch operationNE
10dcsetupml log file%temp%\dcsetupml.log06-50ATextAcquired at the extension of the dcsetupml command and installer operationNE
11trnlnkrm log file%temp%\trnlnkrm.logInitialATextAcquired at the extension of the trnlnkrm command execution, dcsetupml command execution, installer operation, and patch operationNE
12Standard output redirect fileredirect_file_name-operand-valueN
(N: 1 or 2)
Default:
%DCDIR%\spool\prclogN
(N: 1 or 2)
05-00-/EC, E, HTextWhen OpenTP1 is runY
13UAP trace filecurrent-work-path\tmp\home\_z.x\_zPPPPP.uat
(z: server name of 1-8 characters, PPPPP: PID, x: serial number)
InitialIBinaryCreated at the extension of the user server startupY
14Module (UMT) trace filecurrent-work-path\tmp\home\_z.x\_zPPPPP.umt
(z: server name of 1-8 characters, PPPPP: PID, x: serial number)
For a process server:
%DCDIR%\spool\save\_prcPPPPP.umt
(PPPPP: PID)
InitialIBinaryCreated at the extension of the OpenTP1 startup and user server startupY
Legend:
A: Monotonic increase (with no deletion function)
C: Round-robin (with no backup acquisition function)
E: Round-robin (data is output immediately after a specified amount is reached and then a new file is used)
H: Round-robin (existing data is deleted from the target file and then new data is written from the beginning)
I: Round-robin (a new file is used when OpenTP1 starts)
J: Control file or temporary file
Y: Can be deleted at the user's discretion
NE: Must not be deleted, unless error checking is not required.
N: Must not be deleted.
#
Includes process shutdown when the command is executed under the following conditions:
[Figure]The -f and -d options are specified in the dcstop command.
[Figure]The -f and -d options are specified in the dcsvstop command.

The table below describes the files that are output by TP1/Server Base (applicable to Windows version only).

Table F-6 Descriptions of the files output by TP1/Server Base (applicable to Windows version only)

No.NameRelated definitionSizeMax filesDescription
1Patch log fileNoneMonotonic increase
This file is overwritten each time a patch is executed.
5 files
(BASE: 1 generation, DAM: 1 generation, TAM: 1 generation, EXT1: 1 generation, HAF: 1 generation)
This is a patch execution log file. It is acquired when a patch is executed.
2prctee process error output fileNoneMonotonic increase1 fileThis file is used to output prctee process error information.
3Lock file for raw deviceNone0Number of raw devices usedThis file is used to control OpenTP1 operation. It is an internal file created when a raw device is used for the OpenTP1 file system.
4Backup module (UMT) trace fileNone4160 bytes (for a process server, 73696 bytes)10 generations x number of active serversThis is a backup file for the module (UMT) trace file.
5Backup UAP trace fileNoneVariable10 generationsThis is a UAP trace information file for system and user servers that have been shut down.
6Shared memory fileNoneDepends on the machine status and OpenTP1 system operating status1 generationThis file is used to control OpenTP1 operation. It is a shared memory file allocated by OpenTP1.
7Lock file for GUINone02 filesThis file is used to control OpenTP1 operation. It is created to prevent duplicate startup when OpenTP1's GUI function is used.
8admshowpp log fileNoneDuring normal operation: 0 bytes
In event of an error: Size varies
This file is overwritten each time a command is executed.
1 generationThis file is used to control OpenTP1 operation. It is an error log for internal commands. Internal commands that execute at the extension of the dcsetup command output logs to this file. In the event of a command error, the error details are output to the file.
9dcsetup log fileNoneMonotonic increase
This file is overwritten each time a command is executed.
1 generationThis is a trace file for the dcsetup command. It is acquired at the extension of the installer operation and patch operation.
10dcsetupml log fileNoneMonotonic increase
This file is overwritten each time a command is executed.
1 generationThis is a trace file for the dcsetup command. It is acquired at the extension of dcsetupml command execution and installer operation.
11trnlnkrm log fileNoneMonotonic increase
This file is overwritten each time a command is executed.
1 generationThis is a trace file for the trnlnkrm command. It is acquired at the extension of trnlnkrm command execution, dcsetupml command execution, installer operation, and patch operation.
12Standard output redirect file<System environment definition>
  • redirect_file operand
    Destination of standard output and standard error output for a process under OpenTP1
  • redirect_file_name operand
    Name of the standard output and standard error output file
  • redirect_file_size operand
    Size of the standard output and standard error output file
Maximum value is the redirect_file_size operand value (can be changed to a file that increases monotonically)2 generations (1 generation if changed to a file that increases monotonically)This is a log file used to output standard output and standard error output information. This file is output only when Y is specified in the redirect_file operand. This file is not output when the prc_port and rpc_port_base operands are specified in the system common definition.
13UAP trace file<User service definition>
<User service default definition>
  • uap_trace_max operand
    Maximum number of UAP trace records
Variable1 generation x number of active serversThis is a UAP trace file for a process during online operation.
14Module (UMT) trace fileNone4160 bytes (for a process server, 73696 bytes)1 generation x number of active serversThis is a module (UMT) trace file for a process during online operation.
Legend:
Max files: Maximum number of files

(4) TP1/FS/Direct Access

The table below lists the files that are output by TP1/FS/Direct Access. For details about each file, see Table F-8 Descriptions of the files output by TP1/FS/Direct Access.

Table F-7 List of files output by TP1/FS/Direct Access

No.NameFile name or directory nameVersionTypeFile formatAcquisition timingDeletable
1damd life checking file$DCDIR/tmp/damliveInitialJBinaryWhen damd is startedN
2Temporary file during logical file recoverydamfrc-command-execution-directory/.dcdamPPPPPPP
(PPPPPPP: last 7 digits of PID)
InitialJBinaryWhen the damfrc command is executed with the -c option omitted and an online backup file specifiedAD
(damfrc)
3Temporary file during acquisition of online DAM backupdambkup--o--s-execution-directory/bkTTTTPPPP
(TTTT: last 4 digits of the total time in seconds PPPP: last 4 digits of the process ID)
InitialJBinaryWhen the dambkup command is executed with the -o and -s options specifiedAD
(damfrc)
Legend:
J: Control file or temporary file
AD: Deleted when the command is terminated. Parentheses enclose the name of the applicable command.
N: Must not be deleted.

The table below describes the files that are output by TP1/FS/Direct Access.

Table F-8 Descriptions of the files output by TP1/FS/Direct Access

No.NameRelated definitionSizeMax filesDescription
1damd life checking fileNone136 bytes1 fileThis file is used to control OpenTP1 operation. It determines whether damd is running.
2Temporary file during logical file recoveryNone96 bytes1 fileThis file is used to control OpenTP1 operation. When the damfrc command is executed with the -c option omitted and an online backup file specified, internal information is output to a temporary file under the directory where the command was executed.
3Temporary file during acquisition of online DAM backupNoneSize of DAM file that is to be backed up + 128 bytes1 fileThis file is used to control OpenTP1 operation. When the dambkup command is executed with the -o and -s options specified, this file is used for temporary storage of backup data for the DAM file before the backup data is output to standard output.
Legend:
Max files: Maximum number of files

(5) TP1/FS/Table Access

The table below lists the files that are output by TP1/FS/Table Access. For details about each file, see Table F-10 Descriptions of the files output by TP1/FS/Table Access.

Table F-9 List of files output by TP1/FS/Table Access

No.NameFile name or directory nameVersionTypeFile formatAcquisition timingDeletable
1Temporary file during acquisition of online TAM backup$DCDIR/tmp/.dctamdN
(N: 1-9999999​)
InitialJBinaryWhen tambkup command is executed with -o operand specifiedAD
(tambkup)
2Shared memory information file (for TAM)$DCDIR/tmp/tammemfileInitialJBinaryWhen OpenTP1 startsN
3Temporary file during logical file recoverytamfrc-command-execution-directory/.dctamPIDInitialJBinaryWhen tamfrc command is executed with -j option omitted and an online backup file specifiedAD
(tamfrc)
Legend:
J: Control file or temporary file
AD: Deleted when the command is terminated. Parentheses enclose the name of the applicable command.
N: Must not be deleted.

The table below describes the files that are output by TP1/FS/Table Access.

Table F-10 Descriptions of the files output by TP1/FS/Table Access

No.NameRelated definitionSizeMax filesDescription
1Temporary file during acquisition of online TAM backupNoneSize of TAM file to be backed up1 fileThis file is used to control OpenTP1 operation. When the tambkup command is executed with the -o operand specified, this file is used for temporary storage of backup data for the TAM file.
2Shared memory information file (for TAM)None4 bytes1 fileThis file is used to control OpenTP1 operation.
3Temporary file during logical file recoveryNone96 bytes1 fileThis file is used to control OpenTP1 operation. When the tamfrc command is executed with the -j option omitted and an online backup file specified, internal information is output to a temporary file under the directory where the command was executed.
Legend:
Max files: Maximum number of files

(6) TP1/Online Tester

The table below lists the files that are output by TP1/Online Tester. For details about each file, see Table F-12 Descriptions of the files output by TP1/Online Tester.

Table F-11 List of files output by TP1/Online Tester

No.NameFile name or directory nameVersionTypeFile formatAcquisition timingDeletable
1XATMI send data file$DCDIR/spool/uto/test-user-ID/user-service-name/xsdservice-nameInitialJBinaryWhen a client's XATMI request made by the tpsend function is acceptedY
2MCF send message file$DCDIR/spool/uto/test-user-ID/user-service-name/sendmsgInitialJBinaryWhen a client's request made by an MCF function listed in Table F-12 is acceptedY
3UTO trace file$DCDIR/spool/uto/test-user-ID/traceN
(N: 1 or 2)
InitialC, E, HBinaryWhen an online tester is used to check UAP operationY
4Temporarily stored data file$DCDIR/spool/uto/test-user-ID/utotmplogical-terminal-nameInitialJBinaryWhen temporarily stored data is received from a client by issuing the dc_mcf_tempput functionY
5Test data definition fileFile path specified in -o option of utofilcre operand, or
File path specified in the test data definition file that was specified in the -e option of the utofilcre operand
You can create the following tester files:
  • RPC request data file
  • RPC response data file
  • XATMI request data file
  • XATMI response data file
  • XATMI receive data file
  • Asynchronous receive data file
  • Synchronous receive data file
InitialJBinaryWhen the utofilcre command is executedY
6MCF receive message file (there are asynchronous and synchronous files)File path specified in r option of utomsgout commandInitialJBinaryWhen the utomsgout command is executed with the -r operand specifiedY
7RPC response data fileFile path specified for the RPC response data file name in the utosppsvc commandInitialJBinaryWhen the utosppsvc command is executed with the RPC response data file name specifiedY
8UTO trace merge fileFile path specified in -o option of utotrcmrg commandInitialJBinaryWhen the utotrcmrg command is executed with the -o operand specifiedY
9XATMI response data fileFile path specified for the XATMI response data file name in the utoxsppsvc commandInitialJBinaryWhen the utoxsppsvc command is executed with the XATMI response data file name specifiedY
Legend:
C: Round-robin (with no backup acquisition function)
E: Round-robin (data is output immediately after a specified amount is reached and then a new file is used)
H: Round-robin (existing data is deleted from the target file and then new data is written from the beginning)
J: Control file or temporary file
Y: Can be deleted at the user's discretion

The table below describes the files that are output by TP1/Online Tester.

Table F-12 Descriptions of the files output by TP1/Online Tester

No.NameRelated definitionSizeMax filesDescription
1XATMI send data file<User service definition>
The user server name becomes part of the output path.
The service name becomes part of the file name.
<Environment variable>
The test user ID (DCUTOKEY) setting becomes part of the output path.
XATMI send data length+ 68 bytes1 file for each set of a test user ID, user server name, and service nameThis is an XATMI send data file. When a client issues the tpsend function, the send data is stored in this file.
2MCF send message file<Tester service definition>
  • max_message_file_size operand
    Maximum size of MCF send message file
max_message_file_size operand value1 file for each test user IDThis file stores MCF send messages. When the MCF simulation function is used, this file stores send messages when the following functions are issued:
  • dc_mcf_execap function
  • dc_mcf_reply function
  • dc_mcf_send function
  • dc_mcf_sendsync function
  • dc_mcf_sendrecv function
3UTO trace file<Tester service definition>
  • max_trace_file_size operand
    Maximum size of file used to collect UAP trace information
max_trace_file_size operand value2 generationsThis is a UTO trace file. It is used to collect UAP trace information.
4Temporarily stored data file<Tester service definition>
The utotmp logical terminal name becomes the file name.
<Environment variable>
The test user ID (DCUTOKEY) setting becomes part of the output path.
128 bytes1 file for each set of a test user ID and utotmp logical terminal nameThis file is used to control OpenTP1 operation. When a client issues the dc_mcf_tempput function, the temporarily stored data is stored in the file.
5
  • RPC request data file
  • RPC response data file
  • XATMI request data file
  • XATMI response data file
  • XATMI receive data file
  • Asynchronous receive data file
  • Synchronous receive data file
NoneAny size1 fileThis is a test data definition file used by the online tester.
6MCF receive message file (there are asynchronous and synchronous files)NoneAny size1 fileThis file is used to store MCF receive messages. The MCF receive messages are created by editing the send message information output by the online tester.
  • Asynchronous-type
    Messages that are passed to MHP's dc_mcf_receive function
  • Synchronous type
    Messages that are passed to UAP's functions, such as dc_mcf_recvsync and dc_mcf_sendrecv
7RPC response data fileNoneAny size1 fileThis is an RPC response data file. When the server UAP simulation function with an RPC interface is used, this file is used as the response data that is returned to the program requesting the service.
8UTO trace merge fileNoneTotal size of files specified for trace file names1 fileThis is a UTO trace merge file. It is created when the utotrcmrg command is used to merge multiple UTO trace files into one file.
9XATMI response data fileOverall typed buffer definitionUndefined because the file is created on the basis of the typed buffer definition file and XATMI request data file1 fileThis is an XATMI response data file. It is used as the receive data during service execution and as the response data after service execution.
Legend:
Max files: Maximum number of files

(7) TP1/Message Control

The table below lists the files that are output by TP1/Message Control. For details about each file, see Table F-14 Descriptions of the files output by TP1/Message Control.

Table F-13 List of files output by TP1/Message Control

No.NameFile name or directory nameVersionTypeFile formatAcquisition timingDeletable
1Backup file for system service common information definition file$DCDIR/.mcfdef/mcf05-05KTextWhen the dcsetup command is executed with the -d operand specifiedN
2Backup file for system service information definition file$DCDIR/.mcfdef/mcfu*05-05KTextWhen the dcsetup command is executed with the -d operand specifiedN
3Backup file for executable MCF communication server program$DCDIR/.mcfserv/mcfu*05-05KBinaryWhen the dcsetup command is executed with the -d operand specifiedN
4MCF dump file#1$DCDIR/spool/mcfdKAXXZZ
(K: process identifier, AXX: MCF identifier, ZZ: 01-99)
InitialH, IBinaryWhen an error (such as an internal conflict) is detected in TP1/Message Control or TP1/MessagingNE
5MCF trace file#1$DCDIR/spool/mcftAXXZZ
(AXX: MCF identifier, ZZ: 01-99)
InitialH, IBinaryWhen a trace buffer becomes full in shared memory while an MCF communication process is runningNE
6MCF performance verification trace information file#1$DCDIR/spool/dcmcfinf/_mc_NNN
(NNN: 000-256)
07-01D, FBinaryWhen a trace buffer becomes full while an MCF communication process or UAP is runningNE
7Backup file when preparation for MCF configuration change is stopped#2DCMCFQUEBAK value in the system service common information definition
Default: $DCDIR/spool/mcf/mcfquebak
07-03KBinaryWhen preparation for MCF configuration change is stopped (by executing dcstop -b -q)Y#3
8Backup file for MCF performance verification trace information file#1$DCDIR/spool/save/_mc_MMM.bkN
(MMM: 001-256, N: 1 or 2)
07-01KBinaryWhen OpenTP1 has stoppedNE
9Mapping error information file#4$DCDIR/spool/save/dcmap_errXXX
(XXX: process ID of TP1/NET/XMAP3 MCF communication process)
InitialH, ITextWhen an error occurs during mappingNE
Legend:
D: Round-robin (with a backup acquisition function)
F: Round-robin (data is output immediately before a specified amount is reached and then a new file is used)
H: Round-robin (existing data is deleted from the target file and then new data is written from the beginning)
I: Round-robin (a new file is used when OpenTP1 starts)
K: Backup file
Y: Can be deleted at the user's discretion
NE: Must not be deleted, unless error checking is not required.
N: Must not be deleted.
#1
This file is output for TP1/Message Control, TP1/NET/Library, protocol products, and TP1/Messaging.
#2
This file is output for TP1/Message Control, TP1/NET/Library, and protocol products.
#3
You can delete the file after the MCF configuration change restart is complete.
#4
This file is output for TP1/NET/XMAP3.

The table below describes the files that are output by TP1/Message Control.

Table F-14 Descriptions of the files output by TP1/Message Control

No.NameRelated definitionSizeMax filesDescription
1Backup file for system service common information definition fileSystem service common information definition ($DCDIR/lib/sysconf/mcf)Size of the $DCDIR/lib/sysconf/mcf file1 fileThis is a backup file for the system service common information definition.
2Backup file for system service information definition fileSystem service information definitionSize of the system service information definition fileNumber of system service information definition filesThis is a backup file for the system service information definition.
3Backup file for executable MCF communication server programNoneSize of the MCF communication process program or MCF application start process program ($DCDIR/lib/servers/mcfu*)Number of executable MCF communication server programsThis is a backup file for the executable MCF communication server program.
4MCF dump file#1NoneSize determined using the formula for estimating the size of an MCF dump file in the MCF Release Notes.Following number of files output by MCF manager process, MCF communication process, and UAP:
TP1/NET/Library version earlier than 07-03:
99 files
TP1/NET/Library 07-04 or later:
3 files
This file is used to obtain memory information in the event of an MCF failure. It is used for troubleshooting purposes. This file is not output during normal processing.
5MCF trace file#1<Trace definition in MCF communication configuration definition>
-t option in mcfttrc definition command
  • size operand
    Trace buffer size
  • bufcnt operand
    Number of trace buffers
  • trccnt operand
    Number of trace files
  • disk operand
    Whether disk output feature is to be used
-m option in mcfttrc definition command
Handling of the number of files
size value x bufcnt valueWhen del is specified in -m option: trccnt operand value
When off is specified in -m option: 99 files
This file is used to collect send/receive data and events that occur within MCF.
It is used for troubleshooting purposes. If disk=no is specified (or omitted), this trace file is not created. In version 07-00 or later, disk=yes is the default setting.
6MCF performance verification trace information file#1<System common definition>
  • prf_trace operand
    Whether PRF traces are to be acquired
<User service default definition>
  • mcf_prf_trace operand
<User service definition>
  • mcf_prf_trace operand
    Whether PRF traces are to be acquired for each user server
<MCF performance verification trace definition>
  • prf_file_size operand
    Trace file size
  • prf_file_count operand
    Number of trace file generations
<System service definition>
  • mcf_prf_trace operand
    Whether PRF traces are to be acquired for each MCF communication process
<System service common information definition>
  • mcf_prf_trace_level operand
    Acquisition level for the MCF performance verification trace information
prf_file_size operand valueprf_file_count operand valueThis is an MCF performance verification trace information file. It is used for performance verification and troubleshooting purposes. Performance verification trace information is acquired when Y is specified in the prf_trace operand in the system common definition and 00000001​ is specified in the mcf_prf_trace_level operand in the system service common information definition. The default is that this file is not acquired.
7Backup file when the preparation for MCF configuration change is stopped#2<System service common information definition>
putenv DCMCFQUEBAK backup-file-name~ <path name><<$DCDIR/spool/mcf/mcfquebak>>
296 + number of queue groups x 16 + number of logical terminals x 20 + number of service groups x 44 + number of untransmitted or unprocessed messages x (average message length + 1036) (bytes)1 fileThis is a backup file for untransmitted and unprocessed messages when the MCF configuration change restart function is used.
8Backup file for MCF performance verification trace information file#1Same as for MCF performance verification trace information file (No. 6)prf_file_size operand valueprf_file_count operand value x 2 generationsThis is a backup file for the MCF performance verification trace information file. It is obtained when Y is specified in the prf_trace operand and 00000001​ is specified in the mcf_prf_trace_level operand in the system common definition.
In version 07-02 or later, this backup file is not obtained when prf_trace_backup=N is specified in the performance verification trace definition.
9Mapping error information file#3<Mapping service attribute definition>
ERRLOG4={YES|NO}
  • YES
    Acquires error information.
  • NO
    Does not acquire error information if a mapping error with error code 4 (minor error) occurs.
Depends on size of logical map area and size of physical map fileNumber of MCF communication processes#4This file is used to acquire error information in the event of a mapping error. It is used for troubleshooting purposes.
Legend:
Max files: Maximum number of files
#1
This file is output for TP1/Message Control, TP1/NET/Library, protocol products, and TP1/Messaging.
#2
This file is output for TP1/Message Control, TP1/NET/Library, and protocol products.
#3
This file is output for TP1/NET/XMAP3.
#4
This is the number of TP1/NET/XMAP3 MCF communication processes in which a mapping error has occurred. This value increases each time the process ID of the mapping service process changes at the start of OpenTP1.