DataStage ABAP job running in the background aborts due to time-out

-

Technote (troubleshooting)


Problem(Abstract)

DataStage ABAP job aborts with the following error:

Fatal: ABAP_E_00745`:`ABAP background job time-out occurred as defined using BG_JOB_TIMEOUT property.

Symptom

When we create a new job, it aborts in 10 minutes (600 sec) with the error:

ABAP background job time-out occurred as defined using BG_JOB_TIMEOUT property.

Is there any environment variable that needs to be set which defines this property? Existing jobs have the ABAP background time-out set to 100,000 seconds.


Resolving the problem

There is a new stage property, ABAP background job time-out limit (BG_JOB_TIMEOUT), that can be used to adjust the time-out value. To see the property you need to open the ABAP stage in Grid Style.  To do this right-click on the ABAP stage and select Grid Style.  Then select the Outputs > Properties tab and scroll all the way to the bottom to see ABAP background job time-out limit, which is the maximum time in seconds that an ABAP background job may remain the 'Released' state after being started.  The default value is 600 seconds (10 minutes).



Popular posts from this blog

Shrink you container size up to 95%.

-
BLAFS is a bloat-aware filesystem for container debloating. The design principles of BLAFS are effective, efficient, and easy to use. It detects the files used by the container, and then debloats the container by removing the unused files. The debloated containers are still functional and can run the same workload as the original containers, but with a much smaller size and faster deployment. https://github.com/negativa-ai/BLAFS?tab=readme-ov-file
Read more

alma linux: dnf Module yaml error: Unexpected key in data

-
While applying recent updates to a server running Rocky Linux 8, an error presented itself. Module yaml error: Unexpected key in data: static_context [line 9 col 3] Module yaml error: Unexpected key in data: static_context [line 9 col 3] The solution turned out to be a simple one. Update the libmodulemd first to correct the problem then perform the dnf updates as usual. dnf update libmodulemd For a detailed explanation as to the cause of this problem.
Read more