Article 150201 of comp.os.vms:
If you really mean a couple of minutes is going to mess you up, I think you 
might have to look elsewhere.

I've knocked up a really hacky bit of DCL code that searches through 
OPERATOR.LOG for un-satisfied requests. There are a number of shortcomings 
with this:

It's a total hack...

It may take some time for the information to actually appear in OPERATOR.LOG .
 If your timing is that tight, this may be no good.

Each pass takes about 30 seconds, uses about 15 seconds of CPU & 1000 I/Os 
on a 3000-300LX, with a 10k block OPERATOR.LOG file.

If a REPLY/LOG is issued after the OPCOM Request, it won't be in the file 
that's searched.

On that basis, this might be a non-runner. Anyway, here's the code. It's 
really simple (and poor), but it might be of some use.


$ search sys$manager:operator.log "Request"/out=t0.t
$ search t0.t "Request","from user"/match=and/out=t1.t
$ def/user sys$output t2.t
$ ty/tail t1.t
$ open ip t2.t
$loop: read ip/end=no_more rec
$ tmp=f$element(0,",",rec)
$ search t0.t "''tmp'"," was "/match=and/out=nl:
$ status=$status
$ if status .nes. "%X00000001"
$ then
$  write sys$output "Problem with ",rec
$  endif
$ goto loop
$no_more: close ip

It would be much tidier if it were possible to readilly direct the output 
from REPLY/STATUS to a file, but that's back to your original problem, 
really.

Mark


Mark Iline	system@meng.ucl.ac.uk
Dept Mech Eng, University College, London. UK

			Read at your own risk.

From:	SMTP%"blakew@mlm.fuller.com" 25-JUN-1996 18:21:56.47
To:	Info-VAX@Mvb.Saic.Com
CC:	
Subj:	quiet opcom messages.

hey all--

We have a problem with really tight night-time run-schedule, and the quiet
opcom messages.  Our schedule is so tight that missing a few minuets between 
jobs means the difference between the system being up or not in time.

If the operators are paying attention to one of the other systems (AS/400, 
IBM4341, or the Alpha) they mess the opcomm message on the VAX's console.  
They don't have this problem with the other systems because there beep is MUCH 
more irritating.

I have called DEC and they said that there is no way to make the speaker 
louder on a VT type tube.

I started working on a program that captures the opcom messages, opens a 
window up on the VT and sits and beeps until the operator can answer the 
message.  The problem is I just do not have the time to finish nor debug it.

Any one know of anything that could help?  The system is a VAX4000-300 cluster 
running VMS 5.4-2; with vt420's as the main system console(s).

Thank you for your time.

+--------------------------+------------------------------------------------+
|H. Blakely Williford      | Men never do evil so completely and cheerfully |
|Systems Administrator     | as when they do it from religious conviction.  |
|The Fuller Brush Company  |       - Pascal                                 |
+--------------------------+------------------------------------------------+


