SAP Note 16201 - Background program, timeout, SAPMSSY6

Symptom:

A background program was canceled due to timeout.

Reason and Prerequisites

On every application server some ABAP/4 background programs are run at an interval of 5 minutes (rdisp/autoabaptime =300). The programs are executed under control of the program SAPMSSY6 and under the user identification SAPSYS and perform monitoring and control functions for the CCMS. The execution time of these programs is usually less than 2 sec altogether.
Caution: Other background programs that have nothing to do with the programs described here are also run under the user SAPSYS!
The programs are subject to run-time monitoring to ensure that the load on the application server is kept to a minumum. If one of these programs exceeds a run time of approx. 10.30sec twice in succession or a run time of 120..240sec onc (depending on the program), it will not be executed on this day.
The longer run time is intended to allow program generation or make it possible to tolerate temporary malfunctions.
The allowed runtimes should usually be sufficient. If programs are taken out of the execution schedule repeatedly, this may be due to a serious performance problem. The most frequent reasons are network problems, too much load on the database, or to much paging activity on the computer.

List of background programs:

+------- Maximum runtime (twice in succession)
| +- Maximum runtime (once)
Program name | | Task
------------------------------------------------------------------------
RSRZLST0 30s 120s Operation mode control
RSRZLLG0 10s 120s Login load distribution
RSALSUP1 15s 120s Operating system alerts
RSALSUP2 15s 120s Buffer alerts
RSALSUP3 15s 120s Spool alerts
RSALSUP5 30s 240s Database alerts (only on central appl.server)

The program status is kept in a local resident table. You can display
and change this table as follows:
- RZ03 (select) -> Utilities -> More utilities -> Contr/St.Area
- Report RSALTST4
- SMLG -> Supplements -> Background diagnost. (fr. 21I, 22C) or
- SMLG -> Goto -> System diagnoses -> Cyclic system prog. (as of 3.0x)

Example: Status table

Program name Status Dur. Start time Status text
--------------------------------------------------------------------
SAPMSSY6_RSRZLST0 0 0 19941222 184840
SAPMSSY6_RSRZLLG0 1 0 19941222 184840 running/disabled
SAPMSSY6_RSALSUP1 0 0 19941222 184330
SAPMSSY6_RSALSUP2 0 1 19941222 184330
SAPMSSY6_RSALSUP3 0 20 19941222 184331
SAPMSSY6_RSALSUP5 2 45 19941222 162310 disabled

This example shows:
RSRZLST0 was executed at 18:48:40 with a runtime of < 1 sec.
RSRZLLG0 is running
RSALSUP1, RSALSUP2, RSALSUP3 were executed at 18:43:30
RSALSUP3 has exceeded the allowed runtime of 15 seconds and must
take less than 15 seconds the next time in order to remain in the execution schedule.
RSALSUP5 has last been started at 16:23:10. The runtime was 45 sec the program has been taken out of the execution schedule because it has previously exceeded the allowed runtime of 30 sec.
The SMLG -> display looks as follows:
+----------------------------------------------------------------------+
| Diagnostic of CCMS background processing in the report SAPMSSY6 |
+----------------------------------------------------------------------+
| Application server Problem |
+----------------------------------------------------------------------+
| Database monitoring for alerts deactivated |
+----------------------------------------------------------------------+
The key ([Permit] deletes the corresponding status entry and the program will be executed.

Solution
If no user action takes place, the program will be executed after
midnight.
If you want to release the program for execution immediately, you can delete its status entry.
Proceed as follows:
Display th
e table as described above and delete the entry.
Either
- RZ03 (Select) -> Utilities -> More utilities -> Contr/St.Area
or
- Run the report RSALTST4 (SRVNAME empty -> Server to which you are logged on)
and then
- place the cursor on the status of the program concerned and press
the [Delete] key
It is easier to use SMLG (from 21I, 22C onwards):
- SMLG -> and so on (see above)
place the cursor on the line concerned, press the Permit key.