To estimate the size of a status file, you need to know the number of records in the target status file. To find this number, determine the number of bytes in the status file used by each key and the number of keys. Add the calculated number of records to the number of records used by other services.

Determine the number of bytes in the status file used by each key and the number keys for each archive source node, archive node, and MCF service. Specify the results in the -c option in the stsinit command for initializing a status file. Note that the calculated results indicate the minimum requirements. For safety, determine a value that is 1.2 times larger than the calculated size.

The formula for determining the number of records in a status file is as follows:

Total number of records required for all services + number of records required for managing the status file

Legend:

Number of records required for each service

Use the following formula to determine the number of records required for each service:

(Number of bytes in the status file used by each key/(record length^# - 40)) x number of keys

: Decimals are rounded up to a whole number.

Number of records required for managing the status file

Use the following formula to determine the number of records required to manage the status file:

When the record length is 512 or less

(number of records required for each service /472) + 23

When the record length is 513 or greater

(total number of records required for all services + 8776 + (8192/ (record length^# - 40)) x 16) / (record length^# - 40)

: Decimals are rounded up to a whole number.

#

Unit for record length: bytes

The following subsections indicate the number of bytes in the status file used by each key and the number of keys.

For archive source nodes

The following table shows the number of bytes in the status file used by each key and the number of keys.

Table H-1 Number of bytes in the status file used by each key of each service and the number of keys (for an archive source node)

Service	Number of bytes in the status file used by each key (Unit: bytes)	Number of keys
System manager	A x 128 + 2432	1
Schedule service	B x 144 + 128	1
Transaction journal service	2048	1
Transaction service	1280 x (number of RMs + RM extensions) + 2048	1
DAM service	(C + D) x 288 + 256	1
Message queue service	E x 120 + 36	1
	(F + G) x 40	1
	(G + H + 1) x 48	1
Journal service	8192	1
	8192	J
	17008	L
		L
Checkpoint dump service	90	L
	126	L
	32	L
TAM service	N x 136 + 64	1
Online tester	P x 160 + 132	1
Server recovery journal service	512 x Q + 128	1
IST service	V x 8	1
XA resource service	64	1

Legend:

A: Value specified in the server_count operand in the system environment definition

B: Value specified in the scd_hold_recovery_count operand in the schedule service definition

C: Total number of logical files specified in the damfile definition command in the DAM service definition

D: Value specified in the dam_added_file operand in the DAM service definition

E: Total number of physical files specified in the quegrp definition command in the message queue service definition

F: Value specified in the -g option of the mcfmexp command in the MCF manager definition

G: Value specified in the -l option of the mcfmexp command in the MCF manager definition

H: Total number of MCF communication services specified in the mcfmcname command in the MCF manager definition

J: (5 + 3 x K) / 63 - 1 ( : Decimals are rounded up to a whole number.)

K: Total number of journal file groups specified in the jnladdfg definition command in the system journal service definition

L: Total number of files containing the checkpoint dump service definition specified in jnldfsv -c in the journal service definition

M: Total number of journal file groups specified in the jnladdfg definition command in the checkpoint dump service definition

N: Value specified in the tam_max_tblnum operand in the TAM service definition

P: Value specified in the uto_server_count operand in the tester service definition

Q: Total number of files containing the checkpoint dump service definition specified in jnldfsv -c in the journal service definition

V: ((2347 + (W x Y) + (16 x Y)) / 8) ( : Decimals are truncated.)

W: Record length in each IST table specified in the IST service definition (unit: bytes)

Y: Number of records in each IST table specified in the IST service definition

For archive nodes

Table H-2 Number of bytes in the status file used by each key of each service and the number of keys (for an archive node)

Service	Number of bytes in the status file used by each key (Unit: bytes)	Number of keys
System manager	A x 128 + 2432	1
Journal service	8192	1
	8192	R

Legend:

A: Value specified in the server_count operand in the system environment definition

S: Total number of files containing the archive journal service definition specified in jnldfsv -a in the global archive journal service definition

T: Total number of journal-related file groups specified in jnladdfg in the archive journal service definition

U: Value specified in the jnl_max_file_dispersion operand in the archive journal service definition

To determine the number of records required by the MCF service, use the number of bytes in the status file used by each key and the number of keys.

The following table shows the number of bytes in the status file used by each key of the MCF service and the number of keys.

For MCF services

Table H-3 Number of bytes in the status file used by each key and the number of keys (for an MCF service)

Item	Number of bytes in the status file used by each key (Unit: bytes)		Number of keys
MCF service	L x 128		L
	224		L
	Different communication processes	80 x M / 1818 x 48	( M / 1818 ) / 1363
		80 x N / 1818 x 48	( N / 1818 ) / 1363
		MIN (48 + M x 36: 65536)	M / 1818
		MIN (48 + N x 36: 65536)	N / 1818
		80 + O / 4092 x 48	( O / 4092 ) / 1363
		80+P/4092 x48	(P / 4092) /1363
		MIN (48 + O x 36: 65536)	O / 4092
		MIN (48 + P x 36: 65536)	P / 4092
		4	1
		64	1
		48 + 1024 x Q	1

Legend:

L: Number of MCF communication service names specified in the communication service definition (mcfmcname definition command) in the MCF manager definition

M: Upper limit for the number of service groups specified in the status inheritance definition (mcfmsts definition command) in the MCF manager definition

N: Upper limit for the number of services specified in the status inheritance definition (mcfmsts definition command) in the MCF manager definition

O: Upper limit for the number of applications specified in the status inheritance definition (mcftsts definition command) in the MCF communication definition

P: Upper limit for the number of logical terminals specified in the status inheritance definition (mcftsts definition command) in the MCF communication definition

Q: Number of descriptions in the mapping service definition for the mapping service identifier corresponding to the mapping service attribute definition in which YES is specified for the PATHSTS operand

MIN(x:y): x or y, whichever is smaller

: Decimals are rounded up to whole numbers.

Note

For details about the size of the status file of the MQA service and the ISAM service, see the manual OpenTP1 TP1/Message Queue User's Guide, the manual Indexed Sequential Access Method ISAM, or the Release Notes of the applicable product, and determine the size.