Thanks for your answer.


First of all, I want to thank everyone who was able to make sense of my
awful original post (“checking the value of the value”? C’mon!!). I knew
that posting a question at 3am was pushing it (and yes, it seems that my
laptop is in another time zone). No excuses, though.


Ok. So it seems that the register name is a little bit misleading. The APAR
you wrote about states that:

-----------------------------------------------
When CURRENT CLIENT_WRKSTNNAME hasn't been set, the server name
is being returned. This isn't very useful. Returning the
subsystem name would be more useful.

-----------------------------------------------

I could argue that returning the subsystem name isn’t very useful either,
unless that the register is called CLIENT_SUBSYSTEMNAME…I think I will
write my own UDF just for the heck of it.

I wonder if a RFE is called for.


Thanks again. Although the company I work for decided long ago to leave its
I5 in the dark ages (we are a SAP/ORACLE/HP shop now), nowadays I’m trying
to get my IBM i skills up to date practicing in a “public” 7.3 system (
PUB400.COM).


Regards,
Luis

On Thu, May 11, 2017 at 4:04 AM Arco Simonse <arco400@xxxxxxxxx> wrote:

On our 7.3 system it also returns QINTER. That seems not of much value, I
would also expect to see the real workstation ID here.

Regards,
-Arco

2017-05-11 9:08 GMT+02:00 Luis Rodriguez <luisro58@xxxxxxxxx>:

Hi all,

I'm checking the value of the value of the CLIENT WRKSTNNAME special
register on a 7.3 system and I am getting QINTTER, instead of the
QPADxxxx
name of the 5250 session I'm working on. Any ideas why this could be so?

Thanks,
Luis
--

Luis Rodriguez
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.

Please contact support@xxxxxxxxxxxx for any subscription related
questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: http://amzn.to/2dEadiD


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:
Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.