Re: SYS$SPECIFIC and SYS$COMMON not enough?

From: Hoff Hoffman (hoff_at_hp.nospam)
Date: 07/07/03 

Date: Mon, 07 Jul 2003 18:52:31 GMT

In article <01KXZKP04MZUAM7Y4A@sysdev.deutsche-boerse.com>, Phillip Helbig <HELBPHI@sysdev.deutsche-boerse.com> writes:
:What are some real-world examples of stuff which is common to all nodes
:which boot from a common system disk, but not common to all nodes in a
:cluster, even in a share-as-much-as-possible cluster?

  You need to answer this question yourself, and specifically for
  your local environment. One example would be SYSUAF.DAT quota
  settings for various hosts, if running parallel SYSUAF files.
  (You need to be VERY careful here, as you must keep all UICs and
  all usernames and all identifiers involved scrupulously matched.)

  I am aware of nothing here, however, that can't also be handled
  "directly" with per-file logical name redirections. SYSUAF can
  certainly be redirected, of course.

:Is there any chance of extending definitions like SYS$SYSROOT to include
:SYS$CLUSTER while retaining backward compatibility?

  We have something similar here in OpenVMS Engineering, and we do
  create and use a CLU$COMMON root within SYS$SYSROOT:

$ sho log sys$sysroot
   "SYS$SYSROOT" = "ddcu:[root.]" (LNM$SYSTEM_TABLE)
        = "SYS$COMMON:"
1 "SYS$COMMON" = "ddcu:[root.SYSCOMMON.]" (LNM$SYSTEM_TABLE)
        = "CLU$COMMON:"
2 "CLU$COMMON" = "ddcuother:[root.]" (LNM$SYSTEM_TABLE)

  though we do know that various of the LP installation procedures can
  and regularly do become somewhat confused with this structure. Some
  of the engineers have informally discussed implementing and supporting
  this configuration, and (obviously) fixing and extending the various
  OpenVMS installation procedures and tools -- but another and far larger
  project has, um, intruded on this particular OpenVMS enhancement.

  We walk the current list of SYS$SYSROOT translations within some DCL
  within SYLOGICALS.COM, and we append the CLU$COMMON translation onto
  the searchlist.

 ---------------------------- #include <rtfaq.h> -----------------------------
    For additional, please see the OpenVMS FAQ -- www.hp.com/go/openvms/faq
 --------------------------- pure personal opinion ---------------------------
        Hoff (Stephen) Hoffman OpenVMS Engineering hoff[at]hp.com

Relevant Pages

  • Re: What is the convention for Command Prompt window arguments
    ... using slashes is more common than the one with dashes. ... another universal option is ... I think that there may still be something called OpenVMS around but I know ...
    (microsoft.public.dotnet.languages.vc)
  • Re: What is the convention for Command Prompt window arguments
    ... using slashes is more common than the one with dashes. ... another universal option is ... I think that there may still be something called OpenVMS around but I ...
    (microsoft.public.dotnet.languages.vc)
  • Re: Where Are The System Directories
    ... OpenVMS uses a rooted system disk structure and various searchlist logical names, with a system root containing system-specific files for those systems that boot off the particular system disk and one or more system roots present on most every system disk, and with the common system files stored over in the cluster common root. ...
    (comp.os.vms)
  • Re: OpenVMS Quote of the day
    ... That is quite common ... >VMS Success Stories Monthly Mailing List so he can see exactly what ... Network and OpenVMS system specialist ...
    (comp.os.vms)
  • Re: Permission to translate to Portuguese PCL
    ... CT> Looking at the verso of the title page of my copy of /Practical Common ... CT> "For information on translations, please contact Apress directly at ... Peter Seibel's "Practical Common Lisp" ...
    (comp.lang.lisp)
Quantcast