mcfmuap [-d maximum-communication-function-issue-count] [-t "[sndtim=synchronous-sending-monitoring-time] [sndrcvtim=synchronous-transmission-monitoring-time] [recvtim=synchronous-receiving-monitoring-time]"] [-j user-server-journal-buffer-size] [-e "maximum-segment-length"] [-l "[initseg=initial-sequence-number] [maxseq=maximum-sequence-number-for-wrap] [minseq=starting-sequence-number-after-wrap]"] [-u "[ntmetim=nontransaction-MHP-expiration-time]"] [-a "delaytim=delaying-time-allowance-of-application-startup"] [-c "order=function|commit"]

This command defines the environment common among UAPs.

-d maximum-communication-function-issue-count~<unsigned integer> ((0-65535)) <<0>>

Specify the maximum number of communication functions to be issued during processing of a transaction by an MHP.

This number is used to monitor an MHP. OpenTP1 will abnormally terminate an MHP upon the next issue of a communication function in excess of this number. If 0 is specified in this operand with no specification of the maximum number of issued MCF communication functions (of the user service default definition and the user service definition for the applicable service), the system does not monitor the number of issued communication functions.

-t

(Operands)

sndtim=synchronous-sending-monitoring-time~<unsigned integer> ((0-65535)) <<0>> (Unit: seconds)

Specify the maximum monitoring time between start and end of synchronous message transmission. With this operand specified, the system monitors the time until the remote system reports the end of processing. If 0 is specified in the operand, no time monitoring is performed.

sndrcvtim=synchronous-transmission-monitoring-time~<unsigned integer> ((0-65535)) <<0>> (Unit: seconds)

Specify the maximum monitoring time between start and end of synchronous message transmission/reception. With this operand specified, the system monitors the time until a response is returned from the remote system. If 0 is specified in the operand, no time monitoring is performed.

recvtim=synchronous-receiving-monitoring-time~<unsigned integer> ((0-65535)) <<0>> (Unit: seconds)

Specify the maximum monitoring time between start and end of synchronous message reception. With this operand specified, the system monitors the time until the remote system reports the end of processing. If 0 is specified in the operand, no time monitoring is performed.

-j user-server-journal-buffer-size~<unsigned integer> ((multiple of 4 between 4096-4000000)) <<32768>> (Unit: bytes)

Specify the size of the area for storage of the journal data. An MCF manager process uses this area to store data for a journal service until the following requests are issued:

• output request to the journal file,
• storage request to the journal service buffer

For the size of the journal buffer, calculate the data length of GJ, the data length of OJ, and the data length of CJ, and specify the largest of them.

1. Data length of GJ:
   (204 + seg)/4 x 4
   
2. Data length of OJ:
   (204 + seg)/4 x 4
   
3. Data length of CJ (serial number):
   This journal is acquired when you send a message by specifying the serial number. When you send a message to outside of the transaction, specify 128. When you send a message inside the transaction, specify 160.
   
4. Data length of CJ (message queue server):
   This journal is acquired when you use a disk queue as ITQ or OTQ.
   {260 + {(24 x ( msg/q1 + 960/q1 ))} + msg^#}/4 x 4
   

   Where,

   : The value enclosed in these symbols is rounded up to the nearest whole number.

   seg: Segment length

   aps: Number of applications started by the function dc_mcf_execap()

   les: Number of logical terminals used for sending messages

   ap: 32 when a disk is used as the input queue. 0 when memory is used as the input queue.

   msg: Length of messages to be sent or received using a disk queue

   ql: Physical record length of the queue file

   : Sum of the estimates for the messages received or sent in the relevant transaction

   #

   Add this if the value of que_io_maxrecsize in the message queue service definition is larger than the message size.

MCF will check and revise the specified value as follows:

1. if the specified value is smaller than the minimum value determined by MCF, it is revised upward to the said minimum value.
2. if the specified value is larger than the maximum value determined by MCF, it is revised downward to the said maximum value.
3. if the specified value is not a multiple of 4, it is rounded up to the nearest multiple of 4.

This operand can also be specified in the mcf_jnl_buff_size operands in the user service definition and user service default definition.

Priorities of the specified values are (1.>2.>3.):

1. User service definition
2. User service default definition
3. MCF manager definition

If the journal data size exceeds 131,072 bytes, specify the data size in the MCF manager definition and omit the mcf_jnl_buff_size operand from the user service definition and the user service default definition.

-e segsize=maximum-segment-length~<unsigned integer> ((512-2147483647)) <<512>> (Unit: bytes)

Specify the maximum segment length if transmitting messages in the following cases:

• when an MHP for processing error events is started (maximum segment length of the messages sent to or received by the MHP for processing error events),
• when the application startup feature is used (maximum segment length of the messages to be sent to the application started by the dc_mcf_execap function),
• when the message resending function is used, or
• when the mcftdmpqu command is used to copy the contents of the I/O queue (maximum segment length of the messages inside the queue whose contents are to be copied).

Specify the larger of the two values required for these cases.

-l

(Operands)

initseq=initial-sequence-number~<unsigned integer> ((0-2147483647)) <<1>>

Specify an initial value for the message sequence numbers.

maxseq=maximum-sequence-number-for-wrap~<unsigned integer> ((0-2147483647)) <<65535>>

Specify the maximum sequence number before a wraparound occurs; the next sequence number becomes the starting value after the wraparound.

If the specified value is too small, after a wraparound the same sequence number could exist within the same queue file, and unique sequence numbers for the messages cannot be guaranteed. Thus, specify a value that satisfies the following equation:

Maximum sequence number > Q x (1 + R), where

Q is the maximum number of messages stored in the disk, and

R is the roll back ratio, considering the worst case scenario.

minseq=initial-sequence-number-after-wrap~<unsigned integer> ((0-1)) <<1>>

Specify the initial value for the sequence number after a wraparound.

This value will differ as a function of the online control program of the other connections.

-u ntmetim=nontransaction-MHP-expiration-time~<unsigned integer> ((0-65535)) <<0>> (Unit: seconds)

Specify the default value of the ntmetim operand that is to be specified in the -v option of the mcfaalcap command of the MCF application definition.

To monitor a nontransaction MHP process for looping and hanging-up, the -u ntmetim operand specifies the maximum expiration time for the process.

If 0 is specified, no time monitoring is performed.

If the nontransaction MHP process does not terminate within the specified expiration time, it is terminated abnormally.

-a delaytim=delaying-time-allowance-of-application-startup~<unsigned integer> ((0-360)) <<0>> (Unit: minutes)

Specify the delaying time allowance of application startup where the specified startup time is before the current time.

If the specified time is before the current time and is within the delaying time allowance, the MCF starts up the application immediately. If the specified time is out of the allowance, the MCF will start up the application at the specified time of the next day.

-c

(Operands)

order=function|commit ~<<function>>

Specify the order for processing performed by multiple UAPs for each of the following:

• Sending or resending messages that use the same logical terminal (mcftalcle -l)
• Starting UAPs that use the same logical terminal (mcfaalcap -n lname) or internal communication path (mcfaalcap -n cname)

function

Processing is performed in the order in which functions^# are called by UAPs.

commit

Processing is performed in the order in which transactions are committed by UAPs.

If OpenTP1 is restarted when messages remain in the output queue (disk queue) of the logical terminal, processing is performed in the order in which transactions are committed.

#

Functions here indicates the message send function, message resend function, and application startup function.