OVMS 8.2-1: Linking on NFS filesystem causes errors

[Eberhard Wacker]

Too early answered, quote from Volker:
NFS client in TCPIP V5.5 on OpenVMS I64 should be o.k.
I don't know, this was not told to me when I've opened a HP call some times ago.
Again cheers,
EW

[Volker Halle]

Thomas,

as with most communication-related problems it's hard to tell, who's right or wrong. Testing from an OpenVMS Alpha NFS client also does not provide any help, as the I64 linker is a different piece of software compared to the Alpha linker and may use different means of opening/mapping/closing the .OBJ file.

From the %ILINK-W-CLOSEIN message point of view, it's a warning message only. The underlying system service did exit with a fatal error. But the .EXE file should work o.k. - does it ?

Eberhard,

the TCPIP V5.5 release notes state in chapter 3.2:

NFS Server Does Not Run on I64 Platforms

There are no limitations mentioned for NFS client on I64.

Volker.

[Thomas Ries]

Now I also tried the following combinations:
Server: AXP OVMS 8.2 TCPIP 5.5 ECO1
Client: I64 OVMS 8.2-1 TCPIP 5.5 ECO1
and
Server: AXP OVMS 7.3-2 TCPIP 5.4 ECO2
Client: AXP OVMS 8.2 TCPIP 5.5 ECO1

As expected, with I64 as a CLIENT, the effect pops up. With AXP as client, everything works fine.

Side note:
The CXX compiling issue ("can not create tmp file") seems to be related to C++ files using templates like:
CMatrixMap mg_matrixmap;
and having SYS$SCRATCH pointing to a location that is in the NFS device. Also the specified include paths (/INCLUDE=...) seem to matter in some way.

We're going to open a call at HP and see what results we get.
I'll update this thread when we get feedback from HP.

Thanks,
/Thomas

[Thomas Ries]

Ok, we got some feedback from HP:

- This effect is "internally known" by HP, though no customer has complained before. With OVMS 8.3 (TCPIP V5.6) this issue *should* be fixed.

- The ECO2 for TCPIP V5.5 *might* include this fix.


Thanks to anyone helping.

Regards,
/Thomas