The following table shows how to estimate the size of a checkpoint dump file.
Table H-7 Size of a checkpoint dump file
Item |
Size of checkpoint dump file
(Unit: bytes) |
MCF service |
( Sz1 / 4096 + 3) x 4096 |
Transaction journal service |
( Sz2 / 4096 + 3) x 4096 |
- Legend:
- : Decimals are rounded up to a whole number.
- Sz2: (640 x (rm count + 1) + 64 x Br) x Tr
- Cn: Number of logical terminals with serial numbers specified in the -n option of the mcfmcomn definition command in the MCF manager definition
- Pn: Number of physical files specified in the message queue service definition
- Pr: Number of records specified in the -n option of the queinit command
- Br: Maximum number of connection branches per transaction specified in the trn_max_subordinate_count operand in the transaction service definition
- rm count: Number of resource managers (only RMs of OpenTP1)
- Tr: Number of transaction branches specified in the trn_tran_process_count operand in the transaction service definition
Note that archive journal nodes do not require checkpoint dump files.
For details about the size of a checkpoint dump file used by TP1/Message Queue, see the manual OpenTP1 TP1/Message Queue User's Guide or the Release Note.
All Rights Reserved. Copyright (C) 2006, 2010, Hitachi, Ltd.