![[Contents]](FIGURE/CONTENT.GIF)
OpenTP1 Version 7 Operation
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
![[Next]](FIGURE/AFTER.GIF)
This appendix lists the files output by OpenTPI organized by product.
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. | Name | File name or directory name | Version | Type | File format | Acquisition timing | Deletable |
|---|---|---|---|---|---|---|---|
| 1 | Audit log file | log_audit_path-operand-value/audit.log Default: $DCDIR/auditlog/audit.log |
07-02 | D, F, H | Text | When an audited event occurs | Y |
| 2 | Backup file for audit log file | log_audit_path-operand-value/auditNNN.log (NNN: 001-255) Default: $DCDIR/auditlog/auditNNN.log (NNN: 001-255) |
07-02 | K | Text | When the size of the audit log file exceeds the log_audit_size operand value | Y |
| 3 | OpenTP1 automatic start checking file | $DCDIR/spool/.automode | Initial | J | Binary | When OpenTP1 starts | N |
| 4 | Current work path control file 1 | UNIX version: $DCDIR/spool/.dccurrent_path Windows version: $DCDIR\spool\dccurrent_path |
UNIX version: 06-02 Windows version: 07-00 |
J | Binary | When prcd starts (not when the dcstart command is executed) | N |
| 5 | prcd port information storage file | $DCDIR/spool/.portid | Initial | J | Binary | When prcd starts (not when the dcstart command is executed) | N |
| 6 | Command log | $DCDIR/spool/cmdlog/cmdlogN (N: 1 or 2) |
UNIX version: 07-00 Windows version: 06-50 |
C, E, H | Text | When the target command is executed | NE |
| 7 |
|
$DCDIR/spool/dcdfmtrN, $DCDIR/spool/dcdfmtrl (N: 1 or 2) |
07-00 | J | Binary | When the dcdefchk command is executed | N |
| 8 | FIL event trace information file | $DCDIR/spool/dcfilinf/_fl_NNN (NNN: 001-003) |
07-03 | D, F, H | Binary | When 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 value | NE |
| 9 | Core file for jnlchgfg command | $DCDIR/spool/dcjnlinf/errinf/chgfg_N (N: PID of the command that shut down) |
07-03 | A | Binary | When the jnlchgfg command terminates abnormally | NE |
| 10 | Core file for jnlcuef process | $DCDIR/spool/dcjnlinf/errinf/cuef_N (N: PID of the process that shut down) |
07-03 | A | Binary | When the internal command's process terminates abnormally | NE |
| 11 | Invalid journal information file for journal file | $DCDIR/spool/dcjnlinf/errinf/cuef_N (N: PID of the command process that detected the invalid journal) |
07-03 | A | Binary | When the jnlunlfg, jnlchgfg, or jnlls command detects an invalid journal | NE |
| 12 | Core file for jnlls command | $DCDIR/spool/dcjnlinf/errinf/ls_N (N: PID of the command that shut down) |
07-03 | A | Binary | When the jnlls command terminates abnormally | NE |
| 13 | Invalid journal information file for archive-journal source node | $DCDIR/spool/dcjnlinf/errinf/r_N (N: Generation number of the journal that contains invalid data) |
Initial | J | Text | When OpenTP1 is re-run and an error is detected in a loaded block | N |
| 14 | Core file for jnlunlfg command | $DCDIR/spool/dcjnlinf/errinf/unlfg_N (N: PID of the command that shut down) |
07-03 | A | Binary | When the jnlunlfg command terminates abnormally | NE |
| 15 | Journal message queue management file | $DCDIR/spool/dcjnlinf/jnlqid | Initial | J | Binary | When the journal service creates a message queue | N |
| 16 | JNL performance verification trace information file | $DCDIR/spool/dcjnlinf/prfinf/_jn_NNN (NNN: 001-256) |
07-03 | D, F, H | Binary | When Y is specified in the prf_trace operand and 00000001 or 00000002 is specified in the jnl_prf_event_trace_level operand | NE |
| 17 | Deadlock and timeout information files | $DCDIR/spool/dclckinf | Initial | B | Text | When TAM, DAM, or the dc_lck_xxx function is used and a deadlock or lock timeout occurs | NE |
| 18 | LCK performance verification trace information file | $DCDIR/spool/dclckinf/_lk_NNN (NNN: 001-256) |
07-03 | D, F, H | Binary | When transaction processing or lock processing is underway | NE |
| 19 | Socket file for the message log notification function | $DCDIR/spool/dcloginf/.logntf | 03-03 | J | Binary | When the message log notification function is used | N |
| 20 | Message log file | $DCDIR/spool/dclogN (N: 1 or 2) |
Initial | C, E, H | Text | When OpenTP1 is run | N |
| 21 | NAM event trace information file | $DCDIR/spool/dcnaminf/_nm_NNN (NNN: 001-003) |
07-02 | D, F, H | Binary | When Y is specified in the prf_trace operand and a value other than 00000000 is specified in the nam_prf_trace_level operand | NE |
| 22 | Process service event trace information file | $DCDIR/spool/dcprcinf/_pr_NNN (NNN: 001-003) |
07-02 | D, F, H | Binary | When Y is specified in the prf_trace operand while Y is specified in the prc_prf_trace operand | NE |
| 23 | prfget command inheritance file | Earlier 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 |
Initial | J | Binary | When the prfget command is executed without the -a option specified | N |
| 24 | Performance verification trace information file | Earlier 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) |
Initial | D, F, H | Binary | When OpenTP1 is run | NE |
| 25 | Lock file for RAP-processing | $DCDIR/spool/dcrapinf/RAP-processing-listener-name | Initial | J | Binary | When the remote API service starts | N |
| 26 | Invalid message file for RAP-processing | 03-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 |
Initial | J, E | Text | When an invalid message is received by the remote API service | NE |
| 27 | RTS log file | rts_log_file_name-operand-valueN (N: 1-10) Default: $DCDIR/spool/dcrtsinf/rtslogN (N: 1-10) |
07-00 | D, F, H | Binary | When RTSSUP is started with Y specified in the rts_log_file operand | NE |
| 28 | Backup file for RTS log file | rts_log_file_name-operand-valueN.bk (N: 1-10) Default: $DCDIR/spool/dcrtsinf/rtslogN.bk (N: 1-10) |
07-02 | K | Binary | When RTSSUP is started | NE |
| 29 | Server recovery journal | $DCDIR/spool/dcsjl | Initial | J | Binary | Anytime during online operation | N |
| 30 | Transaction recovery journal | $DCDIR/spool/dctjlinf | Initial | J | Binary | Anytime during online operation | N |
| 31 | Undetermined-transaction information file | $DCDIR/spool/dctrninf/file-name | Initial | B | Text | When OpenTP1 is started for re-run | NE |
| 32 | TRN 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, H | Binary | When transaction processing is underway | NE |
| 33 | TRN event trace file | $DCDIR/spool/dctrninf/trace/trnevtrN (N: 1 or 2) |
Initial | D, F, H | Binary | When an error has occurred in an XA function | N |
| 34 | Multiple-file management file (internal file) | $DCDIR/spool/dcusmctl | Initial | J | Binary | When 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 command | N |
| 35 | XAR performance verification trace information file | $DCDIR/spool/dcxarinf/_xr_NNN (NNN: 001-256) |
07-02 | D, F, H | Binary | When 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 operand | NE |
| 36 | XAR event trace information file | $DCDIR/spool/dcxarinf/trace/xarevtrN (N: 1 or 2) |
06-00 | D, F, H | Binary | When the XA resource service is used | NE |
| 37 | Backup file for XAR event trace information file | $DCDIR/spool/dcxarinf/trace/xarevtrM.bkN (M: 1 or 2, N: 1-3) |
06-00 | K | Binary | When the XA resource service is used | NE |
| 38 | Error log information | $DCDIR/spool/errlog/errlogN (N: 1 or 2) |
Initial | C, E, H | Text | When OpenTP1 is run | N |
| 39 | Directory for system internal lock control | $DCDIR/spool/olkfifs | Initial | J | Text | When the dcmakeup command is executed or when OpenTP1 starts | N |
| 40 | Directory for system internal synchronization control | $DCDIR/spool/olkrsfs | Initial | J | Text | When the dcmakeup command is executed or when OpenTP1 starts | N |
| 41 | Control file for resources for internal control (FIFO file) | $DCDIR/spool/oslcntl | Initial | J | Binary | When the dcmakeup command is executed or when OpenTP1 starts | N |
| 42 | RPC log file | $DCDIR/spool/rpclogN (N: 1 or 2) |
Initial | C, E, H | Text | When a communication error (including internal communications) occurs | N |
| 43 | RPC trace file | rpc_trace_name-operand-value Default: $DCDIR/spool/rpctrN (N: 1 or 2) |
Initial | C, E, H | Binary | When the dc_rpc_call or dc_rpc_call_to function is issued | Y |
| 44 | Backup file for FIL event trace information file | $DCDIR/spool/save/_fl_MMM.bkN (MMM: 001-003, N: 1 or 2) |
07-03 | K | Binary | When OpenTP1 is shut down | NE |
| 45 | Backup file for JNL performance verification trace information file | $DCDIR/spool/save/_jl_MMM.bkN (MMM: 001-256, N: 1 or 2) |
07-03 | K | Binary | When OpenTP1 is shut down | NE |
| 46 | Backup file for LCK performance verification trace information file | $DCDIR/spool/save/_lk_MMM.bkN (MMM: 001-256, N: 1 or 2) |
07-03 | K | Binary | When OpenTP1 is shut down | NE |
| 47 | Backup file for NAM event trace information file | $DCDIR/spool/save/_nm_MMM.bkN (MMM: 001-003, N: 1 or 2) |
07-02 | K | Binary | When OpenTP1 is shut down | NE |
| 48 | Backup file for process service event trace information file | $DCDIR/spool/save/_pr_MMM.bkN (MMM: 001-003, N: 1 or 2) |
07-02 | K | Binary | When OpenTP1 is shut down | NE |
| 49 | Backup 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 |
K | Binary | When OpenTP1 is shut down | NE |
| 50 | Backup file for XAR performance verification trace information file | $DCDIR/spool/save/_xr_MMM.bkN (MMM: 001-256, N: 1 or 2) |
07-02 | K | Binary | When OpenTP1 is shut down | NE |
| 51 | Core file | prc_coresave_path-operand-value/server-nameN (N: 1-3) Default: $DCDIR/spool/save/server-nameN (N: 1-3) |
Initial | C, H | Binary | When the process is shut down# | NE |
| 52 | OpenTP1 debug information file | prc_coresave_path-operand-value/server-nameN.deb (N: 1-3) Default: $DCDIR/spool/save/server-nameN.deb (N: 1-3) |
Initial | C, H | Text | When the process is shut down# | NE |
| 53 |
|
$DCDIR/spool/save/dcmtrdpN, dcmtrdpl (N: 1 or 2) |
Initial | C, E, H | Binary | When OpenTP1 is run | N |
| 54 | Backup file for performance verification trace information file | Earlier 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-00 | K | Binary | When OpenTP1 is shut down | NE |
| 55 | Schedule queue information file | $DCDIR/spool/scdqidN (N: 1 or 2) |
Initial | C, E, H | Binary | When the queue-receiving server is started, terminated, shut down, or released from shutdown | N |
| 56 | Shared 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) |
Initial | L | Binary | When a file name is omitted in the argument during execution of the usmdump command | Y |
| 57 | Shared 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) |
Initial | E | Binary | When the system is shut down and when the dcstop command is executed with the -f and -d options specified | NE |
| 58 | Transaction control object | $DCDIR/spool/trnrmcmd/userobj | Initial | J | Binary | When the dcsetup, trnlnkrm, or trnmkobj command is executed | NY |
| 59 | Shared memory information file | $DCDIR/tmp/dcommenv | Initial | J | Binary | When OpenTP1 starts | N |
| 60 | Resources for internal control (FIFO file) | $DCDIR/tmp/olkmsg | Initial | J | Text | When namedpipe is specified in the schedule_method operand in the user service default definition or user service definition | N |
| 61 | jnlcolc command inheritance file | current-path-where-jnlcolc-command-executed/jnlcolcNNN (NNN: 001-999) |
Initial | J | Binary | When the jnlcolc command is executed without the -l option specified | Y |
| 62 | Backup file for jnlcolc command inheritance file | current-path-where-jnlcolc-command-executed/jnlcolcNNN.bak (NNN: 001-999) |
Initial | J | Binary | When the jnlcolc command is executed without the -l option specified and the specified inheritance file already exists | Y |
| 63 | jnlrput command inheritance file | current-path-where-jnlrput-command-executed/jnlrputNNN (NNN: 001-999) |
Initial | J | Binary | When the jnlrput command is executed with the -e option specified and the -l option omitted | Y |
| 64 | Backup file for jnlrput command inheritance file | current-path-where-jnlrput-command-executed/jnlrputNNN.bak (NNN: 001-999) |
Initial | J | Binary | When the following conditions are met:
|
Y |
| 65 | Current work path control file 2 | UNIX version: current-work-path/.dcdir_path Windows version: current-work-path/dcdir_pat |
UNIX version: 06-02 Windows version: 07-00 |
J | Binary | When prcd starts (not when the dcstart command is executed) | N |
| 66 | Work file for dcrasget command | target-directory/work | UNIX version: 06-01 Windows version: 06-50 |
J | Binary | When the dccspool command is executed | AD (dcrasget) |
![[Figure]](FIGURE/ZUENG030.GIF)
The -f and -d options are specified in the dcstop command. 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. | Name | Related definition | Size | Max files | Description |
|---|---|---|---|---|---|
| 1 | Audit log file | <Log service definition>
<User service default definition>
|
log_audit_size operand value | 1 generation | This 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. |
| 2 | Backup file for audit log file | Same as for audit log file (No. 1) | log_audit_size operand value | The maximum value is the log_audit_count operand value - 1 generation | This is a backup file for the audit log file. |
| 3 | OpenTP1 automatic start checking file | None | Several bytes (fixed) | 1 file | This file is used to control OpenTP1 operation. |
| 4 | Current work path control file 1 | None | Several bytes (variable) | 1 file | This file is used to control OpenTP1 operation. |
| 5 | prcd port information storage file | None | Several bytes (fixed) | 1 file | This file is used to control OpenTP1 operation. |
| 6 | Command log | None | 1024 kilobytes | 2 generations | This 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 |
|
None | 64 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. |
| 8 | FIL event trace information file | <System common definition>
|
Maximum 1 megabyte | 3 generations | This 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. |
| 9 | Core file for jnlchgfg command | None | Size of memory used for process#1 | Monotonic increase | This is a core file of the jnlchgfg command. It is acquired when the jnlchgfg command terminates abnormally. |
| 10 | Core file for jnlcuef process | None | Size of memory used for process#1 | Monotonic increase | This is a core file of the jnlcuef process. It is acquired when the jnlcuef process terminates abnormally. |
| 11 | Invalid journal information file for journal files | <System journal service definition>
|
jnl_max_datasize operand value | Monotonic increase | This is an invalid journal information file for journal files. It is acquired when the jnlls command detects an invalid journal. |
| 12 | Core file for jnlls command | None | Size of memory used for process#1 | Monotonic increase | This is a core file of the jnlls command. It is acquired when the jnlls command terminates abnormally. |
| 13 | Invalid journal information file for archive-journal source node | <System journal service definition>
|
jnl_max_datasize operand value | jnl_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 |
| 14 | Core file for jnlunlfg command | None | Size of memory used for process#1 | Monotonic increase | This is a core file of the jnlunlfg command. It is acquired when the jnlunlfg command terminates abnormally. |
| 15 | Journal message queue management file | <System journal service definition>
|
|
1 file | This file is used to control OpenTP1 operation. |
| 16 | JNL performance verification trace information file | <System common definition>
|
prf_file_size operand value | prf_file_count operand value | This 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. |
| 17 | Deadlock and timeout information files | <Lock service definition>
|
Several kilobytes (variable) | Variable | These 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. |
| 18 | LCK performance verification trace information file | <System common definition>
|
prf_file_size operand value | prf_file_count operand value | This 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. |
| 19 | Socket file for message log notification function | <Log service definition>
|
0 | 1 file | This is a socket file used by the message log notification function. |
| 20 | Message log file | <Log service definition>
|
log_filesize operand value | 2 generations | This is an OpenTP1 message log file. |
| 21 | NAM event trace information file | <System common definition>
|
Maximum 10 megabytes | 3 generations | This 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. |
| 22 | Process service event trace information file | <System common definition>
|
Maximum 1 megabyte | 3 generations | This 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. |
| 23 | prfget command inheritance file | None | 128 bytes | Earlier 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. |
| 24 | Performance verification trace information file | <System common definition>
|
prf_file_size operand value | Earlier 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. |
| 25 | Lock file for RAP-processing | None | 16 bytes x (1 + number of RAP-processing servers) | Number of RAP-processing listeners | This file is used to control OpenTP1 operation. It is a lock file used to synchronize the RAP-processing listener and server. |
| 26 | Invalid message file for RAP-processing | None | 03-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.#3 | This is a troubleshooting file that is created when an invalid message is received by the API service. |
| 27 | RTS log file | <Real-time statistics service definition>
|
Maximum value is the rts_log_file_size operand value | rts_log_file_count operand value | This 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. |
| 28 | Backup file for RTS log file | Same as for the real-time statistics (RTS) log file (No. 27) | Maximum value is the rts_log_file_size operand value | rts_log_file_count operand value x 1 generation | This 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. |
| 29 | Server recovery journal | None | Several bytes to kilobytes (variable) | Variable | This file is used to acquire various types of journal information for each system service. |
| 30 | Transaction recovery journal | None | Several bytes to kilobytes (variable) | Variable | This file is used to acquire various types of journal information related to transactions for each transaction branch (UAP process). |
| 31 | Undetermined-transaction information file | <Transaction service definition>
|
Several kilobytes (Monotonic increase) | Variable | This 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. |
| 32 | TRN event trace information file (PRF trace) | <System common definition>
|
prf_file_size operand value | prf_file_count operand value | This 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. |
| 33 | TRN event trace file | None | 1024 kilobytes | 2 generations | This is a TRN event trace file. It is used to acquire trace information related to transaction processing. Its contents are not disclosed. |
| 34 | Multiple-file management file (internal file) | None | 16 bytes | 1 file | This file is used to control OpenTP1 operation. It is a generation management file for recording the current generation of shared-memory dump files. |
| 35 | XAR performance verification trace information file | <System common definition>
|
prf_file_size operand value | prf_file_count operand value | This 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. |
| 36 | XAR event trace information file | <Transaction service definition>
|
xar_eventtrace_record operand value x 224 + 8 | 2 generations | This is an XAR event trace information file. XAR event trace information is acquired when Y is specified in the trn_xar_use operand. |
| 37 | Backup file for XAR event trace information file | Same as for the XAR event trace information file (No. 36) | xar_eventtrace_record operand value x 224 + 8 | 2 x 3 generations | This is a backup file of the XAR event trace information file. |
| 38 | Error log information | None | Earlier than 06-01: 64 kilobytes 06-01 or later: 1 megabyte |
2 generations | This is internal trace information for OpenTP1. Its contents are not disclosed. |
| 39 | Directory for system internal lock control | <Process service definition>
|
0 | prc_process_count operand value x 2 | This file is used to control OpenTP1 operation. |
| 40 | Directory for system internal synchronization control | <Process service definition>
|
0 | prc_process_count operand value + 83 | This file is used to control OpenTP1 operation. |
| 41 | Control file for resources for internal control (FIFO file) | None | 32 bytes (32 or 64 bits) | 1 file | This file is used to control OpenTP1 operation. |
| 42 | RPC log file | None | 1 megabyte | 2 generations | This is communication trace information for checking design. |
| 43 | RPC trace file | <System common definition>
|
Maximum value is the rpc_trace_size operand value | 2 generations | This 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. |
| 44 | Backup file for FIL event trace information file | Same as for the FIL event trace information file (No. 8) | Maximum 1 megabyte | 3 x 2 generations | This 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. |
| 45 | Backup file for JNL performance verification trace information file | Same as for the JNL performance verification trace information file (No. 16) | prf_file_size operand value | prf_file_count operand value x 2 generations | This 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. |
| 46 | Backup file for LCK performance verification trace information file | Same as for the LCK performance verification trace information file (No. 18) | prf_file_size operand value | prf_file_count operand value x 2 generations | This 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. |
| 47 | Backup file for NAM event trace information file | Same as for the NAM event trace information file (No. 21) | Maximum 10 megabytes | 3 x 2 generations | This 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. |
| 48 | Backup file for process service event trace information file | Same as for the process service event trace information file (No. 22) | Maximum 1 megabyte | 3 x 2 generations | This 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. |
| 49 | Backup 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 value | prf_file_count operand value x 2 generations | This 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. |
| 50 | Backup file for XAR performance verification trace information file | Same as for the XAR performance verification trace information file (No. 35) | prf_file_size operand value | prf_file_count operand value x 2 generations | This 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. |
| 51 | Core file | <Process service definition>
<User service default definition>
|
Amount of memory used for process#1 | 3 generations | This 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. |
| 52 | OpenTP1 debug information file | <Process service definition>
|
Variable | 3 generations | This is a debugging information file for system and user servers that have been shut down. |
| 53 | Trace information dump file | None | 64 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. |
| 54 | Backup file for performance verification trace information file | Same as for the performance verification trace information file (No. 24) | prf_file_size operand value | Earlier 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:
|
| 55 | Schedule queue information file | <Schedule service definition>
|
(scd_server_count operand + 4) x 16 + 32 (bytes, maximum) | 2 generations | This file is used to control OpenTP1 operation. |
| 56 | Shared memory dump file | None | Depends on the machine status and OpenTP1 system operating status | 1 generation#4 | This is a dump of the shared memory allocated by OpenTIP1. |
| 57 | Shared memory dump file | None | Depends on the machine status and OpenTP1 system operating status | 3 generations#4 | This is a dump of the shared memory allocated by OpenTIP1. |
| 58 | Transaction control object | None | Several to dozens of kilobytes (variable) | 1 or more files | This 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. |
| 59 | Shared memory information file | None | 544 bytes (32 or 64 bits) | 1 file | This file is used to control OpenTP1 operation. |
| 60 | Resources for internal control (FIFO file) | <Schedule service definition>
|
0 | scd_server_count operand value | This file is used to control OpenTP1 operation. |
| 61 | jnlcolc command inheritance file | None | Depends on the size of recovery journal to be extracted | 1 file | This 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. |
| 62 | Backup file for jnlcolc command inheritance file | None | Size of the inheritance file before renaming | 1 file | This 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. |
| 63 | jnlrput command inheritance file | None | Depends on the size of the transaction-undetermined UJ | 1 file | This 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. |
| 64 | Backup file for jnlrput command inheritance file | None | Size of the inheritance file before renaming | 1 file | This 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. |
| 65 | Current work path control file 2 | None | Depends on DCDIR | 1 file | This file is used to control OpenTP1 operation. |
| 66 | Work file for dcrasget command | None | Depends on the information to be collected | Depends on the information to be collected | This file is used to control OpenTP1 operation. |
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. | Name | File name or directory name | Version | Type | File format | Acquisition timing | Deletable |
|---|---|---|---|---|---|---|---|
| 1 | Communication control file | $DCDIR/.tact/* | Initial | J | Local socket | When a process is started | N |
| 2 | Backup file for inittab | $DCDIR/conf/Inittab/inittabN (N: 1-3) |
Initial | K | Text | When dcsetup command is executed | Y |
| 3 | Control file for dccspool | $DCDIR/spool/.dccspool_time | 06-02 | J | Null | When dccspool command is executed | AD (dccspool) |
| 4 | Pipe file for prctee | $DCDIR/spool/.prc_fifo | 05-00 | J | Binary | When prctee command is started | N |
| 5 | PID storage file for prctee process | $DCDIR/spool/.prc_tee | Initial | J | Binary | When prctee command is started | N |
| 6 | prctee process start error output file | $DCDIR/spool/.prcerr.log | 07-00 | A | Text | When prctee command startup fails | NE |
| 7 | PAUSE checking file for prcd | $DCDIR/spool/.prcnopause | Initial | J | Binary | When OpenTP1 starts | N |
| 8 | PID storage file for Linux prcd | $DCDIR/spool/.prcpid | 06-00 | J | Binary | When prcd starts (not when dcstart command is executed) | N |
| 9 | prctee process error output file | $DCDIR/spool/.prctee.log | 07-00 | A | Text | When an output error occurs on betarn.log | NE |
| 10 | Archive-journal source node connection information file | $DCDIR/spool/dcjnlinf/coninf | Initial | J | Text | When connection is established with or released from the archive journal node | NE |
| 11 | Archive journal node connection information file | $DCDIR/spool/dcjnlinf/coninf | Initial | J | Text | When connection is established with or released from the archive-journal source node | NE |
| 12 | Invalid 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) |
Initial | J | Text | When OpenTP1 is re-run and an error is detected in a loaded block | N |
| 13 | Invalid journal information file for archive journal file | $DCDIR/spool/dcjnlinf/errinf/cuef_N (N: PID of the command that was shut down) |
07-03 | A | Binary | When the jnlunlfg, jnlchgfg, or jnlls command detects an invalid journal | NE |
| 14 | GWF log file | $DCDIR/spool/gwflogN (N: 1 or 2) |
Initial | C, E, H | Text | When a gateway service-related internal function returns control with an error | N |
| 15 | UAP trace edit/output file | prc_coresave_path-operand-value/server-nameN.uat (N: 1-3) Default: $DCDIR/spool/save/server-nameN.uat (N: 1-3) |
Initial | C, H | Text | When the process is shut down# | NE |
| 16 | Backup 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-03 | K | Binary | When the user server is shut down or when OpenTP1 starts | NE |
| 17 | Backup 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-03 | K | Binary | When the user server is shut down or when OpenTP1 starts | NE |
| 18 | PID file for prcd management process | $DCDIR/tmp/home/server-name/.prc.PID | Initial | J | Null | When each process is started | N |
| 19 | UAP trace data file | $DCDIR/tmp/home/server-name.ID/dcuat.map | 07-03 | C | Binary | When a UAP process is started | NE |
| 20 | Module trace data file | $DCDIR/tmp/home/server-name.XX/dcumt.map (XX: Serial number) |
07-03 | C | Binary | When a process is started | NE |
| 21 | DCDIR management information in the same machine | Linux version: /opt/OpenTP1/etc/.OpenTP1 AIX or HI-UX/WE2 version: /usr/etc/BeTRAN |
Initial | J | Text | When dcsetup command is executed | N |
| 22 | DCDIR management shell in the same machine | Linux version: /opt/OpenTP1/etc/dcpwon AIX or HI-UX/WE2 version: /usr/bin/dcpwon |
Initial | J | Text | When dcsetup command is executed | N |
| 23 | Communication control file | 1. 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 |
J | Local socket | When a process is started | N |
| 24 | Backup file for dcsetup | /tmp/.admdPID/* | Initial | J | Text | When dcsetup command is executed | AD (dcsetup) |
| 25 | Realtime 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. |
Initial | A | Text | When OpenTP1 is run | N |
| 26 | Temporary file used during execution of namdomainsetup command | /tmp/TP1dmfilwork(PID) | Initial | J | Text | When namdomainsetup command is executed | AD (namdomainsetup) |
| 27 | Lock file for dcsetup | Linux version: /var/spool/.OpenTP1.HiRDB/.lock AIX or HI-UX/WE2 version: /usr/spool/.OpenTP1.HiRDB/.lock |
Initial | J | Binary | When dcsetup command is executed | N |
| 28 | Temporary file used during execution of jnlsort command | current-path-where-jnlsort-command-executed/sort_I + process-ID current-path-where-jnlsort-command-executed/sort_o + process-ID |
Initial | J | Text | When jnlsort command is executed with the -g option omitted | AD (jnlsort) |
The -f and -d options are specified in the dcstop command. 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. | Name | Related definition | Size | Max files | Description |
|---|---|---|---|---|---|
| 1 | Communication control file | None | Communication message size | Number of active processes | This file is used when communication is performed on the local machine. |
| 2 | Backup file for inittab | None | Size of /etc/inittab file | 3 generations | This is a backup file for the /etc/inittab file. |
| 3 | Control file for dccspool | None | 0 | 1 file | This file is used to control OpenTP1 operation. |
| 4 | Pipe file for prctee | None | Several bytes (fixed) | 1 file | This file is used to control OpenTP1 operation. |
| 5 | PID storage file for prctee process | None | Several bytes (fixed) | 1 file | This file is used to control OpenTP1 operation. |
| 6 | prctee process start error output file | None | Monotonic increase | 1 file | This file is used to output prcd information in the event of a prctee process start error. |
| 7 | PAUSE checking file for prcd | None | Several bytes (fixed) | 1 file | This file is used to control OpenTP1 operation. |
| 8 | PID storage file for Linux prcd | None | Several bytes (fixed) | 1 file | This file is used to control OpenTP1 operation. |
| 9 | prctee process error output file | None | Monotonic increase | 1 file | This file is used to output information about output errors on betran.log. |
| 10 | Archive-journal source node connection information file | <Global archive journal service definition>
|
124 bytes | Number of resource groups specified in -a option of jnldfsv definition command in the global archive journal service definition | This 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. |
| 11 | Archive journal node connection information file | None | 124 bytes x number of archive-journal source nodes to be connected to the archive journal node | Number of archive-journal source nodes to be connected to the archive journal node | This 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. |
| 12 | Invalid journal information file for archive journal node | <Archive journal service definition>
|
jnl_arc_max_datasize operand value | For 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).# |
| 13 | Invalid journal information file for archive journal file | <Global archive journal service definition>
|
jnl_arc_max_datasize operand value | Monotonic increase | This is an invalid journal information file for the archive journal file. It is acquired when the jnlls command detects an invalid journal. |
| 14 | GWF log file | None | 0.1 megabytes | 2 generations | This 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. |
| 15 | UAP trace edit/output file | <Process service definition>
|
Variable | 3 generations | This is a UAP trace information file for system and user servers that have been shut down. |
| 16 | Backup file for UAP trace data file | <User service definition> <User service default definition> <System common definition> <Individual system service definition>
|
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. |
| 17 | Backup file for module trace data file | <User service definition> <User service default definition> <System common definition> <Individual system service definition>
|
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. |
| 18 | PID file for prcd management process | None | 0 | As many as the number of processes | This file is used to control OpenTP1 operation. |
| 19 | UAP trace data file | <User service definition> <User service default definition> <System common definition> <Individual system service definition>
|
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 generation | This is a source data file for the UAP trace edit/output file to which UAP trace information for system and user servers is output. |
| 20 | Module trace data file | <User service definition> <User service default definition> <System common definition> <Individual system service definition>
|
32-bit version: 4096 bytes (for the process server, 73696 bytes) 64-bit version: 6128 bytes (for the process server, 110528 bytes) |
1 generation | This is a source data file for the module trace edit/output file to which module trace information for system and user servers is output. |
| 21 | DCDIR management information in the same machine | None | Depends on DCDIR registered in the same machine | 1 file | This file is used to control OpenTP1 operation. |
| 22 | DCDIR management shell in the same machine | None | Depends on DCDIR registered in the same machine | 1 file | This file is used to control OpenTP1 operation. |
| 23 | Communication control file | <System common definition>
|
Communication message size | Number of active processes | This file is used when communication is performed on the local machine. |
| 24 | Backup file for dcsetup | None | Depends on length of DCDIR and size of /etc/inittab | 12 files | This file is used to control OpenTP1 operation. |
| 25 | Realtime output function (betran.log) | None | Monotonic 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. |
| 26 | Temporary file used during execution of namdomainsetup command | None | Size equivalent to number of lines in the hosts file of host names that were specified in the domain data file | 1 file | This 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. |
| 27 | Lock file for dcsetup | None | 0 | 1 file | This file is used to control OpenTP1 operation. |
| 28 | Temporary file used during execution of jnlsort command | None |
|
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. |
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. | Name | File name or directory name | Version | Type | File format | Acquisition timing | Deletable |
|---|---|---|---|---|---|---|---|
| 1 | Patch log file | TP1/Server Base: %DCDIR%\patchlogbase.txt DAM: %DCDIR%\patchlogdam.txt TAM: %DCDIR%\patchlogtam.txt EXT1: %DCDIR%\patchlogext1.txt HAF: %DCDIR%\patchloghaf.txt |
07-00 | A | Text | Acquired at the extension of patch execution | NE |
| 2 | prctee process error output file | %DCDIR%\spool\betran.err | 05-00-/E | A | Text | When OpenTP1 starts | N |
| 3 | Lock file for raw device | %DCDIR%\spool\dcntbinf\rawlock_N (N: Drive letter) |
06-50 | J | Null | When raw device is opened for the first time | N |
| 4 | Backup module (UMT) trace file | %DCDIR%\spool\save\trc\_zx.umt (z: server name of 1-8 characters, x: serial number) |
Initial | I | Binary | When OpenTP1 starts | Y |
| 5 | Backup UAP trace file | %DCDIR%\spool\save\trc\server-nameN.uat (N: 1-10) |
Initial | C, I | Binary | When a process is shut down# and when OpenTP1 starts | NE |
| 6 | Shared memory file | %DCDIR%\spool\shm\N (N: numeric character beginning at 1) |
Initial | J | Binary | When OpenTP1 starts. The next time online operation begins, the file is deleted and then re-created. | N |
| 7 | Lock file for GUI | %DCDIR%\tp1_tools\Control.lck %DCDIR%\tp1_tools\Environment.lck |
06-50 | J | Null | When the GUI function is used. The file is deleted when the GUI function is terminated. | N |
| 8 | admshowpp log file | %temp%\admshowpp.log | 07-01 | J | Text | Acquired at the extension of the dcsetup command | N |
| 9 | dcsetup log file | %temp%\dcsetup.log | Initial | A | Text | Acquired at the extension of the installer and patch operation | NE |
| 10 | dcsetupml log file | %temp%\dcsetupml.log | 06-50 | A | Text | Acquired at the extension of the dcsetupml command and installer operation | NE |
| 11 | trnlnkrm log file | %temp%\trnlnkrm.log | Initial | A | Text | Acquired at the extension of the trnlnkrm command execution, dcsetupml command execution, installer operation, and patch operation | NE |
| 12 | Standard output redirect file | redirect_file_name-operand-valueN (N: 1 or 2) Default: %DCDIR%\spool\prclogN (N: 1 or 2) |
05-00-/E | C, E, H | Text | When OpenTP1 is run | Y |
| 13 | UAP trace file | current-work-path\tmp\home\_z.x\_zPPPPP.uat (z: server name of 1-8 characters, PPPPP: PID, x: serial number) |
Initial | I | Binary | Created at the extension of the user server startup | Y |
| 14 | Module (UMT) trace file | current-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) |
Initial | I | Binary | Created at the extension of the OpenTP1 startup and user server startup | Y |
The -f and -d options are specified in the dcstop command. 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. | Name | Related definition | Size | Max files | Description |
|---|---|---|---|---|---|
| 1 | Patch log file | None | Monotonic 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. |
| 2 | prctee process error output file | None | Monotonic increase | 1 file | This file is used to output prctee process error information. |
| 3 | Lock file for raw device | None | 0 | Number of raw devices used | This file is used to control OpenTP1 operation. It is an internal file created when a raw device is used for the OpenTP1 file system. |
| 4 | Backup module (UMT) trace file | None | 4160 bytes (for a process server, 73696 bytes) | 10 generations x number of active servers | This is a backup file for the module (UMT) trace file. |
| 5 | Backup UAP trace file | None | Variable | 10 generations | This is a UAP trace information file for system and user servers that have been shut down. |
| 6 | Shared memory file | None | Depends on the machine status and OpenTP1 system operating status | 1 generation | This file is used to control OpenTP1 operation. It is a shared memory file allocated by OpenTP1. |
| 7 | Lock file for GUI | None | 0 | 2 files | This file is used to control OpenTP1 operation. It is created to prevent duplicate startup when OpenTP1's GUI function is used. |
| 8 | admshowpp log file | None | During normal operation: 0 bytes In event of an error: Size varies This file is overwritten each time a command is executed. |
1 generation | This 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. |
| 9 | dcsetup log file | None | Monotonic increase This file is overwritten each time a command is executed. |
1 generation | This is a trace file for the dcsetup command. It is acquired at the extension of the installer operation and patch operation. |
| 10 | dcsetupml log file | None | Monotonic increase This file is overwritten each time a command is executed. |
1 generation | This is a trace file for the dcsetup command. It is acquired at the extension of dcsetupml command execution and installer operation. |
| 11 | trnlnkrm log file | None | Monotonic increase This file is overwritten each time a command is executed. |
1 generation | This 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. |
| 12 | Standard output redirect file | <System environment definition>
|
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. |
| 13 | UAP trace file | <User service definition> <User service default definition>
|
Variable | 1 generation x number of active servers | This is a UAP trace file for a process during online operation. |
| 14 | Module (UMT) trace file | None | 4160 bytes (for a process server, 73696 bytes) | 1 generation x number of active servers | This is a module (UMT) trace file for a process during online operation. |
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. | Name | File name or directory name | Version | Type | File format | Acquisition timing | Deletable |
|---|---|---|---|---|---|---|---|
| 1 | damd life checking file | $DCDIR/tmp/damlive | Initial | J | Binary | When damd is started | N |
| 2 | Temporary file during logical file recovery | damfrc-command-execution-directory/.dcdamPPPPPPP (PPPPPPP: last 7 digits of PID) |
Initial | J | Binary | When the damfrc command is executed with the -c option omitted and an online backup file specified | AD (damfrc) |
| 3 | Temporary file during acquisition of online DAM backup | dambkup--o--s-execution-directory/bkTTTTPPPP (TTTT: last 4 digits of the total time in seconds PPPP: last 4 digits of the process ID) |
Initial | J | Binary | When the dambkup command is executed with the -o and -s options specified | AD (damfrc) |
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. | Name | Related definition | Size | Max files | Description |
|---|---|---|---|---|---|
| 1 | damd life checking file | None | 136 bytes | 1 file | This file is used to control OpenTP1 operation. It determines whether damd is running. |
| 2 | Temporary file during logical file recovery | None | 96 bytes | 1 file | This 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. |
| 3 | Temporary file during acquisition of online DAM backup | None | Size of DAM file that is to be backed up + 128 bytes | 1 file | This 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. |
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. | Name | File name or directory name | Version | Type | File format | Acquisition timing | Deletable |
|---|---|---|---|---|---|---|---|
| 1 | Temporary file during acquisition of online TAM backup | $DCDIR/tmp/.dctamdN (N: 1-9999999) |
Initial | J | Binary | When tambkup command is executed with -o operand specified | AD (tambkup) |
| 2 | Shared memory information file (for TAM) | $DCDIR/tmp/tammemfile | Initial | J | Binary | When OpenTP1 starts | N |
| 3 | Temporary file during logical file recovery | tamfrc-command-execution-directory/.dctamPID | Initial | J | Binary | When tamfrc command is executed with -j option omitted and an online backup file specified | AD (tamfrc) |
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. | Name | Related definition | Size | Max files | Description |
|---|---|---|---|---|---|
| 1 | Temporary file during acquisition of online TAM backup | None | Size of TAM file to be backed up | 1 file | This 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. |
| 2 | Shared memory information file (for TAM) | None | 4 bytes | 1 file | This file is used to control OpenTP1 operation. |
| 3 | Temporary file during logical file recovery | None | 96 bytes | 1 file | This 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. |
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. | Name | File name or directory name | Version | Type | File format | Acquisition timing | Deletable |
|---|---|---|---|---|---|---|---|
| 1 | XATMI send data file | $DCDIR/spool/uto/test-user-ID/user-service-name/xsdservice-name | Initial | J | Binary | When a client's XATMI request made by the tpsend function is accepted | Y |
| 2 | MCF send message file | $DCDIR/spool/uto/test-user-ID/user-service-name/sendmsg | Initial | J | Binary | When a client's request made by an MCF function listed in Table F-12 is accepted | Y |
| 3 | UTO trace file | $DCDIR/spool/uto/test-user-ID/traceN (N: 1 or 2) |
Initial | C, E, H | Binary | When an online tester is used to check UAP operation | Y |
| 4 | Temporarily stored data file | $DCDIR/spool/uto/test-user-ID/utotmplogical-terminal-name | Initial | J | Binary | When temporarily stored data is received from a client by issuing the dc_mcf_tempput function | Y |
| 5 | Test data definition file | File 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:
|
Initial | J | Binary | When the utofilcre command is executed | Y |
| 6 | MCF receive message file (there are asynchronous and synchronous files) | File path specified in r option of utomsgout command | Initial | J | Binary | When the utomsgout command is executed with the -r operand specified | Y |
| 7 | RPC response data file | File path specified for the RPC response data file name in the utosppsvc command | Initial | J | Binary | When the utosppsvc command is executed with the RPC response data file name specified | Y |
| 8 | UTO trace merge file | File path specified in -o option of utotrcmrg command | Initial | J | Binary | When the utotrcmrg command is executed with the -o operand specified | Y |
| 9 | XATMI response data file | File path specified for the XATMI response data file name in the utoxsppsvc command | Initial | J | Binary | When the utoxsppsvc command is executed with the XATMI response data file name specified | Y |
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. | Name | Related definition | Size | Max files | Description |
|---|---|---|---|---|---|
| 1 | XATMI 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 bytes | 1 file for each set of a test user ID, user server name, and service name | This is an XATMI send data file. When a client issues the tpsend function, the send data is stored in this file. |
| 2 | MCF send message file | <Tester service definition>
|
max_message_file_size operand value | 1 file for each test user ID | This file stores MCF send messages. When the MCF simulation function is used, this file stores send messages when the following functions are issued:
|
| 3 | UTO trace file | <Tester service definition>
|
max_trace_file_size operand value | 2 generations | This is a UTO trace file. It is used to collect UAP trace information. |
| 4 | Temporarily 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 bytes | 1 file for each set of a test user ID and utotmp logical terminal name | This 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 |
|
None | Any size | 1 file | This is a test data definition file used by the online tester. |
| 6 | MCF receive message file (there are asynchronous and synchronous files) | None | Any size | 1 file | This 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.
|
| 7 | RPC response data file | None | Any size | 1 file | This 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. |
| 8 | UTO trace merge file | None | Total size of files specified for trace file names | 1 file | This is a UTO trace merge file. It is created when the utotrcmrg command is used to merge multiple UTO trace files into one file. |
| 9 | XATMI response data file | Overall typed buffer definition | Undefined because the file is created on the basis of the typed buffer definition file and XATMI request data file | 1 file | This is an XATMI response data file. It is used as the receive data during service execution and as the response data after service execution. |
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. | Name | File name or directory name | Version | Type | File format | Acquisition timing | Deletable |
|---|---|---|---|---|---|---|---|
| 1 | Backup file for system service common information definition file | $DCDIR/.mcfdef/mcf | 05-05 | K | Text | When the dcsetup command is executed with the -d operand specified | N |
| 2 | Backup file for system service information definition file | $DCDIR/.mcfdef/mcfu* | 05-05 | K | Text | When the dcsetup command is executed with the -d operand specified | N |
| 3 | Backup file for executable MCF communication server program | $DCDIR/.mcfserv/mcfu* | 05-05 | K | Binary | When the dcsetup command is executed with the -d operand specified | N |
| 4 | MCF dump file#1 | $DCDIR/spool/mcfdKAXXZZ (K: process identifier, AXX: MCF identifier, ZZ: 01-99) |
Initial | H, I | Binary | When an error (such as an internal conflict) is detected in TP1/Message Control or TP1/Messaging | NE |
| 5 | MCF trace file#1 | $DCDIR/spool/mcftAXXZZ (AXX: MCF identifier, ZZ: 01-99) |
Initial | H, I | Binary | When a trace buffer becomes full in shared memory while an MCF communication process is running | NE |
| 6 | MCF performance verification trace information file#1 | $DCDIR/spool/dcmcfinf/_mc_NNN (NNN: 000-256) |
07-01 | D, F | Binary | When a trace buffer becomes full while an MCF communication process or UAP is running | NE |
| 7 | Backup file when preparation for MCF configuration change is stopped#2 | DCMCFQUEBAK value in the system service common information definition Default: $DCDIR/spool/mcf/mcfquebak |
07-03 | K | Binary | When preparation for MCF configuration change is stopped (by executing dcstop -b -q) | Y#3 |
| 8 | Backup file for MCF performance verification trace information file#1 | $DCDIR/spool/save/_mc_MMM.bkN (MMM: 001-256, N: 1 or 2) |
07-01 | K | Binary | When OpenTP1 has stopped | NE |
| 9 | Mapping error information file#4 | $DCDIR/spool/save/dcmap_errXXX (XXX: process ID of TP1/NET/XMAP3 MCF communication process) |
Initial | H, I | Text | When an error occurs during mapping | NE |
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. | Name | Related definition | Size | Max files | Description |
|---|---|---|---|---|---|
| 1 | Backup file for system service common information definition file | System service common information definition ($DCDIR/lib/sysconf/mcf) | Size of the $DCDIR/lib/sysconf/mcf file | 1 file | This is a backup file for the system service common information definition. |
| 2 | Backup file for system service information definition file | System service information definition | Size of the system service information definition file | Number of system service information definition files | This is a backup file for the system service information definition. |
| 3 | Backup file for executable MCF communication server program | None | Size of the MCF communication process program or MCF application start process program ($DCDIR/lib/servers/mcfu*) | Number of executable MCF communication server programs | This is a backup file for the executable MCF communication server program. |
| 4 | MCF dump file#1 | None | Size 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. |
| 5 | MCF trace file#1 | <Trace definition in MCF communication configuration definition> -t option in mcfttrc definition command
Handling of the number of files |
size value x bufcnt value | When 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. |
| 6 | MCF performance verification trace information file#1 | <System common definition>
|
prf_file_size operand value | prf_file_count operand value | This 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. |
| 7 | Backup 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 file | This is a backup file for untransmitted and unprocessed messages when the MCF configuration change restart function is used. |
| 8 | Backup file for MCF performance verification trace information file#1 | Same as for MCF performance verification trace information file (No. 6) | prf_file_size operand value | prf_file_count operand value x 2 generations | This 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. |
| 9 | Mapping error information file#3 | <Mapping service attribute definition> ERRLOG4={YES|NO}
|
Depends on size of logical map area and size of physical map file | Number of MCF communication processes#4 | This file is used to acquire error information in the event of a mapping error. It is used for troubleshooting purposes. |
All Rights Reserved. Copyright (C) 2006, 2010, Hitachi, Ltd.