6.2.4.3.10 Command EnableCommunicationCmd

6.2.4.3.10.1 General

If CommandMask EnableCommunicationCmd is set, the EstablishConnections implementation shall enable all communication model-specific Objects related to the ConnectionEndpoints in an atomic operation.

6.2.4.3.10.2 PubSub

The EstablishConnections implementation shall enable the DataSetReader and/or DataSetWriter referenced by the ToDataSetReader and/or ToDataSetWriter References (or listed in the DataSetReaderPath and/or DataSetWriterPath if the PubSub configuration model is not exposed) for each element in ConnectionEndpointConfigurations. It shall also ensure that the parent Objects (WriterGroup, ReaderGroup, PubSubConnection, and PublishSubscribe) are enabled.

If enabling any communication model-specific Objects fails, the EstablishConnections implementation shall abort processing as described in 6.2.4.3.11.

If enabling a ConnectionEndpoint would lead to multiple DataSetReaders being enabled that reference the same TargetVariable(s), the EstablishConnections implementation shall abort processing as described in 6.2.4.3.11.

The possible StatusCodes for the FunctionalEntityNodeResult are formally defined in Table 11. The possible StatusCodes for the ConnectionEndpointResult are formally defined in Table 12. The possible StatusCodes for the EnableCommunicationResult are formally defined in Table 17.

The target of an enabled Connection is the Operational State, but various factors can affect this transition and are not reflected in the result of the EnableCommunicationCmd. The behaviour of the Connection Status and its dependency on PubSub objects is defined in 6.6.3.

6.2.4.3.10.3 Client Server

This clause may be defined in a future version of this document.