OpenTP1 Version 7 Operation

[Contents][Index][Back][Next]

mcftactcn (Establish connections)

Format

mcftactcn [-s MCF-communication-process-identifier]
          {-c connection-ID|-g connection-group-name}
          [-u subconnection-ID] [-S XP-service-name@host-name]

Function

The mcftactcn command establishes connections.

Options

-s MCF-communication-process-identifier~<numerals (0-9), a-f> ((01-ef))

Specifies the MCF communication process identifier of the MCF communication service controlling the target connection. No more than one MCF communication process identifier can be specified.

If this option is omitted, the mcftactcn command is executed on all MCFs. This means that the overhead required to search for the MCF communication services is added to the processing load of the operation commands.

If you want to have a configuration that includes lots of MCF communication services or if you want to use many operation commands, use the -s option to specify an MCF communication process identifier.

-c connection-ID~<identifier, 1-8 characters>

Specifies the ID of a connection to be established.

A maximum of eight connection IDs can be specified. When entering large amounts of inputs for the operation, specify more than one connection or specify a group of connections to increase the number of connections to be processed in parallel by one command while reducing the number of commands to be entered.

To specify multiple connection IDs, separate them by a space and enclose the entire string of connection IDs in double quotation marks ("). The same connection ID cannot be duplicated when specified.

The asterisk (*) can be used in the specification to indicate a group of connection IDs. The ID of a group of connections cannot coexist with the IDs of connections for which no grouping is specified. A group name must be enclosed in double quotation marks (").

*
Specifies that all connections are to be established.

character-string*
Specifies leading characters of a connection ID when all connections with IDs beginning with the specified character string are to be established.

<Example of specifying more than one connection>
To specify cnn1, cnn2, and cnn3, code: -c "cnn1[Figure]cnn2[Figure]cnn3"

<Example of specifying a group of connections>
To specify all connections beginning with cnn, code: -c "cnn*"

-g connection-group-name~<identifier, 1-8 characters>

Specifies the name of a connection group to be established.

A maximum of eight connection group names can be specified. When entering large amounts of inputs for the operation, specify more than one connection group or specify a group of connection groups to increase the number of connection groups to be processed in parallel by one command while reducing the number of commands to be entered.

To specify multiple connection group names, separate them by a space and enclose the entire string of connection group names in double quotation marks ("). The same connection group name cannot be duplicated when specified.

The asterisk (*) can be used in the specification to indicate a group of connection group names. The name of a group of connection groups cannot coexist with the names of connection groups for which no grouping is specified. A group name must be enclosed in double quotation marks (").

*
Establishes all connection groups.

character-string*
Specifies leading characters of a connection group name when all connection groups with names beginning with the specified character string are to be established.

<Example of specifying more than one connection group>
To specify cng1, cng2, and cng3, code: -g "cng1[Figure]cng2[Figure]cng3"

<Example of specifying a group of connection groups>
To specify all connection groups beginning with cng, code: -g "cng*"

Note that the -g option is valid only when the TP1/NET/OSI-TP protocol is used.

-u subconnection-ID~<1-8 character identifier>

Specifies the subconnection ID of a subconnection to be established. It can be specified when only one connection ID is used and no grouping is specified. Neither more than one subconnection ID nor ID of a group of subconnections can be specified. When this option is omitted, all subconnections under the specified connection are established.

The -u option can be used only under the TP1/NET/HNA-NIF protocol.

-S XP-service-name@host-name

Specifies the XP service to be connected. Specify this when the protocol is TP1/NET/XMAP3.

XP-service-name~<1-to-14-character identifier>
Specifies the name of the XP service to be connected.

host-name~<1-to-127-character identifier>
Specifies the name of the host where the management daemon for the XP service to be connected operates. When this option is specified, only one connection ID can be specified. The -g option cannot be specified with this option.

Output messages

Message ID Description Output destination
KFCA10350-I mcftactcn command has been entered. Standard output
KFCA10351-E MCF startup processing is underway. Standard error output
KFCA10352-E MCF termination processing is underway. Standard error output
KFCA10353-W Input format is invalid. Standard error output
KFCA10354-E Memory is inadequate. Standard error output
KFCA10355-W Specification of an argument is invalid. Standard error output
KFCA10356-E Overtime occurred during process. Standard error output
KFCA10357-E Overtime occurred in MCF. Standard error output
KFCA10358-E Error occurred in an internal function. Standard error output
KFCA10359-W Response to mcftactcn command input source failed. Message log file
KFCA10371-I mcftactcn command has been accepted normally. Standard output
KFCA10373-E mcftactcn command terminated abnormally. Standard error output
KFCA10380-E Retrieval of remote process failed. Standard error output
KFCA10381-E Specified connection has not been cataloged. Standard error output
KFCA10391-E mcftactcn command is not supported. Standard error output
KFCA10500-I Help message Standard output
KFCA16402-E RPC error occurred during command processing. Standard error
KFCA16424-E Specified connection group has not been cataloged. Standard error output

In addition to these messages, messages for the protocol being used are output; for details, see the applicable protocol manual.