DCL$PATH (was Re: Error message help needed)

From: Paddy O'Brien (paddy.o'brien_at_tg.nsw.gov.au)
Date: 05/18/03 

Date: Mon, 19 May 2003 06:46:42 +1000

David J. Dachtera wrote:
> The logical name DCL$PATH (which is optional - it can be setup at the
> system-wide level (NEVER recommended, IMO), group (less of a bugaboo,
> but still only recommended with great caution), job (a little better),
> process (probably most common usage), etc. level.

Why do you suggest that system level should NEVER be recommended? What
problems or risks can this create?

I ask because this is the way I have been running since DCL$PATH came out.

Our production users mainly run our applications and utilities we
provide (e.g., ZIP, SWING, GV to name a few) and utilities that we have
written. They might write a few programs themselves, but not enough to
use DCL$PATH themselves (even if they knew about it).

Our applications are not in the path as we need flexiblity in being able
to get users to test different versions other than the current standard
production version.

All the utilities are in two directories, one for .EXEs and one for
.COMs and this is the access order in DCL$PATH. And yes I do have a
$.COM in the first directory. I learnt of this here some while ago, and
IIRC it was a post from you.

All this avoids setting up numerous symbols in SYLOGIN and also avoids
giving them to accounts where they may never be used.

This entire directory structure is identical on our development and our
production machines.

Regards, Paddy

***********************************************************************

"This electronic message and any attachments may contain privileged
and confidential information intended only for the use of the
addressees named above. If you are not the intended recipient of
this email, please delete the message and any attachment and advise
the sender. You are hereby notified that any use, dissemination,
distribution, reproduction of this email is prohibited.

If you have received the email in error, please notify TransGrid
immediately. Any views expressed in this email are those of the
individual sender except where the sender expressly and with
authority states them to be the views of TransGrid. TransGrid uses
virus scanning software but excludes any liability for viruses
contained in any attachment.

Please note the email address for TransGrid personnel is now
firstname.lastname@transgrid.com.au"

***********************************************************************

Relevant Pages

  • RE: null terminated strings
    ... can then use pointers to access individual elements within that buffer. ... "This electronic message and any attachments may contain privileged ... If you have received the email in error, please notify TransGrid ... individual sender except where the sender expressly and with ...
    (comp.os.vms)
  • Re: OT: Battersea Power Station
    ... no kids -- but then I've ... "This electronic message and any attachments may contain privileged ... If you have received the email in error, please notify TransGrid ... individual sender except where the sender expressly and with ...
    (comp.os.vms)
  • [Fwd: OT: HP and US dollar]
    ... If they understood economics and marketing, ... "This electronic message and any attachments may contain privileged ... If you have received the email in error, please notify TransGrid ... individual sender except where the sender expressly and with ...
    (comp.os.vms)
  • Re: Extending DCL [was: Re: DCL suggestion for f$verify()]
    ... Regards, Paddy ... "This electronic message and any attachments may contain privileged ... If you have received the email in error, please notify TransGrid ... individual sender except where the sender expressly and with ...
    (comp.os.vms)
  • Re: IBM smells the coffee - HP refuses to market profitable VMS
    ... Regards, Paddy ... "This electronic message and any attachments may contain privileged ... If you have received the email in error, please notify TransGrid ... individual sender except where the sender expressly and with ...
    (comp.os.vms)