On Wed, 28 Aug 2002 09:46:45 GMT Paul Courry said:

> The way I do it is stub out my UDC's with a call to a command
> file. Since all my UDC's point to command files I can update
> the command files at will. (Be sure to put appropriate
> security on them).

Paul,

Perhaps a less costly approach to replace UDCs with command files
would be to create a system wide logon UDC that sets the search
path to include a group that holds the replacement command files.
The group, say cmds.sys only needs execute access for ALL system
users. Alternatively, you may place Access Control Definitions
(ACDs) on each command file you want system wide users to access;
again X access will be sufficient.

Here is what I use:

User-defined command:

START
OPTION LOGON, NOBREAK
# Logon UDC to set my path and environment.
# by Frank Alden Smith
setvar hppath "cmds.sys,"+hppath
setvar tz "EST5EDT"

In this way any UDC -- that is not replacing a native CI command
-- may be removed from the UDC file(s) and replaced by a command
file (AKA CI program) in the cmds.sys group. Once the UDC is
removed, any reference to that command file’s name will be
resolved in cmds.sys. You may also want to create a cmds group
in accounts other than sys to handle account wide UDCs.

Reducing the number of UDCs on your system, can improve system
performance, but more important it will eliminate the (sometimes
painful) effort involved with administering UDCs.

Take care,
frank
======================================================
Frank Alden Smith           HP MPE/iX Certified Professional
Alden Research, Inc.            Instructor -- Consultant
3617 Ligon Road
Ellicott City MD  21042

Phone: (410) 750-2101

"All knowing is doing" -- Humberto Maturana (biologist and teacher)
======================================================

* To join/leave the list, search archives, change list settings, *
* etc., please visit http://raven.utc.edu/archives/hp3000-l.html *