Why are all system queues blocked?

Owned by Alena Saeuberlich
Last updated: Jun 30, 2021

 

Problem

When importing transports via the system queue, it is blocked; the import is canceled.

Cause

The system queue can be locked for various reasons:

  1. The lock was caused by a faulty transport (e.g. return code 12). In this case, the system queue was blocked for security reasons, based on the threshold value maintained in the global settings.

  2. After a database copy, the error message "TM system has been reset" appears in the Import Scheduler Monitor and all queues are blocked.

  3. Inconsistent entries in the table / RTC / TM_SCTM on the TM server and target system caused by:

    1. An aborted RFC connection to the TM system while a job is running

    2. Different system times for TM server and target system

 

Solution

to 1.: Check the faulty transport and make the necessary adjustments.

Unlock the system queues and repeat the import.

 

Alternatively, change the return value in the global settings:

Call up TM: Execute transaction / RTC / TM> Open the "Global settings" menu> Open the "Global settings" menu. ???

Set a higher value for the return code:

Note: The return value specified above is only taken into account for the "Single" import mode. In the "Bundled" import mode, the behavior is determined by the termination value for "tp" defined in the TMS.

Save the settings.

 

To 2./3 .:

Clear restore flag:

  • If the connection on the system is interrupted (RFC problem, downtime, etc.), the TM blocks the queues for imports, as a restore must be assumed. Even if you have not reset the system, you have to clear the restore flag in this case (it is not necessary to synchronize the import database in this case). Clear the restore flag using TM Tools.

  • Check whether the import mode is set correctly in the TM settings. For the "bundled" mode, "CTC = 1" must be set in the tp settings. (Transaction STMS> System overview> double click on the system> TransportTool)

 

Check REALTECH job on the target systems for obsolete SIDs:

  • Call up transaction SM37 and filter for jobs with the program name / RTC / TM * to get a list of all REALTECH jobs.

  • Delete all import jobs that indicate an old SID or incorrect transport level. These can be recognized by the string "@@" in the job name.

  • Alternatively, you can delete all import jobs and schedule them again using the REALTECH scheduler.

 

Check tables / RTC / TM_SCTM and / RTC / TM_LOCK:

  • The user who triggered the lock can be identified in the / RTC / TM_LOCK table in the AS4USER field.

  • Deleting the entries in the table / RTC / TM_SCTM on the TM system and deleting the relevant entry in the table / RTC / TM_LOCK can solve the problem in special cases.