BackBox H4.00 VTC Scripting Option

Introduction
11 BackBox H4.00 VTC Scripting Option
Distributed utilities
BBOXLOG, BB_ArchiveBit and WAITFILE are distributed Windows programs that can
be used in user–writen BackBox scripts. When a script is started, the MS-Windows
PATH variable is augmented with the VTC program directory to make these utilities
available.
BBOXLOG – Logs a message in NonStop EMS
BBOXLOG sends a message to the EMS subsystem of a NonStop node.
BBOXLOG can be run in scripts triggered by the BackBox software used in a stand-
alone Windows script. BBOXLOG must run in a Windows server hosting a BackBox as
it communicates with a BackPak Domain Manager.
Syntax:
SET BBOX_NSK_NODE=<\node-name>
SET BBOX_DOMAIN=<domain-name>
BBOXLOG event-number “message text” [param-1 [param-2] … ]
BBOX_NSK_NODE and BBOX_DOMAIN set the message destination.
These environment variables are already set with appropriate values when run in
scripts triggered by BackBox.
Event-number is the generated EMS event number.
It must be in the range 8000 to 8999.
“Message text” is the generated EMS event message text.
Text with a syntax similar to the format in the C function
sprintf().
[Param-1 [Param-2] ….] are the parameters for sprintf(). Parameter values
being strings in the command line, the parameter conversion
type must be only %s in the “Message text” - ultimately it
must be %%s, see below.
Notes
• The target EMS collector name is specified in the BackPak Domain
configuration.
• When sprintf() parameters are specified in the “Message text”, the
% character must be doubled. Example:
bboxlog 8001 "Restoring files for tape volume %%s" %BBOX_VOLUME%
•
When BBOXLOG is executed outside the BackBox environment, the
Windows PATH must be update to include the BackBox installation
directory.
SET PATH %PATH%; C:\Program Files\ETINET\BackBox Virtual Tape
Emulation