EQQN011E EQQN016I
System programmer response: Scratch and reallocate the job tracking log data set at a suitable moment when
TME 10 OPC is stopped.
EQQN011E A SEVERE ERROR, SYSTEM ABEND
ABEND
, OCCURRED WHILE ATTEMPTING TO UPDATE
CURRENT JOB TRACKING LOG DATA SET
Explanation: An abend occurred when an TME 10 OPC function attempted to write a record to the current job
tracking log dataset. If the abend code is SB37 or SD37, then the current job tracking log dataset is too small.
System action: TME 10 OPC attempts to switch to the next job tracking log file. If this process is successful, the
log record will be written to the next log instead. The NMM subtask is posted to take a backup of the current plan.
TME 10 OPC administrator response: Contact your system programmer.
System programmer response: If current job tracking log dataset is too small scratch the current data set and
allocate a larger one at a suitable moment when TME 10 OPC is stopped. Instructions can be found in
TME 10 OPC
Customization and Tuning
.
EQQN012I OPC/ESA JOB TRACKING EVENTS ARE NOW BEING LOGGED ON FILE
DDNAME
Explanation: The NMM subtask has switched to the next available job tracking log dataset. This is done after every
current plan backup. If dual logging is requested, the dual log dataset will also switch to the next available dataset.
System action: Normal TME 10 OPC processing continues.
User response: None.
EQQN013I OPC/ESA JOB TRACKING IS NOW ACTIVE AND CURRENT PLAN DD-NAME IS
DDNAME
Explanation: The NMM subtask has started successfully and there is a current plan available.
System action: Normal TME 10 OPC processing continues.
User response: None.
EQQN014I THE JOB TRACKING LOG DATA SET, DDNAME
JTFILE
, HAS BEEN USED TO UPDATE THE
CURRENT PLAN.
NUMBER
EVENTS HAVE BEEN APPLIED TO DD-NAME
DDNAME
Explanation: The NMM determined that the current plan dataset could not be used. A new current plan has been
created by starting from the old current plan and reprocessing events logged on the job tracking log dataset.
System action: Normal TME 10 OPC processing continues.
User response: None.
EQQN015I A VSAM DATA SET WAS SUCCESSFULLY COPIED: FROMDD=
FROMDD
, TODD=
TODD
Explanation: A TME 10 OPC subtask has finished copying a VSAM dataset to a backup dataset.
System action: Normal TME 10 OPC processing continues.
User response: None.
EQQN016I DDNAME OF CURRENT JCL REPOSITORY DATA SET IS
DDNAME
Explanation: The JCL repository dataset name in use after a copy is
DDNAME
.
System action: TME 10 OPC processing continues.
User response: None.
216 TME 10 OPC Messages and Codes