× 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.



Just checked on this a few minutes ago. My RFE has 14 votes, double from
when I checked on Friday. I noticed "Most recent IBM developer update:
IBM_Systems_Developer
<https://www.ibm.com/developerworks/community/profiles/user/IBM_Systems_Developer>
(IBM)
Creating a new RFE based on Community RFE #89070 in product IBM i."

Not sure what that means. Does IBM create an internal RFE not accessible
outside of IBM?

- Dan

On Fri, May 27, 2016 at 2:35 PM, Dan <dan27649@xxxxxxxxx> wrote:

Yesterday, I created an RFE based on a discussion on this thread:
http://archive.midrange.com/midrange-l/201605/msg00833.html

Because this appeal was buried in that thread, I wanted to put out this
new thread to get more attention. I am asking everyone to review the RFE
and to consider voting for it. (To the six of you who already have, thank
you!)

Essentially, my RFE asks IBM to enhance the SYSPSTAT (aka
QSYS2.PARTITION_STATISTICS) SQL routine to include the source member text.
It currently returns the source member name, the source type, the last
source update timestamp, the source creation timestamp, and the "last
source type and/or member text changed" timestamp. (An SQL example is in
the aforementioned post.) Channeling Spock, it follows logically that the
source member text should be included in that list. ;-)

Link to the RFE:
http://www.ibm.com/developerworks/rfe/execute?use_case=viewRfe&CR_ID=89070

Thanks!
- Dan


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.