Hi Dan,

You wrote on 07.12.03 about "400,000 Americans to pr":

[hack to here]
AS>> The one used by Termail's TMUTIL.EXE is really just for the JAM
AS>> message base maintenance.  But - if memory serves me right -
AS>> your use of OMX won't be using that JAM message-base for access.

DC> OMX translates BW into JAM format.

Ah!  That could be the process that's severing the link/s.

Thereby, possibly, could introduce a problem that you'd maybe not  
be able to do anything about.  That's the BW "bundler" running at  
your uplink's site.  If that's stripping the JAM required MSGID  
linking/threading kludges, any replying you do to a message will  
already be short of a link-kludge.

DC> Anyhow, it is like tossing the mail but not entering TM itself.
DC> That command is TM /toss

DC> And, I tried TM /link

DC> What a mess!  I think a couple of message areas were too large
DC> and it choked.  Not a pretty sight!

Can't now recall if that "TM /link" call directly invokes the  
TMUTIL gubbins.  ASSuming that it does, if you hunt through the  
docs I think you'll find that could be caused by a lack of memory  
available.  How much memory do you reckon to have available ??

TTFN,

Archie

--- CrossPoint/FreeXP v3.40 RC3 R