The physical connection from the BS2000 system to the ROBAR server is implemented using a LAN, see "Connection from the BS2000 system to the ROBAR server".
The status of the connection between ROBAR-CL and ROBAR-SV can be monitored in the BS2000 system using a job variable, see third paragraph ("You can monitor...") in section "Starting ROBAR-CL-DCAM" in chapter "Operating ROBAR-CL". In the ROBAR-SV Manager this information is displayed for all ROBAR-SV instances in the overview window (see "Displaying information on ROBAR-SV instances") and on an instance-specific basis in the menu of a ROBAR-SV instance (see "Operating a ROBAR-SV instance"). When the connection is interrupted, this is displayed both on the pages of the ROBAR-SV Manager and in the menu window of the robar menu program of ROBAR-SV (see "Operation using the "robar" menu program").
ROBAR-CL-DCAM must be started on every BS2000 system which is connected to the ROBAR server using the start procedure SYSPRC.ROBAR-CL.<ver> (by means of ENTER-PROCEDURE or CALL-PROCEDURE, see "Operating ROBAR-CL").
During connection setup for ROBAR-SV and ROBAR-CL-DCAM, ROBAR-SV transfers a list of the supported devices and of the error codes which are relevant (inserts of message EXC0858) to ROBAR-CL.
During ongoing operation UCON forwards the console messages with the routing codes which are relevant for MTC operation to ROBAR-CL-DCAM. You define these routing codes when ROBAR-CL is configured, see "ROBAR-CL as an authorized user program".
ROBAR-CL-DCAM filters out those messages which are relevant for ROBAR-SV (see section "File SYSPAR.ROBAR-CL.<ver>.MESSAGES").
From the messages containing the insert MN (mnemonic device name) and from the EXC0858 messages only those are forwarded which are relevant for ROBAR-SV.
Jobs from the ROBAR-CL-SDF user program are also passed to ROBAR-CL-DCAM via the console interface.