T.R | Title | User | Personal Name | Date | Lines |
---|
2854.1 | Check the logicals | FORTY2::ASH | Grahame Ash @REO | Mon Jun 14 1993 11:00 | 15 |
| Hi Chaim,
You say that the fetcher logfile shows there were no mesages to fetch - is
this the initial check before running ALL-IN-1 which fails, or ALL-IN-1 MAIL
MTI_FETCH_REMOTE?
First thing I'd check is that all nodes of the cluster are being set up the
same - specifically that the OA$MTI_* logicals are correct. It sounds as if
the fetcher may be occasionally running on a node which doesn't know where the
mailbox is.
OA$MTI_ERR will only report errors after ALL-IN-1 has started its MAIL
activities - hence the first question above.
grahame
|
2854.2 | Try this.. | FLEX7::ALLINGHAM_PD | Permenantly Peaking! | Mon Jun 14 1993 13:45 | 13 |
| I have had this problem recently - it seems that the fetcher only takes
those messages out of Mrouter that were in Mrouter when the
MTI_FETCH_REMOTE function is issued. As our system is getting mail in
all the time this meant that second class mail at the bottom of the
Mrouter queue wasn't getting into ALL-IN-1 until the end of each day.
I fixed it by adding another MTI_FETCH_REMOTE command after the first
one and by decreasing the execute window to 15 mins rather than 30.
Seems eccentric, I know, and maybe my diagnosis was wrong but it works!
Regards,
Peter.
|
2854.3 | This was deliberate, tho' Heaven knows why! | IOSG::SHOVE | Dave Shove -- REO2-G/M6 | Mon Jun 14 1993 19:21 | 10 |
| You could modify the OaMtiMail.Com file to loop back to where it asks
Message Router whether there's any mail to fetch. That way, it would
stay running until it had cleared out the mailbox.
I've always thought it a bit daft that the fetcher only fetches the
number of messages that were in the mailbox when it starts (the code
asks MR how many there are, then loops this number of times and exits).
A PFR's fetcher will loop until MR says there are no more to fetch.
Dave.
|