The static shared memory required for the MCF service is the total size of the calculation results explained in this subsection.

Add the size of the static shared memory for the MCF service to the size of the static shared memory for other OpenTP1 services, and specify the result of the addition in the static_shmpool_size operand of the system environment definition. In addition, in the -p option of the mcfmcomn definition command in the MCF manager definition, specify the total of the results of the formulas except the second formula in B.2(1)(a) MCF manager process and the second formula in B.2(1)(b) MCF communication processes and application start processes.

The following figure shows the relationship between the formula for estimating the static shared memory size for the MCF service and the value specified for the definition.

Figure B-1 Relationship between the formula for estimating the static shared memory size for the MCF service and the value specified for the definition

Explanations of items (a) through (d) in the figure follow.

(a) MCF manager process

The size of the shared memory used by the MCF manager process is the total of the results of the following two formulas. The MCF manager process uses one process in one OpenTP1 system.

Formula 1:

25000 + 19000 x A + 600 x B + 50 x C + 800 x D + 400 x E + 700 x F + 1000 x G + 96000 x H

Legend:

A: Number of MCF communication processes and application start processes (number of specified mcfmcname definition commands)

B: Total number of logical terminals (number of all mcftalcle definition commands that are specified)

C: Total number of applications (number of all mcfaalcap definition commands that are specified)

D: Number of MHP service groups

E: Total number of MHP services (total number of services in each service group)

F: Number of queue groups (number of specified mcfmqgid definition commands)

G: Number of mapping service identifiers (number of mapping service identifiers specified in the mapping service definition)

H: The value becomes 0 if 00000000 is specified in the mcf_prf_trace_level operand of the system service information definition, or if specification of this operand is omitted. If a value other than 00000000 is specified, the value of H becomes 1.

Formula 2:

7000 + 70 x A

Legend:

A: Number of logical terminals that use message sequence numbers (value specified in the -n option of the mcfmcomn definition command)

(b) MCF communication processes and application start processes

The size of the shared memory used by the MCF communication processes and application start processes is the total of the results of the following two formulas. The number of processes used by these processes is the number of mcfmcname definition commands in the OpenTP1 system.

Formula 1:

2000 + 50 x A + 2000 x B + 800 x C + 800 x D + 500 x E + 3500 x F + (100 + G) x H

Legend:

A: Number of connections (number of specified mcftalccn definition commands)

For the application start process, A is 1.

B: Number of logical terminals (number of specified mcftalcle definition commands)

C: Maximum instantaneous number of logical messages queued in all OTQs (both disk and memory queues) for the process

D: Number of applications to be started (number of specified mcfaalcap definition commands)

E: TP1/NET/OSAS-NIF: Number of relevant connections

Other protocol products: 0

F: TP1/NET/OSAS-NIF: Number of relevant logical terminals

Other protocol products: 0

G: Maximum message length in the facility for user timer monitoring (value specified in the msgsize operand of the mcfttim definition command)

H: Maximum number of timer monitoring requests (value specified in the timereqno operand of the mcfttim definition command)

Formula 2:

4500 + 2 x A

Legend:

A: MCF trace buffer size (the value of the size operand in the mcfttrc definition command)

(c) MCF online command process

The size of the shared memory used by the MCF online command process is 512 bytes. The MCF online command process uses one process when TP1/NET/XMAP3 is used. No process occurs when TP1/NET/XMAP3 is not used.

(d) MCF mapping process

The size of the shared memory used by the MCF mapping process is obtained from the following formula. The MCF online command process uses one process when TP1/NET/XMAP3 is used. No process occurs when TP1/NET/XMAP3 is not used.

700 + (2600 + 32 x (A + B) + 80 x (C + D)) + E + F + G + H + I x J + K x L

Legend:

( ): Total of the results of the expression enclosed in parentheses for each mapping attribute definition

A: Number of physical maps that are subject to residence management (number of MAPNAME entries specified in the mapping service attribute definition)

B: Number of PAGEC maps that are subject to residence management (number of PGCNAME entries specified in the mapping service attribute definition)

C: Number of physical maps that are subject to LRU management (number of MAPCNT entries specified in the mapping service attribute definition)

D: Number of PAGEC maps that are subject to LRU management (number of PGCCNT entries specified in the mapping service attribute definition)

E: Total size of physical maps to be made fully resident

F: Total size of PAGEC maps to be made fully resident

G: Total size of all non-resident physical maps that are subject to LRU management and are not larger than 64 KB

H: Total size of all non-resident PAGEC maps that are subject to LRU management and are not larger than 64 KB

I: Size of the largest non-resident physical map that is subject to LRU management and is larger than 64 KB

J: Number of non-resident physical maps that are subject to LRU management and are larger than 64 KB

K: Size of the largest non-resident PAGEC map that is subject to LRU management and is larger than 64 KB

L: Number of non-resident PAGEC maps that are subject to LRU management and are larger than 64 KB

The dynamic shared memory requirements for the MCF service are the total size of the calculation results explained in this subsection. Add the size of the dynamic shared memory for the MCF service to the size of the dynamic shared memory for other OpenTP1 services, and specify the result of the addition in the dynamic_shmpool_size operand of the system environment definition.

(a) MCF manager process

The size of the shared memory used by the MCF manager process is the total of the results of the following two formulas. The MCF manager process uses one process in one OpenTP1 system.

((600 + A) x B + 1600) x C + 2000 x D + 1600 x E + (600 + F) x G x H + 2 x (1600 x I) + 1600 x J

Legend:

A: Maximum receive message length

B: Maximum number of receive segments

C: Maximum instantaneous number of logical messages queued in all ITQs (memory queues) for the process (for disk queues, C is 0.)

D: Number of UAP processes that send or receive messages

E: Maximum instantaneous number of logical messages queued in all ITQs (both disk and memory queues) for the process

F: Maximum send message length

G: Maximum number of send segments

H: Maximum instantaneous number of logical messages queued in all OTQs (memory queues) for the process (for disk queues, C is 0.)

I: Maximum instantaneous number of logical messages queued in all OTQs (memory queues) for the process (for disk queues, C is 0.)

J: Maximum instantaneous number of logical messages queued in all OTQs (both disk and memory queues) for the process

(b) MCF online command process

The size of the shared memory used by the MCF online command process is 14,000 bytes. The MCF online command process uses one process when TP1/NET/XMAP3 is used. No process occurs when TP1/NET/XMAP3 is not used.