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



On 19-Jan-2015 11:18 -0600, CRPence wrote:
<<SNIP>> the API was invoking the List-Object, yet the API implies
nothing about the ability to specify a Generic* name nor
Special-Value; neither the lone asterisk nor the value *ALL are
documented.
<http://www.ibm.com/support/knowledgecenter/ssw_ibm_i_72/apis/qsyrusra.htm>

So I tested myself by invoking the API directly with the '*'
<<SNIP>>


Following this paragraph is a simple CLP source available to show the effects of the API invocation using '*'; easily modified [changing which is the commented line] to use the value '*ALL' instead. The time taken for the request can be measured with the wall-clock, and the effect of the authorization information being returned for only one [unknown] user profile object should be apparent from the dumped receiver variable; however if the alphabetically first and last user profiles [perhaps those as unauthorized and another authorized user profile] all have a different group profile, then one might be able to infer which user profile the information is being returned for [since from the API docs, there can be only one] when the special value is used instead of an actual\valid user profile name.

dcl &rcv *char 9999
dcl &rln *int 4 value(9999)
call qsyrusra parm( &rcv &rln 'USRA0100' +
'*CURRENT' '* QSYS ' +
/*'*CURRENT' '*ALL QSYS ' */ +
'*USRPRF' x'0000000000000000' )
dmpclpgm
/* dspsplf qppgmdmp splnbr(*last) */


As an Amazon Associate we earn from qualifying purchases.

This thread ...


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.