Special characters in the files
All messages and actions in the ROBAR rule files must be written in uppercase letters.
The lowercase letters t
, m
, v
, l
, s
, a
, b
, r
, f
, n
, z
, u
and the characters #
and /
have a special meaning in ROBAR. Wherever they occur in the message files, they are replaced by the text of the BS2000 message. This enables the following variables to be defined:
| TSN |
| Device mnemonic (2- or 4-character MN) |
| VSN of the volume |
| Storage location of the volume |
| Archive system status byte (for manual command input only) |
| Archive system coordinate, storing position for foreign cartridges, SUBTSN, or other content |
| Archive system coordinate (for manual command input only), or other content |
| Robot number |
| Archive system-response |
| Sequence number of the ROBAR job (used internally) |
| Other information |
| Date and time in the format dd/hhmmss |
| Dummy character in |
| Logical input area |
| Logical output area |
The lengths of the variables m
, v
, l
, s
, a
, b
, r
, f
, #
, z
, u
, i
, e
refer to the archive system commands or inserts of the BS2000 system messages. These lengths must be adhered to (see above).
Example
BS2000 message:
NKVT011 TAPE 'A0001K' DISMOUNTED FROM DEVICE 'T0'
Entry in message_file
:
:*:MF000: %NKVT011 vvvvvv mmmm
Since the BS2000 message is identified uniquely by the message number NKVT011
, certain text positions in ROBAR message can be dispensed with. All character strings consisting of uppercase letters, blanks and special characters are always checked.
In all actions which are executed by ROBAR for this message, the special characters vvvvvv
and mmmm
are replaced with A0001K
and T0
respectively.
The TSN (tttt
) is not given in message_file
since it is determined internally.