| Hi Sang,
Re .1,
There are a few problems with V3.2 namely DDS$INQUE.DAT get's corrupted
if you are using DDS. It's recommended that you go to 3.2-1 we are
currently running on our system.
I have put a note in FORTY2::MAILBUS note 1125 a copy is cross posted
here.
Note 1125.0 Mailbus 3.2-1 DDS and ALL-IN-1, DDS$INQUE.DAT problem No
replies
GIDDAY::SETHI "Man from Downunder" 28 lines
13-AUG-1992 05:59
G'day,
We have had a number of problems reported at the CSC concerning DDS
and ALL-IN-1. Typically it's been found that the [MB$.DDS.DB]DDS$INQUE.DAT
has been corrupted. Mailbus Version MBMAN S3.2-1.
The symptoms of the problem have been the process DDS$55_i1 disappears in
some cases. In other cases the four processes DDS$55_i1,DDS$55_lt1,
DDS$55_lt2 and DDS$LSTN_55_1 are still present and are in normal states
ie LEF and HIB for DDS$LSTN_55_1.
However when you try to do a $sys$manager:mb$control stop=DDS, the
process hangs. You have to control_y out of the command procedure
the 4 DDS processes have been stopped.
If you do a $sys$manager:mb$control start=DDS, the process hangs.
In MBMAN doing a create inqueue hangs. At this point we did a
$analyze/rms/fdl/out=dds$inque.fdl dds$inque.dat and renamed the
DDS$INQUE.DAT. Then created a new DDS$INQUE.DAT, this enabled the
create inqueue command to finish successfully.
It appears that we still have problems with DDS$INQUE.DAT. Can
this be confirmed ? Or do any of you have ideas why this problem has
occured under 3.2-1 of Mailbus ?
*********************************************
Also see 1085 I managed to fix a problem at the customers site with
3.2-1. This applies if you are going to use DDS I am not sure about
message router component of Mailbus.
I am just waiting for a confirmation in the mailbus conference if the
problem still exists.
Sunil
|