cancel
Showing results for 
Search instead for 
Did you mean: 

Job event sap_system_start triggers too soon

Former Member
0 Kudos

Hello Basis Experts,

We need your help and inputs in this problem. Appreciate you response.

We need to execute a few application jobs at system restart. So, we have scheduled these jobs as recurring and to trigger after event SAP_SYSTEM_START.

Our basis team restarts the SAP system using stopsap and startsap commands. We notice that the job starts within 40 seconds of the startsap command and the system has probably not restarted completely. As a result, the job hangs. We see no movement in the work process in sm50.

We are also not able to 'stop' the job from sm37 job overview. We have to kill the process from sm50.

The program that the job uses, calls an abap proxy, via the integration engine. The call goes to PI and is routed back to the SAP to trigger an interface (we had to do this to warm the buffers (load the program and ddic in memory, as the interface is time sensitive).

Thank you in advance.

Regards,

Salai.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Thank you Adam. I will try this and check again.

csaba_goetz
Contributor
0 Kudos

Hello Salai,

Check if increasing rdisp/startup_time profile parameter to 60 improves the situation. This parameter controls when to start the first autoabap etc. scheduling, so it should help.

Best regards,

Adam