JR33776: Allow SAP job logs (SM37) to be kept after the ABAP stage execution is finished - for data transfer methods RFC and FTP.

APAR status

• Closed as program error.

Error description

• Currently, when an ABAP extract completes, the logs seen in
  transaction SM37 in SAP are deleted. The customer would like to
  save the logs seen in transaction SM37 after the ABAP job has
  run. Basically, the physical logs reside on the operating system
  of the SAP application server. The logs' name contains the job
  ID number and looks something like this: 0001X12002401X52642 SAP
  transaction code SM37 reads these logs based upon what it finds
  in the Tempse database.  When jobs are deleted, they get removed
  from Tempse and from the operating system at the same time.
  
  Additional request: implement the above for FTP data transfer
  (in addition to RFC)
  

Local fix

Problem summary

• SAP job logs (SM37) are deleted after the ABAP stage execution
  is finished
  

Problem conclusion

• JR33776 allows SAP job logs (SM37) to be kept after the ABAP
  stage execution is finished.
  This patch introduces a new environment variable
  DSR3_ABAP_KEEP_BG_JOB. Set DSR3_ABAP_KEEP_BG_JOB=1
  in DataStage Administrator Client to prevent the SAP job logs of
  ABAP background jobs from being deleted.
  Support for ABAP jobs with FTP transfer method is also included
  in this patch.
  

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