HP11i migration

[Ryan Twombly]

I'm a programmer involved in an attempted migration of a library of proprietary software running under HP10.20 (32-bit) to 64-bit mode 11i. Any advice from the many of you who seem to be going through similiar exercises these days? Any common issues that seem to be cropping up in terms of variable typing, number-type (int, long, etc.) rollover problems? We're in a holding pattern right now but we hope to have the new OS running within a week or so....

[Eileen Millen]

You could download the 11i STK (software transition kit) tool which you can run on programs to see if there might be any problems.

Eileen

[A. Clay Stephenson]

Hi Ryan:

Generally if you have written good quality code
(e.g. using the sizeof operator vs hard coded size values, not depending on particular byte offset into structs, ...) then the port will go quite well. You have another choice to make and that is do you want to support 32-bit 11x?

Bear in mind that compiling for the 32-bit environment is not necessarily a bad choice and you will not see a performance hit. In fact, unless you really need resources (lots of memory, large files, big chunks of shared memory) there is no real advantage to 64-bit and you can then support both 32-bit and 64-bit platforms with the same binaries.

If you truly need 64-bit applications, then one thing to pay particular attention to is the +DD32 or +DD64 data model compiler switch. It affects the size of basic data types. e.g. +DD32 sizeof(long) = 4; +DD64 sizeof(long) = 64.

I also suggest that you select your compiler carefully. If you need K & R C then you must use the ACSI/C compiler because aC++ does not speak K & R. ANSI/C does not speak C++. If you need both K & R C and C++, you will need both compilers.

Hope this helps, Clay