Playback fails for a script and script name is damaged

The problem: Robotic script playback fails and the script name is damaged after being sent to the Application Management Configuration Editor.

The Robotic Response Time agent permits you to use several different script types, including Rational Performance Tester, Rational Functional Tester, and command line interface (CLI). If you create a script and include non-ASCII characters in the script name, the script name is corrupted when it is sent to the Application Management Configuration Editor. This problem occurs because of a known limitation in the way the product handles non-ASCII characters. As a result, when a script with a corrupted name is sent to the Robotic Response Time agents for playback, the playback fails.

The solution: Avoid using non-ASCII characters when naming scripts.