Messages and Codes - e IBM Tivoli Composite - IBM

EQQW073E EQQW076W
EQQW073E IT IS NOT VALID TO START AN EVENT WRITER IN EVENT READER MODE WITH THIS TYPE OF
HOST CONNECTION
Explanation: The Tivoli OPC configuration does not support starting an event writer in event reader mode. When
the event writer is started with the EWSEQNO, it tries to pass events directly to the controller. EWSEQNO can only
be used in these circumstances:
The event writer is started in the same address space as the controller.
XCF connections. The event writer is started at a tracker system connected to the controller using XCF
communication links.
SNA connections. The event writer is started at a tracker system connected to the controller using VTAM.
System action: The initialization of the event writer is terminated.
System programmer response: Remove the EWSEQNO keyword from the EWTROPTS initialization statement.
EQQW074E THE SUBMIT/RELEASE DATA SET WITH DDNAME = DDNAME IS TOO SMALL
Explanation: The submit/release dataset must be large enough to contain 100 records.
System action: The workstation analyzer processing stops. Message EQQW502E is issued.
Problem determination: None.
System programmer response: Stop Tivoli OPC, allocate a larger submit/release dataset, and restart Tivoli OPC.
EQQW075W THE HEADER RECORD IN FILE DDNAME IS INCOMPATIBLE WITH THE DEVICE TYPE
Explanation: The information in the header record does not match the calculated records per tracks value. Normally
this is caused by moving the dataset to a different device type.
Note: This message may be issued if you have reallocated the dataset using a method that does not put an end of
file at the beginning of the dataset. It can then be ignored.
System action: The dataset is reformatted.
User response: None.
EQQW076W NO CONTROLLER PULSE. EVENT WRITER WILL STOP PULSE DETECTION
Explanation: This message can be issued only when ROUTOPTS PULSE processing is active for tracker systems
on OPC Release 3 level or higher. There are two situations that can cause this message to be issued:
1. When handshake processing is in use, each connected tracker system sends an identification (ID) event to the
controller at the specified interval defined by the PULSE keyword, and the controller responds to the tracker
system. If the tracker detects that the controller has not responded to two consecutive ID events this message is
issued. This indicates that either there is a problem in the controller address space or the communication vehicle
has failed.
2. When a tracker has a blank destination, that is, when a tracker is started in a separate address space and is not
receiving work from the controller, the tracker waits for two default intervals (2 x 10 minutes) and issues this
message.
Note: When a tracker is connecting via XCF, this message may be issued without indicating a problem.
System action: The event writer task stops sending handshake events.
System programmer response: If the Tivoli OPC controller address space is active, check the message log dataset
for error messages or communication failures. If required, restart the controller. If the tracker issuing this message
has a blank destination ID, the message can be ignored.
Note: The startup of the tracker and the controller must be synchronized. However, in a DASD environment using a
submit/release dataset for the catalog management function only, the tracker must be started before the controller to
make sure that the pulsing is synchronized.
358 Tivoli OPC Messages and Codes