If you are interested in just some commands, you could always
investigate HP Security Monitor. It will allow for specified commands to be
logged to the system log file (provided command logging is enabled). I have used
this feature and it can be very useful in determining who did what, when. A
note, if you have a command being monitored and it is a conditional portion of a
job stream, udc or command file it will be shown in the logs even if it was not
executed. The CI had to look at it so it got logged.
It also will allow you to disable execution of a command, both from the CI or
programmatic. Once you have it in the log files, it is easy enough to write a
program to extract what you are looking for and place it into a file on the
3000, sparing a tree or two.

Bob Schlosser
Harris Corporation
Melbourne, FL.
(407) 727-5893

-----Original Message-----
From:   Keven Miller [SMTP:[log in to unmask]]
Sent:   Friday, April 16, 1999 11:57 AM
To:     [log in to unmask]
Subject:        Re: Console out of Paper results in System Hang

For tracking what happened, long ago we imlimented system udcs for
commands such as LIMIT, ABORTJOB, SUSPENDJOB, RESUMEJOB,
DELETESPOOLFILE,
and others which issues a TELLOP of the command.
This leaves a console trail of who and when these commands were done.


Another help for operators, we changed all question marks "?" in the
system catalog CATALOG.PUB.SYS to be question-mark, bell "?^G"
and I think even changed the text to be hilighted.
Then the operator can hear a request anywhere in the computer room
(Assuming you have a quiet room :)

Keven Miller
[log in to unmask]