Clarification on Message Statement

[former_SQLA_member1694871]

In the process of working through our migration to SA12, I came across the following...

We have a procedure that we have created thats sole job is to create connection level variables that are used throught the life of that connection. Procedures, triggers, functions, etc., use these values throughout the database.

We set the values of these connection level variables, and then we display these values using the message statement (example)...

message 'connvar_comseq = ',connvar_comseq type info to console;  
message 'connvar_projectseq = ',connvar_projectseq type info to console;

If I have the network server engine running on our server, and I connect to that server from another client, all the messages that we have in our login procedure, show in the network server engine window (note, I'm not talking about the console utility). However, if I connect to our database from the machine the database server is running on, none of the messages are shown in the network server engine window when I connect to it.

Is there something specific that relates to the message statement that keeps it from displaying its results when you are connecting to that server from the same machine it is running on??? Seems like it works this way no matter what version of ASA or SQL Anywhere you are in.

Any info would be greatly appreciated!

TIA

Jeff Gibson
Intercept Solutions - Sybase SQL Anywhere OEM Partner
Nashville, TN

[VolkerBarth]

FWIW, I have routinely used MESSAGE statements with different action types both on local and network clients (from v5.5 to 12.0.1) and have never noticed any differences between local and network clients.

[Breck_Carter]

FWIW those message statements are not syntactically valid according to the Help... but the Help is clearly wrong when it says the string must be a single expression rather than a comma , separated , list.

[former_SQLA_member1694871]

Thanks for the heads up on that Breck. We put all our message statements in the database when it was living back in ASA6. Just looked at the help there and the comma is shown in the ASA Reference Manual. Very curious that the comma isn't there anymore in SA12. I'll have to see if pulling those commas makes a difference.

[Former Member]

I cannot think of any restriction that would limit the message statement to print messages to the engine window only when connected from a different machine. Are you using the same userid when performing both connection tests? If not, then is it possible that one of the userids does not have permission to execute the login procedure? If you are using the same userid, then try starting the server with the -o option and see if the output file has additional information that perhaps got lost in the engine console.

[former_SQLA_member1694871]

Added the -o options. Seems like with these tests, it has to do with the dba connection running that procedure at login. I've got a few more things to check and will post what I find!! Thanks Karim!!