Still in trouble for migration ....

[Nicolas Dumeige]

Hello,

As described here : http://forums1.itrc.hp.com/service/forums/questionanswer.do?threadId=958308

All this concerns VMS 6 and Oracle Pro*C.

In the production environnement runs an executable (size 1397). We also have the OBJ.

We also have in Dev. :
an OBJ (size 198) ; a source file.
In Dev. if we build the OBJ, we get a file with size of 201 (that is diffent from the OBJ from Prod). Build the EXE, we get a 408 block file (588 with debug option), again different from the size of the EXE in prod.

1)The compiling / linking process "seems" to be equivalent on both machine (same command file), how can we identificate the differences (includes file, library, ...)


2) Do you know an equivalent to the Unix commands [file] [ldd] ?

# file /bin/ls
/bin/ls: ELF 32-bit MSB executable SPARC Version 1, dynamically linked, stripped

# ldd /bin/ls
libc.so.1 => /usr/lib/libc.so.1
libdl.so.1 => /usr/lib/libdl.so.1
/usr/platform/SUNW,Sun-Fire-15000/lib/libc_psr.so.1



3) Do you have any feedback on vmware on Windows as a way of avoiding a migration ?

Thanks in advance, regards,

Nicolas

[Uwe Zessin · Accepted solution]

VMware encapsulates the whole virtual machine into a set of files and provides a consistent hardware environment which is decoupled from the host's hardware. Those files can be transfered between different hosts (x86-based, of course).

Hey, with a little more money you can even do a life 'migration' - move a running virtual machine from one server to another with very little interruption, but I guess that is not what you meant by migration ;-)

[Ian Miller.]

have you compared the results of
$ ANAL/OBJ
on the two object files?

[Phil.Howell]

All this concerns VMS 6 and Oracle Pro*C.

In the production environnement runs an executable (size 1397). We also have the OBJ.

We also have in Dev. :
an OBJ (size 198) ; a source file.
In Dev. if we build the OBJ, we get a file with size of 201 (that is diffent from the OBJ from Prod). Build the EXE, we get a 408 block file (588 with debug option), again different from the size of the EXE in prod.

1)The compiling / linking process "seems" to be equivalent on both machine (same command file), how can we identificate the differences (includes file, library, ...)

The compiler may give you more information with the /SHOW qualifier.
If you include a /MAP=/FULL in your link statement, it tells you what modules are in the executable, when they were compiled, and the compiler version.

2) Do you know an equivalent to the Unix commands [file] [ldd] ?

ANALYZE/IMAGE or ANALYZE/OBJECT ?

3) Do you have any feedback on vmware on Windows as a way of avoiding a migration ?

When you are in a hole, stop digging.

Phil