mcftenv -s MCF-communication-process-identifier | application-startup-process-identifier [-m MCF-manager-process-identifier] -a MCF-application-definition-object-file-name -q [diskitq=yes|no]

This command defines the environment common to the MCF.

-s MCF-communication-process-identifier|application-startup-process-identifier~<numeric character (0-9) and a-f> ((01-ef))

This option specifies the identifier for either an MCF communication process or application startup process identifier. The value must be unique from identifiers specified with other mcftenv commands.

MCF-communication-process-identifier

Specify the identifier for the MCF communication process, if the MCF communication configuration definition corresponds to this process. This identifier is used in special processes such as a message log output by MCF, or the entry of input commands.

application-startup-process-identifier

Specify the identifier for the application startup process, if the MCF communication configuration definition corresponds to this process. This identifier is specified in the -p option of the mcfaenv command of the corresponding MCF application definition.

-m MCF-manager-process-identifier~<alphabetic characters> ((A-Z, a-z)) <<A>>

Specify the identifier of an MCF manager process that manages the MCF communication process. The MCF manager process identifier must be the value specified by the mcfmenv command in the MCF manager definition.

-a MCF-application-definition-object-file-name ~<1-to-8 alphanumeric characters>

Specify the identifier for the MCF application definition object file corresponding to this MCF communication configuration definition. Use the name of the MCF application definition output object file created with the MCF definition object creation utility (mcfapli command).

-q diskitq=yes|no~<<yes>>

Specify whether or not the applications activated from the MCF communication server should use a disk queue as an input queue.

Specify diskitq=no (do not use a disk queue as an input queue) speeds up starting MCF.

yes

Some or all of applications use a disk queue as an input queue. Whether at least some applications use a disk queue as an input queue depends on the value specified in the quekind operand of the -g option in the mcfaalcap MCF application definition.

no

No applications use a disk queue as an input queue.

However, if the MCF communication server which specifies diskitq=no starts an application for which quekind=disk is specified in the -g option of the mcfaalcap command in the MCF application definition, diskitq=no is ignored and a memory queue is used as an input queue.