Access and call modes

You can specify an access or call mode for a member or operation for an interface.
Depending on the type of interface, you must specify additional information:
  • For receiver interfaces, on the Attributes tab of the Features window for the interface, specify an access mode for each attribute:
    • Explicit-Blocking: AUTOSAR-explicit access that blocks until a value arrives
    • Explicit-non-Blocking: AUTOSAR-explicit access that returns immediately with a status code
    • Implicit: AUTOSAR-implicit access
    Note: If an attribute uses the Explicit-non-Blocking access mode, the Rational® Rhapsody® implementation block cannot use the Wakeup on Data Received Event activation policy. That policy is on the Access & Activation tab for the implementation block. Conversely, if an attribute uses the Explicit-Blocking access mode, active elements cannot use the Data Received Event activation policy.
  • For sender interfaces, on the Attributes tab of the Features window for the interface, specify an access mode for each attribute:
    • Explicit: AUTOSAR-explicit access
    • Implicit: AUTOSAR-implicit access
    Note: If an attribute on a sender or receiver interface uses the Implicit access mode, on the Access & Activation tab for the implementation block there must be exactly one active element accessing it.
  • For client interfaces, on the Operations tab, specify a call mode for each operation:
    • Synchronous: The call blocks until the server completes the operations
    • Asynchronous: The call returns immediately. Another active operation with the Asynchronous Server Call Returns Event activation policy might be used to retrieve the value of the written parameters.

Feedback