JM>> -> Nothing that can't be overcome.
JM>>
JM>> Certainly, devise us a spec then.  ...  Or see below.
JM>>
JM>> -> More than one machine is in use, creating messages at the
JM>> same time w
JM>> -> same node number?  A MSGID is considered unique as long as
JM>> the serial
JM>> -> and the system ID string together are unique.
JM>>
JM>> Oooh, you missed that one David.  This whole thread is based
JM>> upon using
JM>> the same  address.  Only the serial number
JM>> is
JM>> different.
JM>>

 RH> This is the error.  If you have two (or more) machines, you need
 RH> two (or more addresses).

no you don't... you only need to build into your serial number generation
routine a method of including a "node" number... in this case,
"node" = "task" on a single machine running more than
one task...

on one setup i have, there are 10 nodes... 4 on one machine, 4 on a second
machine and the last two on one machine each... that's 4 machines for one
FTN address that consists of 10 tasks/nodes... in the serial numbers i
generate, digits 0, 1 and 2 are related to the date, digits 3, 4 and 5 are
the synchronous counter in hex and digits 6 and 7 are the node/task number
in hex...

ie:
            01234567
            dddccctt   d = date part  c = sync counter  t = task
1:3634/12.0 79c00008        first message written by node/task 8
1:3634/12.0 79c00004        first message written by node/task 4
1:3634/12.0 79c00108       second message written by node/task 8
1:3634/12.0 79c00104       second message written by node/task 4
1:3634/12.0 79c00208        third message written by node/task 8
1:3634/12.0 79c00204        third message written by node/task 4
1:3634/12.0 79c00308       fourth message written by node/task 8
1:3634/12.0 79c00304       fourth message written by node/task 4
1:3634/12.0 79c00408        fifth message written by node/task 8
1:3634/12.0 79c00404        fifth message written by node/task 4
1:3634/12.0 79c00508        sixth message written by node/task 8
1:3634/12.0 79c00504        sixth message written by node/task 4
1:3634/12.0 79c00608      seventh message written by node/task 8
1:3634/12.0 79c00604      seventh message written by node/task 4
1:3634/12.0 79c00708       eighth message written by node/task 8
1:3634/12.0 79c00704       eighth message written by node/task 4

  00 -  ff for the tt portion          =  256 total t's possible
 000 - fff for the ccc portion         = 4096 c's per t per day
 ===============================================================
                                      1048576 total id's per day
                                               using this method

that's only 12 messages per second per day... -=B-)

)\/(ark