Hi David,

 MR> eight simultaneous transfers (using the threading support 
 MR> of OREXX).

PK>This sentence caught my eye, I have not dabbled in OREXX too much
PK>(actually I have tried to avoid anything to do with OBJECTS until I 
PK>absolutely HAVE to......;-)),

 DN> If you want to use native multi-threading in OREXX you HAVE to.

I feared as much, but then sometimes you need a good push to get moving
again......;-)

PK>but can you please elaborate 
PK>on how OREXX implements Multi-threading? Is each thread 
PK>under explicit coder control (IE can a control thread 
PK>stop/start other threads?), or is it "dynamic" threading 
PK>within OREXX that does not allow explicit thread control? 

 DN> It is quite simple really. An object class can have one 
 DN> or more methods that run in secondary threads. These are 
 DN> identified by the REPLY statement.

  ......

Thanks for the details, I have filed this with Mikes reply for reference when
I investigate this further.

The actual mention of Threads in Mikes original message just happened to
arrive a couple of hours before I was about to post a message regarding
process control with REXX. 

In one of my projects I am experiencing a situation with multiple independant
REXX tasks that I wish to terminate by external command if a task reaches a
"no progress" stage. Unfortuantely at the determination of this situation
(generally time based), control is with an external executable that is invoked 
from my REXX code, and I was trying to find a TIDY way to issue a "KILL
PID=nnnn" to terminate that task.

Based on Mike initial message I was considering if the REXX Thread
implementation might provide a "better" way to handle this...

More investigation is needed...

Regards..........pk.


--- Maximus/2 3.01
30