topic Re: Multinet to TCP/IP migration in Operating System - OpenVMS

Multinet to TCP/IP migration

Gary_167 — Mon, 26 Jul 2004 08:28:36 GMT

Hello, does anyone have any experience in migrating from Multinet (4.3) to TCP/IP (5.4 or 5.5)? Is there any documentation from HP on this?

Re: Multinet to TCP/IP migration

Art Wiens — Mon, 26 Jul 2004 12:12:39 GMT

I think you're on your own...but enough MULTINET SHOW commands should give you a good picture of what your IP config looks like. You can also wade through MULTINET_ROOT:[MULTINET]START_MULTINET.COM . Much of your configuration is in there.

Its a matter of configuring TCPIP to match after that.

Art

Re: Multinet to TCP/IP migration

Gary_167 — Mon, 26 Jul 2004 12:20:47 GMT

can both applications be loaded at the same time or do i have to uninstall multinet before loading TCP/IP?

Re: Multinet to TCP/IP migration

Wim Van den Wyngaert — Mon, 26 Jul 2004 14:34:04 GMT

Gary,

Never saw multinet but
1) applications may be linked with some olb/exe of it and may fail if multinet is not available. Relink them !
2) you should compare all timeout settings (e.g. keepalive) or get appl;ication hangs.
3) test test test

Wim

Re: Multinet to TCP/IP migration

Art Wiens — Mon, 26 Jul 2004 14:41:01 GMT

I don't imagine trying to "run" both products at the same time would yield "desirable" results! But you don't have to uninstall Multinet, just turn it off when you want flip over to TCPIP. I believe the command to turn it off is:

$ MULTINET CONFIGURE /SERVERS
SERVER-CONFIG> shutdown

This stops the master process. Alternatively, comment out the startup command procedure and reboot, which might not be a bad idea...gets rid of all the Multinet logicals etc.

Why the switch away from Multinet?

Art

Re: Multinet to TCP/IP migration

Gary_167 — Mon, 26 Jul 2004 15:31:53 GMT

Thank you all, Multinet is no longer supported by Oracle.

Re: Multinet to TCP/IP migration

Martin P.J. Zinser — Mon, 26 Jul 2004 21:30:44 GMT

Hello Gary,

http://www.process.com/tcpip/mndocs/MN%20v5.0%20Installation%20Administrator%20Guide/Ch09.htm#E55E56

has an overview of the various configuration files used by Multinet and what they contain (and how to access them). Obviously you do need to mirror this information in the new TCPIP setup. My advise would be to invoke tcpip$configure, start with the first menu and followup through all the submenus ;-). If you know IP in general and have an idea of your network this should not take more than about an hour at most (assuming a moderatly difficult network environment, if you do have 10 Ethernet interfaces in the box and do all kinds of "interesting" routing between the various networks it might take longer ;-)

Other things to consider are in-house developed applications that might use Multinet specific features, third party should be fine, they will use the UCX compatibility mode of Multinet anyhow.

As mentioned before, testing is your friend :-), especially make sure to test your environment under network load.

Greetings, Martin

P.S. Is 5.5 already out?

Re: Multinet to TCP/IP migration

Steven Lovjejoy — Wed, 28 Jul 2004 18:17:03 GMT

Process Software is fully committed to supporting UCX emulation in our MultiNet product. Past versions of MultiNet were directly certified by Oracle, but currently are not - although we are working to rectify this. As a result, Process Software conducts its own 3rd party certification to ensure full UCX emulation in the MultiNet product.

We have many customers successfully using MultiNet with Oracle and will take very seriously any problems you might discover relating to UCX emulation and Oracle.

Steve Lovejoy, Technical Manager
Process Softare

Re: Multinet to TCP/IP migration

Gary_167 — Thu, 29 Jul 2004 07:53:47 GMT

Steven, that is good to know, is MU4.3 certified under VMS 7.3-2?

Re: Multinet to TCP/IP migration

Geoff Bryant — Tue, 03 Aug 2004 09:04:16 GMT

MultiNet works fine with VMS 7.3-2.

As to MultiNet v4.3, please be aware that we recently released MultiNet v5.0. Since we support the current version and one back (which is MultiNet 4.4), you should consider moving forward.

Geoff Byant
Process Software

Re: Multinet to TCP/IP migration

Lawrence Czlapinski — Thu, 19 Aug 2004 14:35:38 GMT

Some of our users use automatic login (ALF)from their PCs to VAXes running Multinet. We could not get automatic login to work with TCP/IP. TCP/IP puts port number in the header in a way that interfered with our getting the TCP/IP address authorized.