Potential risks migrating from Solaris to HP-UX

[Parkar Manda]

Presently we are running Solaris and planning to migrate to HP-UX. What would be the potential problems that we could come across during migration. We have around 1200 shell scripts(c, korn, POSIX). Our application was developed using C, MicroFocus COBOL, SQL and Java. We are running the following software.

- Solaris 7
- BEA Tuxedo
- NIS 95.08.07.15.02
- SPARCompiler C 5.0
- MicroFocus COBOL 4.1.20-e
- Perl 5.6.0
- Sun WebServer 2.0
- AutoSys 3.4

[Martin Johnson]

Make sure you get the latest patches for MicroFocus COBOL. We have some performance issues that were resolved with patches.

HTH
Marty

[harry d brown jr]

going from solaris to hpuc:

(1) you will try to slice disks
(2) stop-a doesn't work on hpux boxes
(3) sam is different than admintool
(4) you don't need veritas

- SPARCompiler C 5.0
will you be migrating to HP's "c" or to gcc??
- MicroFocus COBOL 4.1.20-e
check with MF to see differences
- Perl 5.6.0
check your modules on the perl you have on your solaris box, make sure you have at least same on hpux



live free or die
harry

[Patrick Wallek · Accepted solution]

I would suspect that your C and MF Cobol apps will probably have to be recompiled on the HP-UX machine.

With your shell scripts, if you use any nawk on the Solaris, then you will have to link nawk to awk on the HP-UX machine. Solaris' nawk is the same as HP-UX awk (nawk doesn't exist on HP-UX).

You may run into some other issues with your shell scripts as well.

The only thing I can is test, test, test and then test some more.

You probably won't get all the bugs worked out, but hopefully you can find the majority of them before you go live with the new machine.