Logical Command [Dido Solutions, Inc Wiki]

This page is read only. You can view the source, but not change it. Ask your administrator if you think this is wrong.

====== Logical Command ======

[[dido:99_annexes:annex-b-terms-and-definitions:l:start|Return to L Terms]]

===== Discussion =====

A Logical Command represents a Logical Data Structure Instance that expresses an intended action by a Logical Node or Node Role.

A Logical Command differs from a Logical Event. A Logical Command requests or directs action. A Logical Event reports the occurrence or result. Logical Commands primarily support Control Plane interactions, but a domain profile identifies any domain-specific command-handling requirements.

Logical Commands support operational coordination, recovery, replay, status reporting, configuration reload, pause, resume, retry, and other controlled behaviors.

===== Definition =====

//Logical Data Structure Instance expressing intended action.//

===== Source =====

Specialization of Data Structure Instance and Control Plane from Part 1, Sections 7.8 and 8.2; generalised from control-plane command material in the original FX Demo Reference Architecture.

===== Note =====

A Logical Command is not an orchestration command, shell command, API call, DDS command topic, queue message, or RPC method. Implementation profiles select those realisations.

===== Example =====

A report-status command requests that a Logical Node report its lifecycle state and operational condition.

----

[[dido:99_annexes:annex-b-terms-and-definitions:l:start|Return to Top]]