David,
You have two options as far as I can tell.
1) In DB2 DW you can define what are called UDP’s. A UDP is a user defined program that can
be any executable. In fact most of
the ETL1/ETL2 code in TDW 1.2 is Perl based UDP’s. You can insert a UDP upon completion of
the ETL1 and ETL2 steps. In the UDP
you can send a TEC event.
2) You can use a TEC adapter to scan the sqllib\logging
directory. I really don’t like
this option however. IMO, ITM
is still not ready for primetime for ASCII log scanning.
To me it makes more sense to use TEC
instead of ITM because the ETL processing is more of an event driven process
then something that would be monitored.
In other words what would you set your cycle time at? The ETL’s only run once per
night. However if you have your
heart set on ITM I guess in a UDP you could send an event to the NTEvent log
and use something like TMW_ParamEventLog to pick it up. The only thing is that if you go to TDW
1.3 you wouldn’t be able to use the NTEvetnlog if you move your Control
server over to a Unix box. I am
starting to ramble. Good luck.
John Willis
Gulf Breeze Software
www.gulfsoft.com
OpenESM Project
www.sourceforge.net/projects/gulfsoft
-----Original Message-----
From: owner-tme10@xxxxxxxxxxxxxxxx
[mailto:owner-tme10@xxxxxxxxxxxxxxxx] On
Behalf Of David Weir
Sent: Wednesday, January 26, 2005
9:55 PM
To: tme10@xxxxxxxxxxxxxxxx
Subject: [tme10] Monitoring TDW
work in progress
Hi guys
Can anyone offer any
helpful hints in how to monitor whether or not the steps in TDW are successful
or not ? While you can manually check the Work in Progress to see if success ,
I would like to have an ITM monitor to do this. Any suggestions ?
Best regards
David Weir
IMPORTANT NOTICE
This communication including any file attachments is intended solely for the
use of the individual or entity to whom it is addressed. If you are not the
intended recipient, or the person responsible for delivering this communication
to the intended recipient, please immediately notify the sender by e-mail and
delete the original transmission and its contents. Any unauthorised use,
dissemination, forwarding, printing, or copying of this communication including
any file attachments is prohibited.
It is your responsibility to scan this communication including any file
attachment for viruses and other defects. To the extent permitted by law, ING
and its associates will not be liable for any loss or damage arising in any way
from this communication including file attachments.
