 |
The Question is:
How can I mold OPCOM messages generated by the backup process into my own
status system.
My goal is to create a console that display's the status of all remote
backupfacilities on our site. While the helpdesk is responible for intime
exchanging tapecardridges they have to know what node exceeded it's storage
capacity of the cardridge. Therefo
r the return message produced by OPCOM is the most effective way to base an
alarm on.
A simple pipe structure like:
--------------------------------------
$pipe reply/status > OPCOM_Capture.lis
won't do.
Nore does this kind of type:
---------------------------------
$ DEFINE/USER SYS$COMMAND _OPA0:
$ REPLY/LOG
$ DEFINE/USER SYS$COMMAND _OPA0:
$ REPLY/ENABLE=tape
$ WAIT 00:05
$ DEFINE/USER SYS$COMMAND _OPA0:
$ REPLY/DISABLE
$ REPLY/LOG
The Answer is :
There is no easy way to do this.
OPCOM does not provide a programmable interface for capturing arbitrary
messages whether from BACKUP or other utilities, thus the usual approach
to capture these operator messages is to create a terminal, DECterm, or
pseudoterminal, associate a mailbox, and then enable the terminal as an
operator. The broadcasts will arrive in the mailbox.
For details on programming the terminal driver and the associated
mailbox, and information on the mailbox driver, please see the I/O
Users Reference Manual.
The OpenVMS Wizard expects this topic has been discussed in the
support databases, and there may well be examples available. Now
that you know some of the terminology, your search should be easier.
|