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!
asked 31 May '11, 18:06
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.
answered 01 Jun '11, 07:17