what is the use of killing/terminating job in sm37 or sm50

[former_member601185]

If my target(dso) status is yellow colour my superior said to kill the job.

I need to know the use of killing the job in sm37 or sm50

I followed below steps sm50-menu-process-cancel with core.

They I got dump and turned status in red colour.

I have a doubt that I can directly change the status in target to red and delete the request but why I need to kill it??

Please provide your answers asap.

[former_member600276 · Accepted solution]

Hi Krishna,

The ideal way is to make the request "red" and then delete it. By doing this way, we don't miss a delta. To cross check request deletion, we go to SM37 and check if there is any job against the user ID or along with the Job Name and Job Start Time Combination. Sometimes, the backend process runs not letting other jobs to execute with the "Same" available process as that of your job. In order to make the process free, we delete it in SM50. Hope this helps 🙂

[kiran_k8]

Sindhuja,

Kill means nothing but stopping the job from running.It releases the workspace in the application server and let the other jobs run using the available workspace, effectively.

K.Kiran.

[former_member186445]

depending on when the dump occured in your loading process, the background job can keep running idle. At that point you have no choice but to kill the job.

[former_member186445]

depending on when the dump occured in your loading process, the background job can keep running idle. At that point you have no choice but to kill the job.

[former_member601185]

Hi Mario,

Will you please explain in detail.

Regards,

Krishna sindhuja