RE: QWCRSSTS problem

We need the system name in a program so we've been using QWCRSSTS.
Apparently, on rare occasions, we are getting blanks in the name,

with

no error. I've been told to QWCRSSTS replace with RTVNETA. I don't

This sounds like the problem-solving approach that dominates an

operating

system from Macrosloth: "If it doesn't seem to work, then stop using

it and

use some other tool." Not cool, David, and I think you know that!

If there

is a problem with QWCRSSTS (doubt that, by the way, but...) then

report it!

I've encountered the same problem. I think it's real. The users (IT
developers; I'm an administrator) insist the application was working
correctly up to a week or so ago. That's about the time that IBM
(we've
outsourced our System i administration to them) put the latest PTFs on
the partition where we're encountering the error.

Well, I'd be surprised, but of course IBM are not perfect. Else there would
be no need for a PTF process, huh?

One of the points I was trying to make is that such things should be brought
to IBM's attention so that the problem may resolved... rather than just
silently not using the tool anymore.

I changed a copy of the application program we have that is getting the
blank system name using QWCRSSTS to use QWCRNETA, and the latter works
consistently. Not only that, the call is much faster.

Really? That's good news. How much faster? I'm fascinated that any
application would need to find out what system it's running on so frequently
that API speed makes any difference at all, so do tell. :)

Dennis Lovelady
http://www.linkedin.com/in/dennislovelady
--
Transmitted on 100% recycled electrons