🚀 go-pugleaf

How can XV v2.11 be tricked to access files on another node?

We have a large collection of GIF files on our DECnet-based network which
we would like to make available to all our other nodes. This works well for
PC's (we use PathWorks V4.1), but NOT for VAXstation's with XV as the viewer.

The problem seems related to the Un*x filename simulation under VMS.
Network access works if we copy the file to a local disk, and then use XV.
However, XV won't allow nodenames as part of the filename in the way that
VMS Utilities do.

I'm using XV V2.11 with VMS patches under VMS V5.4-3 Motif V1.0 with DECnet.

I've defined DEVICE_LIST_ROOT to allow selecting different disks, and this
works well, where each directory name in this directory is the name of
a concealed logical name pointing to another device. 

However, this won't work when the logical name includes a node name.



example:

$ dir shfcsa::*.gif

Directory SHFCSA::USER$ROOT:[KEITH_W]

ALEX.GIF;1          418     JISEL1.GIF;1        303

Total of 2 files, 721 blocks.
$
$ xv shfcsa::*.gif
xv.exe.3: LoadGIF() - Can't map file to memory
xv.exe.3: Couldn't load file 'shfcsa!alex.gif'.
$
$ define/sys/exec/trans=(conc,term) csa_kw shfcsa::shfcsa$dkb200:[user.keith_w]
$ dir csa_kw
%DIRECT-E, error opening CSA_KW as input
-RMS-F, error in device name or inappropriate device type for operation
$


Any suggestions?