Relay-Version: version B 2.10 5/3/83; site utzoo.UUCP
Path: utzoo!utgpu!water!watmath!clyde!cbosgd!ucbvax!uwovax.UWO.CDN!PM
From: PM@uwovax.UWO.CDN.UUCP
Newsgroups: comp.os.vms
Subject: Logical Names & CMU-TEK IP print spooler
Message-ID: <0564845875@uwovax.UWO.CDN>
Date: Wed, 25-Nov-87 13:37:55 EST
Article-I.D.: uwovax.0564845875
Posted: Wed Nov 25 13:37:55 1987
Date-Received: Sun, 29-Nov-87 06:28:19 EST
Sender: daemon@ucbvax.BERKELEY.EDU
Distribution: world
Organization: The ARPA Internet
Lines: 30

We are running a VAX cluster.  We run a cluster wide print queue that uses
the CMU-TEK IP package to ship the print files to a Ultrix lpd deamon that
feeds a laser printer.

Normally files put into the queue arrive properly at the other end.
Everything works just fine.  If I try to send a file like
SYS$HELP:FINGER.HELP then the CMU symbiont fails complaining that it
can't find the file.  The file that it is looking for is
_HSC001$DUA0:[SYSCOMMON.SYSHLP]FINGER.HELP and if you try to type that
file, sure enough the directory is bad.  It should be something like
_HSC001$DUA0:[SYS0.SYSCOMMON.SYSHLP]FINGER.HELP (i.e. SYSCOMMON is not
a top level directory).  When I print the same file to the standard
SYS$PRINT queue it "says" that it is printing the file named by the
illegal directory specification (on the header page), but it actually
finds the right file.

This looks like a problem with the expansion of logicals, but what is the
standard print symbiont doing to make it work?  Is this situation just
an artifact of our specific logical name setup on our cluster or is it
a more general problem?

Any help to untangle the logicals web, or to tell me that we are not
alone would be appreciated.  A work around would be great!

---
Peter Marshall, Data Comm. Manager
CCS, U. of Western Ontario,
London, Canada N6A 5B7  (519)661-2151x6032
pm@uwovax.BITNET; pm@uwovax.uwo.cdn; Peter.Marshall@uwo.cdn
peter@julian.uucp; ...!watmath!julian!peter