$ unzip :==
$$2$dka500:[bin]unzip.exe
$ xfig == "@$2$DKA500:[BIN.XFIG32]XFIG.COM"
$ mxrn :== $$2$dka500:[bin]mxrn
Actually, you might want to do a HELP DEFINE and learn how to set
up logicals. Hard-coded device names scattered throughout a bunch of
command files are a pain in the rear when you later move stuff between
disks or consolidate disks. Wouldn't you rather say DISK$BIN: than
$$2$dka500: ?
On a small system the advantage may not be so obvious, but when you've
got a medium-sized VMScluster (a couple dozen CPU's, a few hundred disks),
especially with a mix of Alpha and VAX CPU's, it really pays off.
I totally agree. Of course I didn't realize that until last night after
writing that :^) Right now I'm just a small cluster, and primarily Alpha.
However, I'm getting ready to add a couple more VAXen (currenlty only a MV3
is in the mix and it's only used for one small task), and I happened to
think, the above just won't work with mixed architectures.
Off the top of my head I believe you're talking about doing the following
in
SYLOGICALS.COM
DEFINE/SYSTEM DISK$BIN $2$DKA500:[bin.]
Of course then I'll need to move any programs in [bin] to a subdirectory.
Guess I should spend more time reading the User and Clustering manuals,
this is obviously messed up. It looks like [bin] should actually be
[alpha] and [vax] with a [.bin] under that. That way I can have the system
set DISK$BIN, and everything be transparent to the
LOGIN.COM.
Oh, well, guess I didn't have anything better to do this morning...
Zane
| Zane H. Healy | UNIX Systems Adminstrator |
| healyzh(a)aracnet.com (primary) | Linux Enthusiast |
| healyzh(a)holonet.net (alternate) | Classic Computer Collector |
+----------------------------------+----------------------------+
| Empire of the Petal Throne and Traveller Role Playing, |
| and Zane's Computer Museum. |
|
http://www.aracnet.com/~healyzh/ |
