We are running a setup with a background job to execute this program and send emails to inform developers about issues.
The background job is set up correctly, it executed correctly, the SPOOL contains the right data, the job log shows no errors, no dumps and no errors caught in SU53, however, no emails were sent nor queued in SOST.
This seems to be expected, since there are COMMIT statements in CL_BCS that will not deliver when running in background (?)
Proposal to change from CL_BCS to CL_BCS_MESSAGE, since it doesn't commit until you call the send method, and it provides the option to set it in an update task, so a committable LUW.
We are running a setup with a background job to execute this program and send emails to inform developers about issues.
The background job is set up correctly, it executed correctly, the SPOOL contains the right data, the job log shows no errors, no dumps and no errors caught in SU53, however, no emails were sent nor queued in
SOST
.This seems to be expected, since there are
COMMIT
statements inCL_BCS
that will not deliver when running in background (?)Proposal to change from
CL_BCS
toCL_BCS_MESSAGE
, since it doesn't commit until you call thesend
method, and it provides the option to set it in an update task, so a committable LUW.I can put some work into this one myself.
For reference, a similar issue:
COMMIT CL_BCS email in background task