Stopping a ROBAR-SV instance

The ROBAR administrator or operator stops a ROBAR-SV instance in the ROBAR-SV Manager, in the robar menu program or with the robar_stop program. To stop a ROBAR-SV instance properly, the ROBAR instances which are running must first be terminated by ROBAR-SV.

Before you stop a ROBAR-SV instance, check whether all the actions have been terminated properly. This is particularly important for archive system commands such as IVK or IN. If the ROBAR processes are terminated prematurely, data inconsistencies can occur or messages can remain unanswered.

When the archive system switches to the OFF status, a message is sent to the BS2000 system. Depending on the ROBOT_OFF_MSG configuration parameter, this will be a PAUSE or TYPE message.

Stopping a ROBAR-SV instance with the ROBAR-SV Manager

>	Start the ROBAR-SV Manager.
>	In the ROBAR-SV Instances menu select the required instance.
>	In the Operation tab click the action icon to stop the instance

Stopping a ROBAR-SV instance using the robar menu program (only standalone variant)

>	Start the robar menu program.
>	Select the INSTANCES menu.
>	Select the corresponding instance using the "up arrow" or "down arrow" key (inverse presentation) and select the STOP function. ROBAR-SV will stop the ROBAR processes for communicating with the archive system and the BS2000 systems. The interface-specific configuration file of the ROBAR-SV instance is retained. The ROBAR-SV instance is consequently still configured and can be restarted.

Stopping a ROBAR-SV instance using the robar_stop program (only standalone variant)

The ROBAR administrator or operator can also stop a ROBAR-SV instance using the robar_stop program.

Call:

robar_stop [--type=scsi/-s] [--type=abba/-a] <instance>

Operands:
--type=scsi/-s	Selects the SCSI interface
--type=abba/-a	Selects the ABBA interface (one of the interfaces must be specified)
<instance>	Name of the ROBAR-SV instance which is to be stopped

Example

robar_stop -s myrobar