We do this by running dsmadmc -id=xx -pas=xx -console, and trapping the
output there.
You could also use a file escape, or run q actlog periodically, or write
a user exit, or buy the Tivoli hook thing...

There are several ways to monitor what goes on in the activity log.

"Frost, Dave" wrote:
>
> SpamCop - Report spam:
> http://members.spamcop.net/sc?action=report&id=1045636
>
> Hi, *Smers
>
> We have been bitten (HARD) by a tape drive going bad - it gave a write
> error, but adsm carried on using it for many, many tapes.  A significant
> percentage of these were then rendered unreadable.  We have recovered them
> all, but it was a major job.
>
> I have been considering running dsmserv as a ksh co-routine so that I can
> trap a message such as ANR8302E containing the string OP=WRITE, and issue a
> command to vary the affected drive offline until we can investigate.
>
> Is anybody running dsmserv in this way?  Any problems or disadvantages?  It
> <seems> ok on our test rig so far.
>
> Tia
>
> dave
>
> ----------------------------------------------------------------------------
>
> The information contained in this email is confidential
> and intended only for the use of the individual or
> entity named above. If the reader of this message is
> not the intended recipient, you are hereby notified
> that any dissemination, distribution, or copying of
> this communication is strictly prohibited. Guardian will
> accept no responsibility or liability in respect to this
> email other than to the addressee.
>
> If you have received this communication in error, please
> notify us immediately by telephone at 44 (0) 1932835900
> or by email.

--
Mr. Lindsay Morris
Mr. Lindsay Morris
Gresham Enterprise Storage
lmorris AT openmic DOT com
606-253-8000