Disruptions of connections between a ROBAR-SV instance and the BS2000 systems are reported both on the information pages of the ROBAR-SV Manager and in the menu window of the robar menu program (see section "Reporting a disruption to the connection between ROBAR-SV and ROBAR-CL" in chapter "Screen layout").
If the connection between ROBAR-SV and a BS2000 system is severed, ROBAR reacts as follows.
All jobs of the BS2000 system to which the connection has been severed are deleted from the job file of the ROBAR-SV instance. Thereafter ROBAR makes regular attempts to re-establish the connection.
Following a successful connection setup, ROBAR-SV sends all messages to ROBAR-CL that have not yet been transferred. Subsequently ROBAR requests information on the allocated devices and their assignment as well as on open BS2000 jobs still to be processed. It then begins normal processing of these jobs.
Proceed as follows should the attempt to establish the connection fails:
terminate ROBAR-CL-DCAM in the BS2000 system
terminate all the ROBAR-SV instances, then log off from the ROBAR server
log on to the ROBAR server again, start the ROBAR-SV instances again
restart ROBAR-CL-DCAM in the BS2000 system
Each time the connection is severed between the BS2000 system and the ROBAR server, the current BS2000 trace file is closed. Once the connection has been set up again, a new trace file displaying the current time stamp is created.
In the case of saturation states (Grade 2 and higher) in the paging area of a BS2000 system, operation with ROBAR-CL is stopped. It is resumed automatically when the saturation state has terminated.