dbisql command line connection string behaviour change?

[thomas_duemesnil]

Hello.

I have multiple instances running. For each instance i have create links that start dbisql.exe with the Connection String for that instance. In the String i don't include the Password for security reason.

The behaviour since years the behaviour was that isql starts up with all parameters from the connection string prefilled in the Connections screen.

I installed EBF 17.0.11.7312.

Now the ENG and DBN paramters are missing from the dbisql login screen.

My command line is

"%SQLANY17%\\Bin64\\dbisql.exe " -c "ENG=XXX;DBN=yyyy;UID=myuser;links=tcpip(host=x.x.x.x;port=2638)"

When dbi sql comes up the Server Name and Database Name fields are empty.

When I provide the proper password on the command line with the PWD= parameter the connection is established correctly. So I see no problem with my code here.

The same call with the Client of ASA16 is working as expected.

"%SQLANY16%\\Bin64\\dbisql.exe " -c "ENG=XXX;DBN=yyyy;UID=myuser;links=tcpip(host=x.x.x.x;port=2638)"

Any ideas are welcome.

Probably somebody knows the latest version that is working without this problem.

Thomas

[regdomaratzki]

Working fine for me.

Is it possible that you used your v17 DBISQL to connect to an non-SQLA database (like IQ or HANA) at roughly the same time you upgraded to the new EBF?

When the connection dialog comes up, does the top left corner still say "Connect to a SQL Anywhere Database" ?

Does adding -sa to the dbisql command line help?

Reg

[VolkerBarth]

Is there a space before the closing double quote after DBISQL.exe?

[thomas_duemesnil]

Yes it is. But that doesn't make a difference. I have tried it. Thanks for your good eyes.

[thomas_duemesnil]

Hello Reg. No I connect to a normal SQL Anywhere instance. The caption of the screen shows "Connect to a SQL Anywhere Database"

Adding the -sa Parameter doesn't change the behavior.

When you say working fine for me you use the same EBF 7312 as me?

Thanks for helping. Thomas

[jack_schueler · Accepted solution]

This issue will be corrected in a later release (CR 828167).