SAP SM37

It monitors background jobs, showing their status (scheduled, released, active, finished, cancelled), logs and spool, the go-to for batch-job operations.

• Selection: job name, user, date range, status.
• Job list with status and timings.
• Job log and spool (output) per job.
• Actions: release, cancel, repeat.

• Investigate cancelled jobs via the job log (and ST22 for dumps).
• Filter by status to find failures quickly.
• Use SM36 to define/schedule jobs.

• Cancelled jobs (check the log for the cause).
• Jobs delayed by too few background work processes.
• Missing authorization to view other users’ jobs.

• Leaving the user selection at your own name. The default hides everybody else's jobs, which is how somebody concludes nothing is scheduled.
• Reading finished as succeeded. A job that selected nothing and did nothing finishes green, and no standard check reports it.
• Not opening the spool. The job log records that the program ran; the spool holds what it produced.
• Restarting a failed job before reading why it failed. Most cancellations repeat, and the second run wastes the window the first one lost.
• Ignoring duration drift. A job growing from ten minutes to two hours is a warning nobody receives, because it has not failed yet.