Steve,

     I have a request outstanding for a fellow TSM'r for userexit code
     under NT. Within a week I hope to have some time to cleanup my
     existing userexit code (it has a tie in with the registry) so that it
     has a more generic behaviour. As soon as I'm finished I'll send it to
     you.

     To give a hint as to what the userexit will do for you, for every TSM
     message not filtered a message file will be created in the TSM startup
     directory. The message file will have a filename like userx001.mit
     (the 001 is a message file number that will rap around at 999) with
     contents similar to this:


     ERR2121
     Event time: 11/11 12:00:00
     Severity  : error, TSM function: server
     Event type: server, message origin: TSMSRVX, message owner: TSMSRVX
             ------------------
     ANR2121 the message......

     regards Walter Ridderhof.



_____________________________ Reply Separator
_________________________________
Subject: tsm 4.1 event notification
Author:  "ADSM: Dist Stor Manager" <ADSM-L AT VM.MARIST DOT EDU> at INET-1
Date:    11/8/00 2:15 PM


We have been running adsm 3.2.1.50 running on aix for several years. We
have written numerous korn shell scripts that do monitoring functions
like checking for offline drives, missed or failed schedules,
outstanding tape mounts, etc.

One important function is notifying our operators of a pending tape
mount for the 8mm drive which is used for our offsite media. In aix we
accomplish this by a script that tails the adsm console log so that
mount and other necessary messages can be trapped. Once trapped we
generate emails for some messages and for other messages we ftp jcl to
our os390 system. The job runs and puts up a mount message on the
operator console.

Now we are in the process of replacing adsm with tsm 4.1 which will run
on windows 2000. To ease the migration I installed cygwin (bash shell)
and blat (mail) so that most of our aix scripts would work with minor
modifications. However, the really important script that tails the
console log has some problems. It works fine for a while and then just
stops working. I have not had any luck diagnosing the problem so I have
been looking for alternatives. So far I have looked at event logging for
file, filetext, nteventlog and userexit and for various reasons have not
been successfull implementing them.

How do the rest of you handle notifying your operations staff of tsm
manual tape mount requests or other events that need attention?


--
Steve Bennett, (907) 465-5783
Steve Bennett, (907) 465-5783
State of Alaska, Information Technology Group, Technical Services
Section


-----------------------------------------------------------------
ATTENTION:
ATTENTION:
The information in this electronic mail message is private and
confidential, and only intended for the addressee. Should you
receive this message by mistake, you are hereby notified that
any disclosure, reproduction, distribution or use of this
message is strictly prohibited. Please inform the sender by
reply transmission and delete the message without copying or
opening it.

Messages and attachments are scanned for all viruses known.
If this message contains password-protected attachments, the
files have NOT been scanned for viruses by the ING mail domain.
Always scan attachments before opening them.
-----------------------------------------------------------------
=========================================================================