Re: QWCRSSTS problem

Dennis Lovelady wrote:

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 see
the point in using QWCRNETA so I was just going to create a CL module
that does RTVNETA.

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.

You'll probably find that it's something silly in the code. (If you don't
want to or cannot report the problem, and if you could post a small example
that demonstrates the failure, we could have a look.)

Issue two: "I don't see the point in using QWCRNETA ..." Say, what? What
is it about this API that makes you "not see the point?" Do you need help
understanding the parameters, or is it something else?

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.