[mod.computers.vax] LINKING ACROSS DECNET

BOSS@TAMVXOCN.BITNET.UUCP (03/03/87)

I am trying to link across the net. The remote node is REMOTE.
I am on HOME.
The following link command works fine.

$link main,REMOTE::sys$sysdevice:[graphicsdir]graphics/lib

However, the next set of commands do not work.

$assign "REMOTE::sys$sysdevice:[graphicsdir]graphics.olb" -
 lnk$library
$link main

I get the following error...
%LINK-F-OPENIN, error opening
 REMOTE::LNK$LIBRARY_1YSDEVICE:[GRAPHICSDIR]GRAPHICS.OLB;1 as input
-RMS-F-DEV, error in device name or inappropriate device type for operation

Any ideas?
It would be nice to link across the net without having to list the libs
in the link command.

Thanks,
Pat Setser   BITNET: BOSS@TAMVXOCN

STEINBERGER@SRI-KL.ARPA.UUCP (03/05/87)

Another work around for linking over DECNET might be to use a symbol,

$ rem :== remote"""access string"""::$devive:[directory.subdir]libr/lib

Then

$link main,'rem'

I haven't tried this explicitly with linking, but it does work with
routine (e.g. COPY) DECNET file access.

Good Luck

-Ric Steinberger
steinberger@kl.sri.com

-------

LEICHTER-JERRY@YALE.ARPA.UUCP (03/05/87)

    I am trying to link across the net. The remote node is REMOTE.
    I am on HOME.  The following link command works fine.

    $ link main,REMOTE::sys$sysdevice:[graphicsdir]graphics/lib

    However, the next set of commands do not work.

    $ assign "REMOTE::sys$sysdevice:[graphicsdir]graphics.olb" -
     lnk$library
    $ link main

    I get the following error...

    %LINK-F-OPENIN, error opening
     REMOTE::LNK$LIBRARY_1YSDEVICE:[GRAPHICSDIR]GRAPHICS.OLB;1 as input
    -RMS-F-DEV, error in device name or inappropriate device type for operation

I've seen reference to this problem before.  The Linker, for obvious reasons,
was one of the earliest pieces of VMS written.  Some of the code is apparently
pretty flakey; dealing with logicals for LNK$LIBRARY etc., is in this class.
Apparently, it's SO flakey that no one really wants to touch it.

You should SPR this; it might help raise the visibility of the problem to the
point that someone finally is forced to endure the pain and deal with it.

I'm afraid I know of no work-arounds other than the obvious one of including
the library explicitly, which as you've seen DOES work.
							-- Jerry
-------