CONNECT statement in a script does not automatically connect. (64701)

When running a CONNECT statement in a script through Quest Script Runner, a prompt to specify the database is given and does not automatically connect.

i.e. CONNECT someuser/pswd@database1

TNS entry uses fully qualified database alias of database1.prod.server.corp. This CONNECT string prompts for connection info.

Database name is not recognized and not found in the tnsnames.ora file. Either the database name is incorrect or it is not fully qualified to match the TNS info entry.

Check the TNS entry for that database in the Oracle tnsnames.ora file.

Either fully qualify the database name in the script, or add a new TNS entry that specifies the partial database name in the .ora file.

i.e. Using CONNECT someuser/pswd@database1.prod.server.corp does work

or add a TNS entry that specifies the partial database alias of database1 instead of just database1.prod.server.corp.

Changes in the new (10.5) QSR has made fully qualified database names in the CONNECT statement required.