JR43304: JOB SPORADICALLY FINISHES WITHOUT PROCESSING DATA WHEN FOLLOWING ANOTHER ABAP JOB

APAR status

• Closed as program error.

Error description

• Job runs successfully but ABAP stage extracts 0 rows when it
  closely  follows the execution of another job with ABAP extract
  stage. Both jobs use the same program id.
  

Local fix

Problem summary

• Job runs successfully but ABAP stage extracts 0 rows when it
  closely follows the execution of another job with ABAP extract
  stage.
  

Problem conclusion

• Code fix: Switched from multiple to single "end of data" signal
  from the generated ABAP program.
  The code fix affects both the Runtime and the Client, so
  separate patches will be generated for each.
  The Runtime (server) patch removes an extraneous
  RfcWaitForRequest+RfcDispatch from the RFC Server
  implementation.
  The Client patch changes the generated code for the ABAP program
  (the form RFC_CALL_END_DATA) so only one "end of data" signal is
  generated.
  After installing both patches, the user needs to regenerate the
  ABAP programs for the jobs affected by the issue. It's not
  necessary to
  regenerate all programs, just the ones affected; the old ABAP
  programs that were running fine before the patch will continue
  to run fine.
  

Temporary fix

Comments

APAR Information

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

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

Fix information

• Fixed component name

  IS PACK FOR SAP

• Fixed component ID

  5724Q5500

Applicable component levels

• R650 PSY

     UP

• R700 PSY

     UP