Your Browser is not longer supported

Please use Google Chrome, Mozilla Firefox or Microsoft Edge to view the page correctly
Loading...

{{viewport.spaceProperty.prod}}

ROBAR rule files

To enable you to deal with all the different eventualities that may occur in the tape processing handled by a data center, you are allowed to define your own console messages and message processing by ROBAR. This is done using device-specific execution control files, the so-called ROBAR rule files (RRF), which are used to define the actions that the archive system should perform in specific situations.

In addition to the BS2000 files SYSPAR.ROBAR-CL.<ver>.MESSAGES and SYSPAR.ROBAR-CL.<ver>.PROZPARAM, ROBAR uses the following RRFs on the ROBAR server (gray background in table):

File name

Meaning

See

SYSPAR.ROBAR-CL.<ver>.MESSAGES

This file contains the message numbers of the console message that ROBAR-CL passes to ROBAR-SV

"File SYSPAR.ROBAR-CL.<ver>.MESSAGES"

SYSPAR.ROBAR-CL.<ver>.PROZPARAM

This file contains the internal parameters for execution control

"File SYSPAR.ROBAR-CL.<ver>.PROZPARAM"

message_file

This file contains all BS2000 and archive system messages relevant to ROBAR

"File message_file"

message_xref

This file contains BS2000, ROBAR and archive system actions triggered by events specified in the message_file1

"File message_xref"

message_resp

This file contains among others the keywords for the BS2000 and ROBAR actions of the messages used in message_xref

"File message_resp"

roboter_cmds

This file contains the archive system commands used in message_xref

"File roboter_cmds"

error_defines

This file contains actions to be taken in the event of an error 1

"File error_defines"

TYPE-1/message_xref

Special file for devices of the type LTO-Ux 2


1

This file contains the keywords for the ROBAR actions

2

The different rule files allow ROBAR to take account of the specific device attributes (e.g. error handling) of the relevant device types

The RRFs are placed in the interface specific message_storage directory when ROBAR-SV is installed, see "Directories and files of ROBAR-SV". When a ROBAR-SV instance is started, they are transferred to the /var/lib/<interface>/<ROBAR-SV-Instance>/message_storage directory together with the other files of the ROBAR-SV instance.


Several RRF sets are available:

  • set CentricStor for ETERNUS CS

  • set SCSI_1 for Scalar i500 and i6000


ROBAR is shipped with standard ROBAR rule files for both the BS2000 systems and the ROBAR server.

If the standard files do not cover all the requirements of your data center, you can modify them to suit the needs of your data center at your own responsibility before ROBAR is used for the first time, see section "Modifications in the ROBAR rule files".