EQQW018E EQQW023E
EQQW018E SYSOUT CLASS
CLASS
IS ALREADY BEING PROCESSED BY ANOTHER JCC TASK
Explanation: A JCC task has been requested to process SYSOUT datasets in a SYSOUT class that is already being
processed by another JCC subtask on the same MVS system. The SYSOUT class can only be processed by one
JCC subtask at a time.
System action: JCC initialization is terminated.
Problem determination: The JCC subtask is started when either JCCTASK(YES) or CATMLVL(step) is defined in
the OPCOPTS statement. When the JCC is started for catalog management actions, the class or classes processed
by this JCC can be defined in the CATMCLAS keyword of the JOBOPTS statement. If CATMCLAS is not defined, the
classes checked by the JCC subtask are automatically determined by TME 10 OPC from the MSGCLASS value of
jobs and started tasks executing on this system.
System programmer response: Check the values of JCCOPTS CHKCLASS and OPCOPTS CATMCLAS of all
TME 10 OPC subsystems started on the system. If you use catalog management at step level, consider including the
CATMCLAS keyword to define the held SYSOUT classes used for production processing. Ensure that you do not
start more than one subsystem with CATMLVL(STEP), unless CATMCLASS is defined with different values for each
subsystem. Correct the error and restart the JCC subtask or the TME 10 OPC subsystem.
EQQW019E A SEVERE ERROR IN THE JCC TASK HAS CAUSED ONE OR MORE EVENTS TO BE LOST
Explanation: An abend in the JCC queue processing routine prevented the JCC from processing all queued jobs.
System action: MVS recovery/termination is requested to generate a dump. The JCC attempts to continue
processing.
Problem determination: Review the SYSLOG dataset, the TME 10 OPC message log, and the dump dataset to
determine the cause of the error.
Operator response: Check the ready list for the computer workstation that is serviced by the abending JCC task.
Check that all operations that have the started status are in fact executing. If necessary, set the correct status for
jobs that are listed as started but have completed execution.
EQQW021E THE EVENT WRITER OUTPUT DATA SET IS TOO SMALL
Explanation: The event writer requires that the event dataset is large enough to contain at least 100 events. The
dataset defined by the EQQEVDS ddname does not fulfill this requirement.
System action: The event writer processing is terminated. Message EQQW062E is issued.
System programmer response: Allocate a larger event dataset. If necessary, restart TME 10 OPC to pick up the
new event dataset.
EQQW022I THE JOB COMPLETION CHECKER ENDED NORMALLY
Explanation: JCC initialization has completed and the JCC has been requested to stop execution.
System action: TME 10 OPC processing continues.
User response: None.
EQQW023E UNEXPECTED SUBSYSTEM REQUEST RETURN CODES FOR JOB
JOBNAME
(
JOBNUM
) REQUEST
TYPE:
TYPE
, R15:
R15
, SSOBRETN:
SSOBRETN
Explanation: An error occurred when the JCC was retrieving information from the JES about job
JOBNAME
. The
information request is either a status request (request type = CS), or a process SYSOUT request (request type = SO).
R15
and
SSOBRETN
are return codes from JES. JCC issues this message because there is no code to handle this
combination of return codes.
System action: An incident record is written to the JCC incident log and the job is flagged as having encountered a
JCC error.
Operator response: Set the correct status for the job manually and delete or re-queue SYSOUT datasets for the job
if necessary.
298 TME 10 OPC Messages and Codes