|
Measures reported by AsAbapStdJobTest
SAP background processing automates routine tasks and helps you optimize your organization’s SAP computing resources. Using background processing, you tell the SAP System to run programs for you. Background processing lets you move long-running or resource-intensive program runs to times when the system load is low. It also lets you delegate to the system the task of running reports or programs. Your dialog sessions are not tied up, and reports that run in the background are not subject to the dialog-step run-time limit that applies to interactive sessions.
The SAP System offers sophisticated support for background processing. You can choose from a variety of methods for scheduling and managing jobs. You can run both SAP-internal and external programs. And, for easier scheduling and management, you can run related programs as “job steps” within a single background processing job, allowing a single background job to accomplish a complex task that consists of multiple processing steps.
Often job execution takes too long when the job consists of too many complex tasks. This prolonged execution of a job may consume a considerable amount of resources and therefore hamper the execution of other background jobs. In order to figure out the background jobs that are executing for a longer time and the status of the job, administrators may use the AsAbapStdJobTest test!
This test monitors the current status and the previous status of each background job that is executing, the time taken for job execution and the time delay encountered by the jobs during execution. This way, administrators can figure out the background job that is executing for a longer duration and blocking valuable resources.
The measures made by this test are as follows:
| Measurement |
Description |
Measurement Unit |
Interpretation |
| Status |
Indicates the current status of this job execution. |
|
The values that this measure reports and their numeric equivalents are provided in the table below:
| Measure value |
Numeric value |
| N/A |
0 |
| Planned or Scheduled |
1 |
| Released |
2 |
| Ready |
3 |
| Active |
4 |
| Finished |
5 |
| Cancelled or Aborted |
6 |
Note:
By default, this measure reports one of the values listed under Measure Values to indicate the current status of this job execution. In the graph of this measure however, the same is represented using the numeric equivalents i.e., 0 to 6 only. |
| prevstatus |
Indicates the status of this job that was executed before the last known execution of this job. |
|
The values that this measure reports and their numeric equivalents are provided in the table below:
| Measure value |
Numeric value |
| N/A |
0 |
| Planned or Scheduled |
1 |
| Released |
2 |
| Ready |
3 |
| Active |
4 |
| Finished |
5 |
| Cancelled or Aborted |
6 |
Note:
By default, this measure reports one of the values listed under Measure Values to indicate the status of the job execution before the last known execution. In the graph of this measure however, the same is represented using the numeric equivalents i.e., 0 to 6 only. |
| Duration |
Indicates the total time taken to execute this job. |
Minutes |
Compare the value of this measure across the jobs to figure out the job that took too long to execute. |
| Delay |
Indicates the time delay encountered by this job during execution. |
Minutes |
A low value is desired for this measure.
If there is an alarming increase in the value of this measure, it indicates that adequate background processes are not available for executing this job. The background processes may not be available when there are too many job executions and when a job is executing endlessly. In such cases, administrators need to overlook the issue and rectify the same before any serious performance degradation of the server occurs.
Comapring the value of this measure across the jobs will help you identify the job that encountered the maximum time delay. |
|