EQQX269E EQQX300E
EQQX269E THE LTP DATA SET IS BEING USED BY A BATCH FUNCTION, TRY LATER
Explanation: You cannot access the long-term plan dataset because it is being used by a batch function.
System action: The request is rejected.
User response: Try again later.
EQQX270E THE JS DATA SET IS IN USE, TRY LATER
Explanation: You have requested a function that requires access to the JCL repository file, but this file is not
available at the moment.
System action: The request is rejected.
User response: Wait a few seconds and then repeat the request.
EQQX271E A SEVERE ERROR OCCURRED IN THE GENERAL SERVICE TASK
Explanation: Your request to use the general service function could not be granted because a severe error occurred
in the general service subtask.
System action: The request is rejected.
User response: Try again later. If the error persists, contact your system programmer.
System programmer response: To determine the cause of the error, review the TME 10 OPC message log and
look for messages concerning the general service subtask and issued at the time of the request. Correct all errors
and then restart the TME 10 OPC subsystem. If the error persists, collect information in the form of the sequence of
actions leading to the error, and if possible, the data it may be dependent on. Then contact your IBM representative.
EQQX274E AN I/O REQUEST SPECIFIES TOO LARGE RECORD SIZE
Explanation: Your request to create or modify a record resulted in the record exceeding the maximum size of the
VSAM record.
System action: The request is rejected.
User response: Contact your system programmer.
System programmer response: Check the record size against the VSAM file definition. For more information, refer
to
TME 10 OPC Installation Guide
.
EQQX300E AN APPLICATION DESCRIPTION RECORD IS TOO LARGE TO BE SAVED
Explanation: Current AD record is larger than the maximum record size of the AD data base.
System action: The request to write the record is rejected.
Problem determination: Refer to the diagnostic file (with ddname EQQDUMP) for further information. This file
contains a copy of the record and the position of the error.
User response: Check the entered data and if the error occurred in batch, resubmit the job. The application may
have to be split into two applications. If you cannot find a valid reason for the error, contact your system programmer.
System programmer response: Review the TME 10 OPC message log to determine the cause of the error. If you
cannot determine the cause and the error persists, contact your IBM representative. If the current AD record is valid,
it may become necessary to change the maximum record size of the AD file. The recommended way of doing this is
to define a new VSAM cluster similar to the current AD file but with a larger maximum record size. Copy the current
AD file to the new AD file using IDCAMS REPRO. Change all JCL referencing the old AD file to instead reference the
new AD file. Restart the TME 10 OPC controller and retry the failing AD file update request.
342 TME 10 OPC Messages and Codes
