Friday March 17 1995, Jerry McBride writes to Mike Stella:

 JM>> Errr... No. You still have it wrong... The software package
 JM>> that we were discussing was RXASYNC. This is an "add-on"
 JM>> library of serial functions for os/2's built-in rexx
 JM>> langage. RXASYNC, expects the user to use the old-fashioned
 JM>> dos COMPORT number, instead of the os2 comhandle number...
 JM>> This is what I was speaking of.

 MS>> (sigh)  I ought to pay more attention.  So you have a
 MS>> program that passes the com handle, and you really want the
 MS>> com port.  Hardcode it?

 JM> I could, but I really want to use the comhandle... :')

 JM> Mike, let's give this a rest. Either I'm too vague explaining what I want
 JM> or... I dunno'...

:-)

I've just had a little play with RXASYNC and managed to run the following
from Xenia - a FidoNet mailer front-end like Binkleyterm - the same should
work with any program which passes a handle to the comm port. In this case
the handle is passed in the second parameter as -p3 (not the same 3 as in
the parse var line) This is just a simple illustration to show that it does
work.

/* */
call RxFuncAdd 'RxAsyncLoadFuncs', 'RXASYNC', 'RxAsyncLoadFuncs'
call RxAsyncLoadFuncs

parse arg var1 var2 var3

parse var var2 3 PortHandle
Remaining     = 0
crlf          = '0D0A'x

rc = RxAsyncWrite( PortHandle, 0, 'hello'crlf, 'Remaining' )
rc = RxAsyncWrite( PortHandle, 0, 'going now...'crlf, 'Remaining' )
rc = RxAsyncWrite( PortHandle, 0, 'bye'crlf, 'Remaining' )

exit


... now I'll have to see if I can do anything more useful with it.


John

--- GoldED/2 2.50.Beta4+