EQQR014W EQQR023E
EQQR014W ERDR
ERC
£ NO VALID HEADER IN EVENT DATA SET WITH DDNAME
DDN
Explanation: Event reader
ERC
encountered a header record that contained invalid information, for example, the
track capacity and the total number of records in the dataset were missing. The most probable reason for this
message is that a new event dataset has been created and it is being formatted by the event writer before usage.
The header record is not updated with the dataset characteristics until the formatting job has completed. This might
take some time if the event dataset is large.
System action: Event reader
ERC
processing continues. It makes a new attempt to extract valid information from
the header record every 10 seconds. This message is written on the TME 10 OPC message log every two minutes
until a valid header is read, or until the TME 10 OPC subsystem posts a stop request.
Problem determination: If this message appears more than 10 times on the TME 10 OPC message log dataset,
stop the event readers. Check that the
DDN
ddname connects to the correct event dataset, and if so, find out why
the header record is not valid.
System programmer response: Stop the event readers using the MODIFY command. Correct the error and restart
the event readers.
EQQR015E SEQUENCE NUMBER
SEQNO
IS ALREADY IN USE BY AN EVENT WRITER SUBTASK
Explanation: At event reader initialization, an event writer was already started with the sequence number specified in
the ERSEQNO keyword of ERDROPTS.
The number specified in the ERSEQNO keyword of ERDROPTS must be unique within the TME 10 OPC subsystem.
System action: The event reader initialization fails. The event reader subtask is terminated.
TME 10 OPC administrator response: Update the ERSEQNO keyword with a unique sequence number, and
restart the event reader subtask.
EQQR021E ERDR
ERC
£ UNABLE TO OPEN EVENT DATA SET WITH DDNAME
DDN
Explanation: Event reader
ERC
could not open its associated input dataset (ddname
DDN
).
System action: Event reader
ERC
processing is terminated.
Problem determination: Verify that the ddname statement associated with this event reader is correctly specified.
The ddname is EQQEVD
xx
, where
xx
should be equal to
ERC
.
System programmer response: Stop the event readers using the MODIFY command. Correct the error, if any, and
then restart the event readers.
EQQR023E ERDR
ERC
£ RECORDS OVERWRITTEN ON EVENT DATA SET (DDNAME
DDN
)
LR
£ EVENTS HAVE
BEEN LOST
Explanation: Event reader ERC# encountered a situation where the event writer overwrites event records not yet
processed by the event reader. Event datasets are used in a wrap-around fashion and for some reason the event
reader cannot keep up with the event writer.
System action: Event reader ERC# processing continues. The event records that were overwritten (LR#) are lost
and cannot be recaptured.
Problem determination: You probably have one of the following:
An inadequate event dataset allocation, so that it wraps around too fast.
The wait interval (ERWAIT of the ERDROPTS statement) is too long, that is, the event reader waits too long
between successive read attempts.
You should also check the dispatching priority of the reader task, to ensure that its priority is similar to that of the
event writer.
User response: Contact your system programmer.
System programmer response: Stop the event readers using the MODIFY command. Modify the appropriate
parameters and restart the event readers.
250 TME 10 OPC Messages and Codes