Article 152738 of comp.os.vms: In article <1996Aug9.152930.1@sldb4.slac.stanford.edu>, wrote: >In article <1996Aug9.164633.11117@hpal01.isd4.tafensw.edu.au>, > cpasfield@newsmail.tafensw.edu.au writes: > >> I have a mixed architecture cluster and need to define a common >> NETOBJECT.DAT file. How do I do this? >> >> I've been unable to locate doco describing a NETOBJECT logical >> which will do this. I believe this should work in a similar manner >> to my common NET$PROXY and NETPROXY files. Is this correct? > > Yes, correct. We define all of NETNODE_REMOTE, NETOBJECT, > NETPROXY and NET$PROXY to be the associated, fully-qualified file > specification on the target disk. Since we're new to Alphas, I > simply point these logicals to the associated files in SYS$COMMON on > the VAX system disk (and I mount the VAX system disk early in the > boot, I chose SYLOGICALS, on the Alpha). Additionally, I define > LMF$LICENSE, SYSUAF, RIGHTSLIST, QMAN$MASTER, and VMSMAIL_PROFILE in > the same way. > > As far as documentation goes, there is an article on DSNlink > that discusses mixed architecture clusters and which files can be > shared. I'm not sure it's exhaustive, but I believe it contained > some additional logicals than those above. Unfortunately, I can't > lay my hands on the thing at the moment. :-( > > Other references? Anyone? Anyone? :-) Look at sections 5.5 (Providing VMScluster System security) though section 5.8 (Coordinating System Files) in the VMScluster Systems for OpenVMS manual. It includes the files that should be shared among the cluster to establish a single security domain (which includes authorization, queue and network files). I also share TCP/IP (UCX) files. Here is part of my sylogicals.com file (the end bits of some of the file names are clipped, but you get the idea): $ IF F$TRNLNM("SYSUAF") .EQS. "" THEN - DEFINE/SYSTEM/EXEC SYSUAF VAX_SYSTEM:[VMS$COMMON.SYSEXE]SYSUAF $ DEFINE/SYSTEM/EXEC NETPROXY VAX_SYSTEM:[VMS$COMMON.SYSEXE]NETPROXY $ DEFINE/SYSTEM/EXEC NET$PROXY VAX_SYSTEM:[VMS$COMMON.SYSEXE]NET$PROXY $ DEFINE/SYSTEM/EXEC NETOBJECT VAX_SYSTEM:[VMS$COMMON.SYSEXE]NETOBJECT $ DEFINE/SYSTEM/EXEC NETLOGING VAX_SYSTEM:[VMS$COMMON.SYSEXE]NETLOGING $ DEFINE/SYSTEM/EXEC NETNODE_REMOTE VAX_SYSTEM:[VMS$COMMON.SYSEXE]NETNODE_RE $ DEFINE/SYSTEM/EXEC VMSMAIL_PROFILE VAX_SYSTEM:[VMS$COMMON.SYSEXE]VMSMAIL_PR $ DEFINE/SYSTEM/EXEC RIGHTSLIST VAX_SYSTEM:[VMS$COMMON.SYSEXE]RIGHTSLIST $ DEFINE/SYSTEM/EXEC QMAN$MASTER VAX_SYSTEM:[VMS$COMMON.SYSEXE]QMAN$MASTE $ DEFINE/SYSTEM/EXEC VMS$PASSWORD_HISTORY - VAX_SYSTEM:[VMS$COMMON.SYSEXE]VMS$PASSWORD_HISTORY $ $! UCX logicals $ DEFINE/SYSTEM/EXEC UCX$HOST VAX_SYSTEM:[VMS$COMMON.SYSEXE]UCX$HOST.D $ DEFINE/SYSTEM/EXEC UCX$NETWORK VAX_SYSTEM:[VMS$COMMON.SYSEXE]UCX$NETWOR $ DEFINE/SYSTEM/EXEC UCX$PROXY VAX_SYSTEM:[VMS$COMMON.SYSEXE]UCX$PROXY. $ DEFINE/SYSTEM/EXEC UCX$SERVICE VAX_SYSTEM:[VMS$COMMON.SYSEXE]UCX$SERVIC $ -- Vance Haemmerle vance@alumni.caltech.edu my VAXbar page: http://condor.lpl.arizona.edu/~vance/vaxbar.html