Symptom:
a) The last line in the SLOG file that starts with "START" or "STOP" has the form
START tp_getprot.......
b) After the above line, you will find in the SLOG file, and in addition to further messages, a line of the form:
Background job not running properly. Function: ... Jobcount: ... Status: Y
This line can occur repeatedly.
Solution:
Log on to the SAP system as the DDIC user. Call transaction SM37. Enter the following search criteria:
Job name: RDD*
User: DDIC
Selection date: leave these fields empty
Only jobs with status "Ready".
If an entry is found, position the cursor on the job name and use the menu item "Job -> Display" and on the following screen the menu item "Process -> Job details". On the following screen, you find the ID number of the job. Compare this number to the number which is referred to as "Job count" in the above SLOG message. (If several jobs were selected, examine all jobs this way). If the ID number should match the job count entered, an unexpected status is contained in the batch system.
This status could indicate a permanent error in the batch system. Refer to Note: 37104.
If the unexpected status of the entire batch system was only temporary, then you can solve the problem for the transport as follows:
a) To maintain the TRJOB table, use Transaction SM31.
b) Select the entry which matches the above SLOG message concerning the value "Function" and "Jobcount". Delete this entry.
c) If the transport control program continued running during these examinations and did not make any progress due to the temporary problem in the batch system, the transport control program (tp) will continue its work as soon as you have corrected the above error. Otherwise, start the transport control program with the same parameters as during the last call for which you noticed hanging transports. If you do not know the parameters or are not sure, start the following call:
tp getprots <SID>