Locking/Unlocking TMS for an R/3 System

Prerequisites

In certain circumstances, you may want to lock an R/3 System for TMS accesses. If you have to stop an R/3 System for hardware maintenance, for example, it may make sense to communicate this to the other R/3 Systems in the transport domain. This will prevent unneccessary attempts to access an R/3 System that cannot be reached.

They are not displayed in the import overview. Neither display functions nor import functions are therefore available for R/3 Systems that have been locked.

If an R/3 System is locked for the TMS, all virtual R/3 Systems that have this R/3 System configured as a communications system are also locked.

Procedure

To lock an R/3 System, proceed as follows:

  1. Log onto the R/3 System acting as the domain controller.
  2. Call transaction STMS.
  3. Choose Overview ® Systems.
  4. This takes you to the system overview.

  5. Position the cursor on the R/3 System to be locked.
  6. Choose R/3 System ® Lock.
  7. Confirm the prompt and distribute the configuration.

The R/3 System has been locked for the TMS. All R/3 Systems belonging to the transport domain are informed that the R/3 System has been locked.

To unlock a locked R/3 System, proceed as follows:

  1. Log onto the R/3 System acting as the domain controller.
  2. Call transaction STMS.
  3. Choose Overview ® Systems.
  4. This takes you to the system overview.

  5. Position the cursor on the R/3 System to be unlocked.
  6. Choose R/3 System ® Unlock.
  7. Confirm the prompt and distribute the configuration.

The R/3 System has been unlocked for the TMS. All systems belonging to the transport domain are informed that the R/3 System has been unlocked.

If the TMS configuration of the transport domain has changed in the meantime, this is communicated to the R/3 System that is unlocked.