Under no circumstances should any GUI, documentation or correspondence refer to the keyword HOST without making it exactly clear WHICH flavor of HOST it's referring to:
TCP/IP connections – If you are connecting over TCP/IP, the database
server name (specified by the
ServerName (SERVER) connection
parameter) is no longer mandatory if a
host name is provided with the HOST
connection parameter. See Host
connection parameter.
Note: I am yet to be convinced that the HOST connection parameter offers any meaningful advantages over the HOST protocol option. AFAIK in V12 both are (by default) no longer just hints. Also, there's one disadvantage that is a showstopper in some applications: no extra TCP/IP parameters other than PORT when using the HOST connection parameter (you can't use LINKS to get them). ...but, I await convincing that I should store a new and somewhat limited technique in my definitely limited meatspace 🙂 - Breck
To clarify: Older versions cannot use the HOST connection parameter, i.e. "%SQLANY11%bin32dbisqlc" -c "HOST=MyHost;DBN=MyDatabase;UID=MyUser;PWD=MyPwd" will give an "invalid connection parameter" error.
Correction: The HOST connection parameter is recommended over LINKS. It is still recommended to use SERVER (ENG) as well as HOST, but you no longer need to.
Late reply, I know, but this is great exhortation, Breck. For our next release, the docteam will take a look at existing references to HOST in the docs and make sure we're being specific enough.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.