|
ABAP Tutorials -
ABAP Data Interfaces
|
|
Written by admin
|
|
Sunday, 21 September 2008 08:52 |
|
To get an overview of background jobs, use the Job Overview function - menu path “ System -> Services -> Jobs -> Job Overview ” or “ GoTo -> Job Overview ” from the Job definition screen (transaction “SM37”). In the Job Overview, you can see the status of background jobs: - Scheduled - The job has been created, but it has not yet been assigned a starting date.
- Released - The job has been created and it has been assigned a starting date.
- Ready - The job is ready to be processed.
- Active - The job is being processed.
- Finished - The job has finished successfully.
- Canceled - The job did not finish successfully. A job will be “canceled” if any warning, error, or abend messages occur within one of the programs or within the system.
From this Job Overview, you can manage background jobs (i.e., release, change, delete, display, etc.). You can also display the job log for a particular background job (see next slide) and view or print its spool list.
Job Analysis using a Job Log
The job log of a background job will indicate when the job started, when each of the job steps started, and when the job finished.
Along with the system messages indicating the progress of the job, any program messages will be displayed in the job log. System messages:
- Step 001 started (program....)
This job log is particularly useful when a background job is cancelled (see above slide). In this case, you can find out what error caused the cancellation by examining the entries in the job log. You can determine the message class and number by looking at the Msg. ID column. For example, the message text “484 ” is an error message number 000 from message class ZSDRSB with this information, you can debug the program to find out where this message is issued within the program.
Job Analysis using a Job Spool
When a report is run in the foreground, the output is typically lost when the user goes out of the report (unless additional logic was coded to capture the output in some other medium, such as an email message or an output file).
In contrast, when a report is run as a job step, the screen output is captured in the spool list and can be viewed at a later time.
|
ABAP Tutorials 
