After you implement routing rules and create user mappings, you can monitor the results from Unity session list in the Unity UI or at the unityadmin prompt.
All session related actions, such as stopping and aborting a session, must be performed from the Unity environment and not directly on the managed Teradata system. If you attempt to manage a session on one of the managed Teradata systems, Unity treats the action as a system failure and automatically restores the affected session to its previous state.
The Unity UI and the unityadmin command line allow you to stop sessions in either passive or managed mode. Additionally, you can stop all sessions using the same routing rule from unityadmin.
You can also abort the current transaction in managed sessions from the Unity UI or the unityadmin command line. The abort command may take longer time because it must wait for a roll back of the transaction on the Teradata systems.