× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



Rob,

Thanks for your answer. I already had the URL for the DB2 Services (it's a
nice reference).
Had not thought of checking the Memo to Users...Good idea.

So I suppose they must have acess to that register. Will have to ask him
for the exact SQL sentence he is trying to execute.

Thanks again,
Luis

On Wed, May 10, 2017 at 1:10 PM Rob Berendt <rob@xxxxxxxxx> wrote:

Why yes there is, but that's for services.
http://ibm.biz/DB2foriServices

I don't see one for special registers like CLIENT_WRKSTNNAME.

It is referred in the 6.1 Infocenter

https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_61/db2/rbafzcurclws.htm

And "Client special registers" appears in "What's new for V6R1" at

https://www.ibm.com/support/knowledgecenter/ssw_ibm_i_61/db2/rbafzwhatsnew.htm


Rob Berendt
--
IBM Certified System Administrator - IBM i 6.1
Group Dekko
Dept 1600
Mail to: 2505 Dekko Drive
Garrett, IN 46738
Ship to: Dock 108
6928N 400E
Kendallville, IN 46755
http://www.dekko.com





From: Luis Rodriguez <luisro58@xxxxxxxxx>
To: Midrange Systems Technical Discussion <midrange-l@xxxxxxxxxxxx>
Date: 05/10/2017 12:49 PM
Subject: Finding the Release/TR number for a SQL feature
Sent by: "MIDRANGE-L" <midrange-l-bounces@xxxxxxxxxxxx>



Hi all,


Is there any (easy) way to know when (release/TR) a particular DB2 feature
was introduced?


Someone I know was trying to read the CLIENT_WRKSTNNAME special register
and was getting an error message (sorry, don’t have the specific message
code).


They are using 7.1. Don’t know their TR level, though…



Thanks in advance,



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.