Testing the database connection in the Development and Test Environment wizard can cause Rational Software Architect to stop responding. This is occurs when one of the scripts running under the covers picks up the wrong find command. The problem is typically because something like MKS Toolkit is installed, which includes its own version of the find command. You may not have installed MKS Toolkit manually, for example DataStage Designer installs MKS Toolkit automatically. The simplest way to check if this is the case, is to run the find command directly and check the output. You can use the start > Run... menu option to open a Command Prompt; type cmd in the Open box and press OK. You should see the following output when you run the find command:
If you see a different response, the Development and Test Environment wizard will fail when you try to test the database connection. To get round this problem you should modify the PATH environment variable so that the folder containing the default Windows find command is before any others. The article, "How To Manage Environment Variables in Windows XP" describes how to modify environment variables on Windows XP. The correct find command is in the same folder as cmd.exe, which you used above. This folder will already be in the PATH, but you need to move it to the beginning so that is checked before any of the other folders. This change will cause problems for any software relying on the the PATH to locate the alternative find command, so I recommend taking a copy of the PATH setting before you change it, then restoring the original settings after you have successfully set up your development environment.