Filter
Top Products
EQQW075W EQQW101E
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. This is
normally caused by moving the dataset to a different device type.
Note: This message may be issued if you have reallocated the data set using a method that does not put an end of
file at the beginning of the data set. 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: The message can only be issued when ROUTOPTS PULSE processing is active for Tracker systems
on OPC/ESA 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 there is a problem in the controller address space, or that 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 not
receiving work from the controller, the tracker will wait for two default intervals (2 x 10 minutes) and then issue the
message.
Note: When a tracker is connecting via XCF, this message may be issued without indicating a problem.
System action: The event writer subtask will stop sending handshake events.
System programmer response: If the TME 10 OPC controller address space is active, check the message log
dataset for error messages or communication failures. Restart the controller if required. If the tracker issuing this
message has a blank destination ID, the message can be ignored.
Note that 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
get the pulsing synchronized.
EQQW077E THE SUBMIT/RELEASE DATASET IS NOT INITIALIZED
Explanation: An TME 10 OPC tracker system tried to update the submit/release dataset, ddname EQQSUDS, but
the dataset is not initialized by the controller. This message is only issued when starting with a new submit/release
dataset.
System action: The event writer initialization fails and the subtask terminates.
User response: Stop the tracker and start the controller in order to initialize the submit/release dataset.
EQQW100E WORK STATION NAME IS NOT DEFINED OR IT IS INVALID
Explanation: Data entry error; see “Data Entry Errors” on page 2.
The first character in a valid name must be an alphabetic character.
EQQW101E WORK STATION TYPE IS NOT DEFINED OR IT IS INVALID
Explanation: Data entry error; see “Data Entry Errors” on page 2.
Valid workstation types are: G for general, C for computer, and P for printer workstation.
308 TME 10 OPC Messages and Codes