EQQE000I EQQE001E
EQQE000I TOTAL NUMBER OF EVENTS PROCESSED BY THE EVENT MANAGER TASK IS:
NUMEV
NUMBER OF EVENTS SINCE THE PREVIOUS MESSAGE IS:
NEWEV
EVENT MANAGER QUEUE LENGTH STATISTICS FOLLOW:
TOTAL Q1 Q2 Q5 Q10 Q20 Q50 Q100 >100
CALLS
Q1
Q2
Q3
Q4 Q5
Q6
Q7
Q8
|Explanation: This message is issued if the EVENTS statistics are made active, either by specifying the
|STATMSG(EVENTS) keyword in the JTOPTS initialization statement, or by issuing the modify command, /F
|subsys,EVESTA=ON.
|Once activated, this messages is regularly issued by the event manager subtask, until it is deactivated. The interval
|between two messages is calculated as follows:
|If STATIM is nonzero (in the initial parm or by modify command) the message is issued approximately every
n
|minutes (where
n
is the STATIM value), if any events have been processed.
|Otherwise, if EVELIM is nonzero (in the initial parm or by modify command) then the message is issued
|approximately every
n
events (where
n
is the EVELIM value).
|Otherwise, the message is issued approximately every
n
events, where
n
is half the JTOPTS BACKUP keyword
|value (default BACKUP is 400).
|This message shows the total number of events processed and how many events have been processed since the
|message was last issued or, if it is the first time it is issued, since the last time the event manager processed the
|events queue.
The message also contains information about how many events were waiting to be processed each time the queue
processing routine was called. The value below the TOTAL heading gives the total number of times that the event
queue was emptied. The values below the Qx headings give the number of times that the length of the queue was in
a particular interval. For example, Q50 gives the number of times that the queue was between 21 and 50 events.
System action: Normal TME 10 OPC processing continues.
User response: None.
EQQE001E ETT FAILED TO ADD
ADID
FOR TRIGGERING EVENT
TRIG
I/O ERROR READING AD DATA BASE
Explanation: ETT was triggered by an event but could not add the associated application due to an I/O-error on the
AD database.
System action: The associated application was not added by ETT, but ETT processing continues normally.
Problem determination: Review the preceding messages in the TME 10 OPC message log dataset to determine
the cause of the error.
User response: Contact your system programmer.
System programmer response: Save the message log dataset containing this error, and contact your IBM
representative.
Copyright IBM Corp. 1991, 1998 79