| T.R | Title | User | Personal
Name | Date | Lines |
|---|
| 193.1 | Gotcha | BACK::HAYCOX | Jaguar Le Mans winners 1988 | Mon Nov 14 1988 16:44 | 16 |
| Jerry,
Can we please have PASSTR V3.8 instead of V3.4 as this provides ALL
the Pascal environment files for lib$,str$,sor$ etc as separate files,
as well as an updated starlet.pas.
Note as well that CMS V2 libraries need to be converted. This can take
several hours and screws up ACL's/Security if your not careful. Release
notes available on BACK::SYS$HELP:CMS%%%.RELEASE_NOTES if interested.
Ian.
Ps, I think only Nmail V9.0 works on V5
Pps, DON'T run dopter on V5, it took me forever to recover from a
corrupted system disk.
|
| 193.2 | First draft? | NECK::THOMPSON | | Mon Nov 14 1988 17:29 | 4 |
| Thanks Ian. The list is still provisional so I expect there will be
some changes in the final version. Watch this space for the latest
updates!
|
| 193.3 | Possible problem with DBMS V4.0 and VMS V5.0-2 | THROAT::CLARK | ASC, a mad Scot | Tue Nov 15 1988 09:40 | 41 |
| Attatched to this reply is a note from the DBMS notes conference
which suggests some problems with going straight to DBMS V4.0 on
VMS V5.0-2. I have looked further into this problem and it seems
that it only occurs on the restore of a very large database on a
busy system.
You - the system manglement team - may want to check out the relevant
notes yourself to assess the risks, or otherwise, of going straight
to V4.0 of DBMS on V5.0-2 of VMS. From past experience, I am sure
a patch will be ready VERY soon.
Stewart
<<< NOVA::$111$DUA0:[NOTES$LIBRARY]DBMS.NOTE;1 >>>
-< VAX DBMS >-
================================================================================
Note 781.8 large database corrupts on v4.0 8 of 8
CANYON::ADKINS "Insert Relevant Phrase Here" 19 lines 13-NOV-1988 17:10
-< CSC Patch for VMS 5.0-1 and later bombs on 5.0-2 >-
--------------------------------------------------------------------------------
DANGER!!! WARNING!!!! Will Robinson.
The patch for DBMS V4.0 for VMS 5.0-1 and later does not work on
VMS 5.0-2. It seems when DBO is built under 5.0-2, the locations
needing patched change addresses. (DBO is linked during the install, so
the use of VMSINSTAL to install the product under VMS 5.0-2 will
cause this problem.)
I've got a call in to have a new patch cut for 5.0-2.
IF YOU ARE UPGRADING VMS FROM 4.X to 5.0-2, save yourself some
heartache and install DBMS at 5.0-1 and patch it *before* going
on to 5.0-2. (This restriction will change after the new patch
is released).
Jim
(Who has a less than happy customer at the moment and who had a
less than pleasant Saturday :-( )
|
| 193.4 | No ALL-IN-1 for VMS V5.0 yet | NECK::THOMPSON | | Wed Nov 16 1988 11:08 | 179 |
| Attached is a note outlining restrictions to ALL-IN-1 on VMS V5.0
As a result of these restrictions there will be no ALL-IN-1 software
running on FUTURS until V2.3 of ALL-IN-1 and/or its equivalent BEV
clone are available.
<<< SAC::SYS$SYSDEVICE:[NOTES$LIBRARY]UKV5.NOTE;1 >>>
-< VMS V5.0 in the U.K. >-
================================================================================
Note 45.0 ALL-IN-1 Support for VMS V5.0 1 reply
SAC::WALL "Disk space... the final frontier." 166 lines 25-APR-1988 10:25
--------------------------------------------------------------------------------
C O U N T R Y S U P P O R T
S U P P O R T F L A S H NO. 16
------------------------------------------------------
ALL-IN-1 V2.2 AND VMS V5.0
------------------------------------------------------
From: Jill K Smith (COMICS::JSMITH, DTN: 7833 3578)
Product Focus Engineer (Office Products)
Country Support
Basingstoke
IMPORTANT
It is possible to run ALL-IN-1 V2.2 on VMS V5.0 but there are RESTRICTIONS
(documented in this Support Flash). HOWEVER, customers should be encouraged
to upgrade to ALL-IN-1 V2.3 BEFORE upgrading to VMS V5.0 (PLEASE BE AWARE
THAT ALL-IN-1 V2.3 HAS NOT BEEN PUBLICLY ANNOUNCED).
Currently the ALL-IN-1 V2.2 kit contains Message Router VMSmail Gateway Kit
V2.1. Message Router V2.1 is not supported on VMS V5.0. The ALL-IN-1 V2.3
kit will contain an appropriate version of Message Router to run on VMS
V5.0.
There are no plans to update the Message Router kits that have been
purchased as part of an ALL-IN-1 kit. Therefore, if a customer insists that
he cannot perform the upgrade to VMS V5.0 in the recommended order it will
be necessary for the appropriate District to raise an exception order on
his behalf to obtain Message Router V3.0 so that ALL-IN-1 V2.2 can be
installed on VMS V5.0.
There follows a statement issued by European Marketing about the status of
ALL-IN-1 V2.2, Message Router and VMS V5.0 and the restrictions involved:
"With the introduction of VMS V5.0 it is necessary to use Message
Router VMSmail Gateway Kit Version 3.0 since MR V2.1 is not
supported. When you run ALL-IN-1 Version 2.2 with Message Router
VMSmail Gateway Kit Version 3.0 and VMS Version 5.0, the following
restrictions apply:
************
It is recommended that if you are running ALL-IN-1 and wish to use
VMS V5.0 then you wait until the next version of ALL-IN-1 is
available and install that at the same time. The next version of
ALL-IN-1 will contain Message Router V3.0.
If you do not wish to upgrade to ALL-IN-1 V2.3, but do wish to
install VMS V5.0, then MR V3.0 is required and must be purchased
and installed before upgrading to VMS V5.0. The following restriction
applies which will be fixed in the next version of ALL-IN-1:-
o Electronic Messaging
If you try to bring your unread VMSmail into ALL-IN-1 Electronic
Messaging by using the VMSmail Import option, an access violation
will occur.
If you want to read your VMSmail from your ALL-IN-1 account, make
sure Message Router V3.0 is installed and then set Autoforward on
your VMSmail account. VMSmail will then automatically be imported
without causing problems.
o Running the MAIL image
The Message Router VMS Gateway (MRGATE) needs the MAIL image to
run with SYSPRV. Unlike VMS Version 4.*, VMS Version 5.0 does not
install the MAIL image with SYSPRV. Therefore, if you are running
MRGATE on VMS Version 5.0, log in to the SYSTEM account and use
the following command to assign SYSPRV to the MAIL image:
$ INSTALL REPLACE MAIL /PRIV=SYSPRV
o Using the SUBMIT command
The SUBMIT command works differently in VMS Version 5.0 from how
it works in VMS Version 4.*. In Version 4.*, any logical names
specified in the /LOG quali- fier are translated at submission
time. In Version 5.0, the logical names are translated when the
job starts, at which point the logical names may not have been
defined.
If you are using exception reporting in Message Router Version
3.0, the change to the SUBMIT command in VMS Version 5.0 can cause
the exception reporting batch submission to fail. The batch jobs
are entered on the batch queue, but the jobs fail and do not leave
a log file indicating the reason for failure, because no logical
name is defined for the log file.
To avoid this happening, edit the command procedure which starts
up the exception reporting batch jobs
(SYS$COMMON:[SYSMGR]MB$$ER_START.COM) as follows:
1. Change the /LOG qualifier of the SUBMIT command
from
/LOG=MB$SCRATCH:MB$'component'_'node'.LOG -
to
/LOG=MB$ROOT:[MB$SCRATCH]MB$'component'_'node'.LOG -
2. Change the /LOG qualifier of the SUBMIT command
from
/LOG=MB$SCRATCH:MB$NET_''mb$$mgmnt_node'.LOG -
to
/LOG=MB$ROOT:[MB$SCRATCH]MB$NET_'mb$$mgmnt_node'.LOG -
o Message Router Directory Service
If you are running the Directory Service part of Message Router
Version 3.0 on VMS Version 5.0, you may see the following error
messages:
DDS-E-OPSYS, Operating system interface error
LIB-E-BADBLOADR, bad block address
These messages indicate that part of the Virtual Memory is not
being released. You will see these error messages when new nodes
join the Directory Service network and when the Directory Service
servers are running (for example, when you use the MBMAN SUSPEND
command). These are erroneous messages, the Directory Service
carries on working.
o Defining Batch Queues
As stated in the Message Router Version 3.0 Release Notes, the
verification procedures need DECnet and the Queue Manager to be
started on the system. However, the verification procedures also
need at least one queue to be defined in the system startup
procedure.
If you do not have a queue defined in the system startup
procedure, use the DCL command, INITIALIZE /QUEUE /BATCH, to
define a queue in the system startup procedure. Refer to the
VAX/VMS DCL Dictionary for details of this command.
************
|
| 193.5 | Postponement of V5 Upgrade | ELBOW::DRAPER | Steve Draper | Wed Nov 23 1988 05:53 | 6 |
| In order to avoid impacting the additional work required on the Beta software,
the VMS V5 upgrade scheduled for the FUTURS cluster has been temporarily
postponed.
A further announcement giving revised dates for the upgrade will be made later
after the impact of BETA on this has been evaluated.
|
| 193.6 | | FOOT::WRIGHT | I AM a member of this company | Thu Nov 24 1988 11:03 | 5 |
| Steve,
Does this mean that applications will NOT be moving from FUTURS
to ADG over the weekend?
Tony
|
| 193.7 | Something dosen't ring true | BIGHUN::HARVEY | The Devon Dumpling | Tue Nov 29 1988 13:49 | 9 |
| > Attached is a note outlining restrictions to ALL-IN-1 on VMS V5.0
> As a result of these restrictions there will be no ALL-IN-1 software
> running on FUTURS until V2.3 of ALL-IN-1 and/or its equivalent BEV
> clone are available.
So how do you plan to support countries that conform to the European
Published recommended list published in .0?
Heather
|
| 193.8 | some info | BIGHUN::HARVEY | The Devon Dumpling | Tue Nov 29 1988 17:55 | 13 |
| The warnings were given for ALL-IN-1, with VMS V5.0-0 and Message
router V3.0
One of the supported confugurations for ALL-IN-1, Message router, and
VMS is:
VMS V5.0-2 ALL-IN-1 V2.2 MR 3.1
(MR 3.0 is NOT supported with V5.0-2 using any version of ALL-IN-1)
Hope this helps,
Heather
|
| 193.9 | FUTURS VMS V5.0 Plan B | NECK::THOMPSON | | Wed Jan 11 1989 16:31 | 24 |
| And here is the next plan for upgrading FUTURS to V5:
Fri 13th Jan - Futurs system disk copied to CUCKOO ,and CUCKOO isolated
from ethernet
Mon 16th to
Thurs 19th Jan - CUCKOO used to produce an upgraded system disk copy.
NO CHANGES permitted to FUTURS system disk.
All users off FUTURS by 5:30pm Thurs 19th.
CUCKOO's upgraded copy loaded back onto FUTURS on
Thursday evening and tested.
Fri 20th Jan - Futurs not available until 11am while remaining
V5 upgrade procedures are completed and system tests
are finished
The upgrade can be done in this way to maximise the uptime of FUTURS
during normal working hours. But because the upgrade would not be
done strictly by the book and because this is the first cluster to go
to V5 there is a risk that the cluster may not be available by 11am Friday.
The alternative is to postpone all tasks by one week and complete the
upgrade during the weekend of 28/29th Jan. This would leave even
less time for projects to be developed and tested under v5.0 ready for
the EASE migration in April.
|
| 193.10 | Surely Rdb V3.0 | YARD::SIMS | Adrian - UK ADG 781-4315 | Thu Jan 12 1989 17:26 | 6 |
| Steve,
Rdb V2.3 will not run on VMS 5.0 - you will require Rdb V3.0.
I also believe that CDD+ is also required for Rdb V3.0.
Ady
|
| 193.11 | ALL-IN-1? | GROYNE::HAYES | Ian Hayes, DTN 781 ext 4327 | Fri Jan 13 1989 15:22 | 5 |
| Also, which verison of ALL-IN-1 will be loaded - 2.1BEV I hope (at
least initially)
Ian
|
| 193.12 | Wait a while ... | INCH::BADMAN | Food is for Wimps | Mon Jan 30 1989 15:00 | 10 |
| RE .11
Ian,
.4 says that ALL-IN-1 will not be loaded onto Futurs until 2.3BEV
Jamie.
|
| 193.13 | Install RDB V3.0a | INCH::BADMAN | Food is for Wimps | Mon Jan 30 1989 15:04 | 11 |
| Also, RE .10,
RDB V3 should be installed on V5, but the kit used should be V3.0a
which should be released in the first week or so of February. It
contains the infamous 8 patches to the original 3.0 kit plus 20-30
additional bug fixes. It looks like it would be a good idea to ensure
that this is the version installed!
Jamie.
|
| 193.14 | $ Allin1/Version=Random | NECK::THOMPSON | | Wed Feb 01 1989 14:01 | 13 |
| re .11
Well according to the list of layered products for EASE V5.0 you can
have All-in-1 BEV 2.1
or
All-in-1 2.2
or
All-in-1 (�Vax?) 2.3
But which Message Router version can we use, V3.1? Anyone out there got
any inside information about which combination is needed?
|
| 193.15 | Perm and 3 from 10? | BIGHUN::HARVEY | The Devon Dumpling | Wed Feb 01 1989 16:24 | 12 |
| > But which Message Router version can we use, V3.1? Anyone out there got
> any inside information about which combination is needed?
MSG Router V3.1 is the version stated on the V5 upgrade list that we get
from Geneva(Jim Kirk), and will be the version that all the countries run.
There is a lot of info in the ALL-IN-1 notes conference about
restrictions on versions....
Heather
|
| 193.16 | ALL-IN-1 | GROYNE::HAYES | Ian Hayes, DTN 781 ext 4327 | Fri Feb 03 1989 12:54 | 6 |
| Well, we need ALL-IN-1 BEV V2.1 initially to do our migration testing
for MRE. Following that we will need a VMS V5 system with ALL-IN-1
2.3 to do new development (from the end of February).
We don't need message router at all.
Ian.
|