Configures communication to a remote using the ALCM protocol.
 ALCM is a simple message oriented protocol that uses low level ethernet
 frames with protocol type 60-06 (DEC customer use). On DEC-based systems,
 ELN and VMS, the usage is simple and supported by the operating system. The
 DECnet address is used for addressing.
 On Linux systems, we have to use raw sockets to gain access to low level
 ethernet frames and the device's MAC address for addressing.

• RemoteConfig
• RemTrans

 Optional description.

 Process priority for the transport process. For future use.

 Device name for the ethernet device, Not yet implemented, defaults to "eth0".

 Hostname for the remote node. Used when hostname is to be part of the
 ALCM header in remote I/O or when mirroring common areas.
 Dynamic change is possible.

 DEC-net or MAC-address for the remote node. These to address types have
 the same format and is used directly in the address field of the low
 level ethernet frame. Note that on Linux systems, we often override
 the systems MAC-address in /etc/interfaces when using ALCM. This way we don't
 have to change address in remote when changing network device.

 The notation for DECnet address is node.area, eg 4.21 (decimal notation)
 The notation for MAC address is for example AA:00:A4:00:01:54 (hex notation)

 Dynamic change is not possible.

 Attribute that indicates connection with the remote node.
 The link is considered down when we reach the link supervision timeout
 time without receiving any ALCM data or I/O messages. The link is
 considered up again when receiving any kind of message. Note that this
 supervision is separated from the remote I/O supervision which uses
 IOStallFlag and IOStallTime.

 Time in seconds before the link is considered down. A value of 0 (zero) disables
 the LinkUp supervision.
 Dynamic change is possible

 When set, this attribute tells the remote handler not to start
 or restart the process that handles this remote node. If the transport process
 is running while the attribute is set it will terminate. Note that in ALCM there
 is only one process that handles all remote nodes.
 Dynamic change is possible.

 This attribute shows how many times the remote handler has restarted the
 transport process that handles this remnode.
 Dynamic change is possible and can be used in order to earn more restarts.

 The restart limit tells the remote handler how many times the transport process
 that handle this remnode can be restarted.
 Dynamic change is possible and can be used in order to earn more restarts.

 The restart time is set by the transport process at startup and therefore
 shows the latest (re)starttime.

 Scantime in seconds for outgoing RemTrans objects.
 Dynamic change is possible.

 Time in seconds to wait before retransmit when using acknowledge and buffering.
 For more information about acknowledge handling and retransmitting,
 refer to the documentation of the RemTrans object.
 Dynamic change is possible.

 Error counter.

 Type of remnode. Used in the RemoteConfig classgraph.

 Contains the objid for the RemTrans objects for this remnode.
 The objid's are inserted by the remote process.