MOORE@UTHSCSA.BITNET (01/21/87)
I have a situation that requires some policies to be made. What I am
asking for is experiences in similar situations or just an opinion.
We are currently involved in a slow migration from DEC-20s to VAXes. On the
DEC-20s, the system looks for executables in a directory called SUBSYS which is
pointed to by a system-wide logical named SYS:. Logicals can be set up as
search lists, and can be redefined by individual users. If a new version of a
piece of software arrives it would be placed in a directory and pointed to with
a system-wide logical name of NEW:. The old version would remain in a directory
pointed to by SYS:. Software developers could then write new applications using
the new version (by defining SYS: as NEW:,SYS:) and convert older applications
at their convenience. Eventually the old version would be moved into a
directory pointed to by a logical name of OLD:. The new version would be moved
into SYS:. All the while the old version would still available and systems
that depend on it would still function.
Management wants the same functionality on the VAXes. We have four clustered
VAXes running version 4.5 of VMS with a common system disk.
1. What do you think?
2. What are your policies?
3. Suggestions of how to implement?
4. Reasons why we shouldn't implement?
Any response to this message will be appreciated. I can summarize and post
to the list, or if you wish you can send responses to the list.
Mark Moore
The University of Texas
Health Science Center
San Antonio, Texas
MOORE@UTHSCSA.BITNET