EQQZ130W EQQZ135E
EQQZ130W XCF FUNCTION MSGO HAS FAILED DUE TO SIGNALLING FACILITY BUSY
Explanation: An XCF transmission was not successfully sent.
System action: The system will try to send it again. If the data queue element has not been successfully
transmitted within 5 minutes, it will be discarded.
Problem determination: This message can indicate that insufficient message-buffer space has been allocated in the
transport class, for the TME 10 OPC user. If this message appears on your system, increase the value you have
specified for MAXMSG, or if you have not specified a value for MAXMSG, include this keyword with a value greater
than 500, which is the default.
System programmer response: Check XCF transmission capacity.
EQQZ131W THE FOLLOWING OUTBOUND QUEUE ELEMENT HAS BEEN DISCARDED DUE TO REPEATED
TRANSMISSION ERRORS:
DQE
Explanation: The system tried for 5 minutes to send the data queue element, but did not succeed. The data queue
element is discarded.
System action: Processing continues.
System programmer response: None.
EQQZ132W THE FOLLOWING INBOUND QUEUE ELEMENT HAS BEEN DISCARDED DUE TO MISSING
EXTENSION BUFFER SEGMENTS:
DQE
Explanation: The system waited 5 minutes for a least one missing buffer segment, and then discarded the data
queue element and the incomplete extension buffer.
System action: Processing continues.
System programmer response: None.
EQQZ133W THE FOLLOWING INBOUND QUEUE ELEMENT WITH MISSING EXTENSION BUFFER SEGMENTS
HAS BEEN DISCARDED DUE TO DATA ROUTER TERMINATION:
DQE
Explanation: A data queue element with an incomplete buffer was present when the data router task terminated.
System action: Data router termination continues.
System programmer response: None.
EQQZ134I AN OPC/ESA CONTROLLER IS ALREADY ACTIVE WITHIN THE SAME XCF GROUP AS THIS
SYSTEM
Explanation: This system has been started as a host within an TME 10 OPC XCF group including an active host.
System action: The system terminates.
System programmer response: Check XCFOPTS for the group keyword value. Check OPCOPTS for the
OPCHOST keyword value.
EQQZ135E THE TRROPTS INITIALIZATION STATEMENT IS REQUIRED FOR A TRACKER SYSTEM
Explanation: A tracker system was started with no TRROPTS initialization statement.
If OPCHOST(NO) is specified, TME 10 OPC needs to know how the tracker is connected to the controller. This is
defined in the HOSTCON keyword in TRROPTS. The possible connections are:
Shared DASD The controller and tracker communicate via an event dataset and optionally a submit/release
dataset.
XCF The controller and tracker communicate via XCF communication links.
SNA The controller and tracker communicate via VTAM communication links.
System action: TME 10 OPC initialization fails and the subsystem terminates.
User response: Add a TRROPTS initialization statement specifying the controller connection type.
424 TME 10 OPC Messages and Codes