Sorry Rick,
First of all, I want to say that I'm really sorry I am only replying to your email now. I can get a little scatterbrained when life gets busy and lose track of even more important things.
Concerning how to set up "2 local transport domains for DEV and PRD" please consider the following:
Example of initial Set up:
- DEV as Domain Controller and Local DIR_TRANS (/usr/sap/trans)
- PRD connected to Domain Controller DEV and Remote DIR_TRANS via QFileSvr.400 (/usr/sap/trans)
Configuration of 2 Local TMS :
- Check whether SIDADM (SIDOFR) are present on both side and have the same password
- Remove the symlnk for DIR_TRANS on PRD Server
- Copy the local DIR_TRANS on DEV to a local DIR_TRANS on PRD (SAVF)
- Log on to PRD Client 000 and delete the TMS configuration (T-Code STMS)
- Distribute the TMS Configuration and also check in DEV
- Create a new Domain Controller in PRD and activate the configuration.
- Log on to PRD domain controller client 000 T-Code STMS --> SAP System --> create --> Domain link Enter the parameter for DEV system.
- You can now see that you have requested the domain link to the other domain in the system overview.
- Log on DEV domain controller client 000 T-Code STMS --> SAP System --> Approve
- Confirm and distribute the configuration.
You can now see all systems in both domains in the system overview and the import overview, but you still need to adjust the transport route.
- Log on DEV domain controller client 000 T-Code STMS --> Overview --> Transport Route --> Edit
Create a new Transport route and add PRD system.
Now once you release a transport in DEV the import queue of PRD shows the requests to which the transport files must still be transferred. .
It looks too many work steps but it isn't when you are a bit familiar with the STMS concept.
If you are still interested in the cleanup command please send me the error message.
Regards,
Hadi