PQ15943: EQQE043W JOB START OR JOB END EVENT RECEIVED FOR IFAONJ15 EQQE043I IS NOT CONSISTENT WITH CURR. OPC/ESA STATUS OF THIS JOB

APAR status

• Closed as program error.

Error description

• EQQE016I ETT HAS SUCCESFULLY ADDED IFAONJ15ZPA FOR TRIGGERING
  EVENT IFAONJ15
  ........................
  EQQE043W JOB START OR JOB END EVENT RECEIVED FOR IFAONJ15
  EQQE043I IS NOT CONSISTENT WITH CURR. OPC/ESA STATUS OF THIS JOB
  -----------------------------------------
  OUTPUT.
  Here is missing A2
  .
  Enhancing problem description:
  One of the ways this problem may show up is with a failure of
  CP BATCH EXTEND/REPLAN jobs with MSGEQQN043E RC08 RTN08 on the
  NCP.  This is a DUPLICATE RECORD ERROR on JOBNAME TABLE RECORDS
  -- JNT -- usually for jobs which are in COMPLETE status.
  .
  When this problem surfaces, it can usually be bypassed by
  setting BATCHOPT keyword PREVRES(NO) and resubmitting the
  failing job, or by identifying and deleting the operation and
  occurrence identified by the MSGEQQN043E issued by the failing
  batch job.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED: All OPC customers using the ETT              *
  *                 functionality.                               *
  *                                                              *
  *                 FUNCTION=EM Event Manager                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: OPC does not track correctly a job      *
  *                      that is the trigger for adding a        *
  *                      new occurrence to the CP through        *
  *                      ETT. Message EQQE043W is issued for     *
  *                      the job.                                *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When a job is used as a trigger to add a new occurrence to
  the Current Plan and must also be tracked by OPC, if the start
  event is received before the reader event sometimes the Event
  Manager is not able to match the subsequent events and the job
  is not tracked correctly.
  

Problem conclusion

• The Event Manager code has been changed in order to handle
  properly the situation in which the reader events arrives
  after the start event.
  102Y
  EQQEMJPR
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

  PQ04306

• APAR is sysrouted TO one or more of the following:

  UQ17778

Modules/Macros

• EQQEMJPR
  

Fix information

• Fixed component name

  TME 10 OPC V2 R

• Fixed component ID

  5697OPC01

Applicable component levels

• R102 PSY UQ17778

     UP98/05/19 P F805