IDX / VMS Connection

[Tim Malaney]

Were moving a site from one server to another and cannot get an IDX interface running on VMS to connect to the new IP. We just inherited the IDX system and have little VMS background. We’ve looked at the obvious, can ping, ftp and telnet from server to server. No firewall exists. The status on the IDX app stays in “Starting”. At VMS, “tcpip netstat” never shows the IP of the new server. “show net” only shows the “old” server IP. Is there an operating system setup required for it to recognize the new IP/Server inVMS?

Thanks

Tim

Topic

[David Harrison]

Do you have a route set up to the new ip on VMS?

[Tim Malaney]

This is a feed from IDX to Cloverleaf. The port on Cloverleaf shows up and listening.

[Kevin Scantlan]

Did you bring the server side up first and then bring up the client side?  This is what we call our IDX 2-step dance.  When we go down we take the client side down first, then the server.  When coming back up just the opposite.

[Tim Malaney]

Thanks but no luck.

[Anonymous]

Tim,

You might try using ‘hcitcptest’ instead of Cloverleaf to make a connection.  The utility is a simple socket program and if you’re not connecting to it you certainly can’t connect to Cloverleaf.  I always use it first because it’s a little simpler to set up than a Cloverleaf thread (if you can believe that!) and it sometimes reveals things that aren’t obvious in Cloverleaf.  For instance, I had a connection one time that was sending a startup message and disconnecting right away when it didn’t get a response.

[Tim Malaney]

Thanks for the suggestion. It did not show anything. This is a matter of being IDX/VMS challenged. Just moving a site from one server to another. Able to connect with this exception. Vendor thinks it’s at the OS level. Just was hoping someone else was running IDX on VMS that may have some insite.

[Author]

Replies