RE: QWCRSSTS problem

In fact, this particular application doesn't have a compelling need
for
speed. It's something from some shareware/freeware called
TOOLKIT400, and
it's an e-mail application that usually runs in batch, once per job.
The
program calls the API to get the system name to form the domain part
of
the sender address. The call to QWCRNETA (vs QWCRSSTS) is actually
much
faster. A call to the mail send program can hang up for four to
seven or
eight seconds while it makes the call to QWCRSSTS, which doesn't
even

Wow, that is significant! On a very small partition of an 820 system
running V5R3, the code at http://code.midrange.com/47c41e30a6.html executes
100 iterations of this API in about three seconds. Not saying you're wrong
at all. But this is certainly worthy of reporting to your support provider.

BTW: to me, even three hundredths of a second for this API seems outlandish.
I had no idea this was such a poor performer, as I've not had occasion to
use it before. I'd be interested in knowing your results, if you have the
time and inclination to test.

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
"They couldn't hit an elephant at this dist---"
-- last words of Union army commander John Sedwick as he addressed
his troops during a (US) Civil War battle