Starting a ROBAR-SV instance

The ROBAR administrator or operator starts a ROBAR-SV instance in the ROBAR-SV Manager, in the robar menu program or using the robar_start program.

Preparations for the initial start of a ROBAR-SV instance

Configure a ROBAR-SV instance as a ROBAR administrator and create an interface-specific configuration file with the name of the ROBAR-SV instance (see "Interface-specific ROBAR-SV configuration files").

For this purpose the ROBAR-SV Manager offers a user-friendly wizard with which you can create a new ROBAR-SV instance either completely from scratch or by modifying an existing configuration file. You are recommended to proceed as follows:

>	Start the ROBAR-SV Manager.
>	In the ROBAR-SV Instances menu select the Upload configuration file button when you wish to upload a configuration file for the new instance from your PC to the ROBAR system.
>	In the ROBAR-SV Instances menu select the Create new instance button. The wizard for creating a new instance is started.
>	In the first step choose whether you want to create a ROBAR-SV instance either completely from scratch or by modifying an existing (or uploaded) configuration file.
>	In the following steps enter the information required for the new instance. Using your information the wizard will create the interface-specific configuration file with the name of the ROBAR-SV instance.

Each additional ROBAR-SV instance requires its own interface-specific configuration file.

Starting 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 start the instance.

Starting 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 START function. ROBAR-SV will start multiple ROBAR processes for communicating with the archive system and the BS2000 systems.
>	Optional but recommended: In the INSTANCES menu, SELECT function, select the highlighed ROBAR-SV instance if you also wish to address this ROBAR-SV instance from other masks of the menu program. The selection of the ROBAR-SV instance is also retained when the menu program is terminated.

Starting a ROBAR-SV instance using the robar_start program (only standalone variant)

The ROBAR administrator or operator can also start a ROBAR-SV instance using the robar_start program.

Call:

robar_start [--type=scsi/-s] [--type=abba/-a] <instance> [nocmx] [deltraces]

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 started
nocmx	This specification prevents the CMX components from starting (optional)
deltraces	This specification deletes the trace files (optional) The following trace files are deleted: CMX trace files (inotrc.*) Trace files of the ROBAR-SV instance Backed-up trace files (see RECOVER_DISK_FULL script, "Automatic disk storage monitoring")

Example

robar_start -s myrobar deltraces

Job file of a ROBAR-SV instance

All jobs of a BS2000 system for MTC management which ROBAR-CL passes to ROBAR-SV are collected in the job file of the ROBAR-SV instance which is responsible for the archive system.

The robar.mess job file of an active ROBAR-SV instance is contained in the /var/lib/<interface>/<instance>/cmx/ directory.

Status of the MTC devices when a ROBAR-SV instance starts

If a ROBAR-SV instance is started, it calls an entry MFSAT (START-ATTACH) predefined in the ROBAR rule files for all devices connected during the start.
The status of the MTC devices is checked by ROBAR-SV during the start. The entries MFSMT, MFSKE and MFSOC are called depending on the status of the MTC devices:

MFSMT	There is no data volume mounted on the MTC device (MFSMT stands for device EMPTY).
MFSKE	A data volume not used by BS2000 is mounted on the MTC device. This data volume should be removed using the KEEP command (MFSKE stands for KEEP).
MFSOC	The MTC device is reserved and is currently being used (MFSOC stands for OCCUPIED).