RE: Event ID always 1

ok .. that makes sense ... In the detail section of the client is shows the
event_hndl as Event ID if you display formatted names and values... thank
you for your help

Gerry


Gerry Brown
Cell    678 571 3839
Office 770 370 7186



                                                                           
             "Loren Cain"                                                  
             <loren.cain@digic                                             
             onasp.com>                                                 To 
             Sent by:                  <tme10@xxxxxxxxxxxxxxxx>            
             owner-tme10@lists                                          cc 
             .us.ibm.com                                                   
                                                                   Subject 
                                       RE: [tme10] Event ID always 1       
             11/30/2004 12:45                                              
             PM                                                            
                                                                           
                                                                           
             Please respond to                                             
             tme10@xxxxxxxxxxx                                             
                   m.com                                                   
                                                                           
                                                                           




Each event received by the EventServer is uniquely
identified by the concatenation of the following
three attributes:
  server_hndl
  date_reception
  event_hndl

The server_hndl attribute refers to the EventServer.
Since under the current architecture there can be only
one EventServer per TMR, this value is always 1 (you
can change it, but there's no particular reason to).

The date_reception attribute is a timestamp indicating
when the event was received by the server, and is in
Unix epoch format (number of seconds since 1-1-1970).

The event_hndl attribute is just a counter used to
differentiate multiple events that may have been
received during the same second. If you only receive
one event per second, the event_hndl will always be 1.
If you receive 3 events in the same second, you will
have event_hndl values of 1, 2, and 3 for those events.

You may also see event_hndl values up in the thousands,
but those are for internally-generated events that did
not arrive through the tec_reception process.

It sounds as if you may be confusing the event_hndl
attribute with something like the "Event ID" field in
the Windows event log. They really serve quite different
purposes. The event class is probably a closer match to
the Windows "Event ID".


Loren Cain
Digicon

-----Original Message-----
From: owner-tme10@xxxxxxxxxxxxxxxx [mailto:owner-tme10@xxxxxxxxxxxxxxxx]
On Behalf Of gerrbrown@xxxxxxxxxxxxxx
Sent: Tuesday, November 30, 2004 12:04 PM
To: tme10@xxxxxxxxxxxxxxxx
Subject: [tme10] Event ID always 1

>From the TEC client all events show up with an Event ID (event_hndl) of
1
.. very hard to use this field as an identifying slot if everything is
"1".
Any suggestions as to why this would be the case?

Any help would be greatly appreciated,


Gerry Brown




*****************************************************************************************************************************************************************************************
This message is intended for the use of the individual or entity to which
it is addressed and may contain information that is confidential and
privileged and exempt from disclosure under applicable law.  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.  If you have received this communication in error,
please contact the sender immediately and delete it from your system.
Thank You
*****************************************************************************************************************************************************************************************