Re: User Profile API Question

[Gord Hutchinson <gordm1@xxxxxxxxxxxxxxx>]

I put TZLSWRKUSR on our help desk menu quite sometime ago & it works
great.  Changed it to be owned by QSECOFR  & use *OWNER authority and it
cut down a lot on our usage of QSECOFR.


Gord



On Thu, Jan 5, 2017 at 10:21 AM, Rich Loeber <rich@xxxxxxxxx> wrote:

>    Glenn,
>
>    Never mind that last question.  I found the API documentation and I see
>    that ZLSL0900 only shows disabled users.  This is PERFECT!
>
>    Thanks.
>
>    Rich
>
>    ------------------------------------------------------------
> --------------
>
>    On 1/5/2017 9:58 AM, Glenn Gundermann wrote:
>
>  Option 12 on the NETS menu executes program TZLSWRKUSR.
>  Some of the code is as follows:
>
>  DCL        VAR(&DATA)      TYPE(*CHAR) LEN(9999)
>  DCL        VAR(&LSTI)      TYPE(*CHAR) LEN(64)
>
>  CALL       PGM(QZLSOLST) PARM(&DATA X'0000270F' &LSTI +
>               'ZLSL0900' '               '  X'00000000')
>
>  CHGVAR &NBRUSERS %BINARY(&LSTI 5 4)
>
>  A list of users is contained in &DATA.
>
>
>  Yours truly,
>
>  Glenn Gundermann
>  Email: [1]glenn.gundermann@xxxxxxxxx
>  Work: (905) 486-1162 x 239
>  Cell: (416) 317-3144
>
>
>  On 5 January 2017 at 09:46, Jeff Crosby [2]<jlcrosby@xxxxxxxxxxxxxxxx>
> wrote:
>
>
>  Not that this is much help (since you're wanting to do it
> programmatically)
>  but I use the GO NETS menu.
>
>  There is a Work with Netserver users on that menu that will show disabled
>  Netserver users, so there must be SOME way to figure it out.
>
>
>  On Thu, Jan 5, 2017 at 9:43 AM, Kevin Bucknum [3]<
> Kevin@xxxxxxxxxxxxxxxxxxx>
>  wrote:
>
>
>  QZLSLSTI with the ZLS0900 format should be the right one. I haven't
>  tried that one, but I've used the API  with other formats before.
>  [4]http://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/
> apis/qzlslsti.ht
>  m
>
>
>
>
>
>  Kevin Bucknum
>  Senior Programmer Analyst
>  MEDDATA/MEDTRON
>  Tel: 985-893-2550
>
>  -----Original Message-----
>  From: MIDRANGE-L [[5]mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of
>  Rich Loeber
>  Sent: Thursday, January 5, 2017 8:34 AM
>  To: Midrange Systems Technical Discussion
>  Subject: Re: User Profile API Question
>
>
>     I have used RTVUSRPRF, but it does not tell me when the windows
>     neighborhood access is disabled.  When that happens, regular access
>  still
>     works on the IBM i and the status remains set to *ENABLED.
>
>     Rich
>
>
>  ------------------------------------------------------------------------
>  --
>
>     On 1/5/2017 9:26 AM, David Gibbs wrote:
>
>       On 1/5/2017 8:22 AM, Rich Loeber wrote:
>
>         I'm looking for an API that will let me know if a user profile is
>         disabled for windows neighborhood purposes.  I've been scanning
>  the
>         API lists and delving into a few of these, but no joy so far.
>
>       Create a wrapper around RTVUSRPRF?
>
>       You would probably have to make it owned by QSECOFR (or another
>       privileged profile) and have it adopt *OWNER authority.
>
>       david
>  --
>  This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
>  list To post a message email: [6]MIDRANGE-L@xxxxxxxxxxxx To subscribe,
>  unsubscribe, or change list options,
>  visit: [7]http://lists.midrange.com/mailman/listinfo/midrange-l
>  or email: [8]MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take
> a
>  moment to review the archives at [9]http://archive.midrange.
> com/midrange-l.
>
>  Please contact [10]support@xxxxxxxxxxxx for any subscription related
>  questions.
>
>  Help support midrange.com by shopping at amazon.com with our affiliate
>  link: [11]http://amzn.to/2dEadiD
>  --
>  This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
>
>  list
>
>  To post a message email: [12]MIDRANGE-L@xxxxxxxxxxxx
>  To subscribe, unsubscribe, or change list options,
>  visit: [13]http://lists.midrange.com/mailman/listinfo/midrange-l
>  or email: [14]MIDRANGE-L-request@xxxxxxxxxxxx
>  Before posting, please take a moment to review the archives
>  at [15]http://archive.midrange.com/midrange-l.
>
>  Please contact [16]support@xxxxxxxxxxxx for any subscription related
>  questions.
>
>  Help support midrange.com by shopping at amazon.com with our affiliate
>  link: [17]http://amzn.to/2dEadiD
>
>
>
>
>  --
>
>
>  Jeff Crosby
>  VP Information Systems
>  UniPro FoodService/Dilgard
>  P.O. Box 13369
>  Ft. Wayne, IN 46868-3369
>  260-422-7531
>  [18]www.dilgardfoods.com
>
>  The opinions expressed are my own and not necessarily the opinion of my
>  company.  Unless I say so.
>  --
>  This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
> list
>  To post a message email: [19]MIDRANGE-L@xxxxxxxxxxxx
>  To subscribe, unsubscribe, or change list options,
>  visit: [20]http://lists.midrange.com/mailman/listinfo/midrange-l
>  or email: [21]MIDRANGE-L-request@xxxxxxxxxxxx
>  Before posting, please take a moment to review the archives
>  at [22]http://archive.midrange.com/midrange-l.
>
>  Please contact [23]support@xxxxxxxxxxxx for any subscription related
>  questions.
>
>  Help support midrange.com by shopping at amazon.com with our affiliate
>  link: [24]http://amzn.to/2dEadiD
>
> References
>
>    Visible links
>    1. mailto:glenn.gundermann@xxxxxxxxx
>    2. mailto:jlcrosby@xxxxxxxxxxxxxxxx
>    3. mailto:Kevin@xxxxxxxxxxxxxxxxxxx
>    4. http://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/
> apis/qzlslsti.ht
>    5. mailto:midrange-l-bounces@xxxxxxxxxxxx
>    6. mailto:MIDRANGE-L@xxxxxxxxxxxx
>    7. http://lists.midrange.com/mailman/listinfo/midrange-l
>    8. mailto:MIDRANGE-L-request@xxxxxxxxxxxx
>    9. http://archive.midrange.com/midrange-l
>   10. mailto:support@xxxxxxxxxxxx
>   11. http://amzn.to/2dEadiD
>   12. mailto:MIDRANGE-L@xxxxxxxxxxxx
>   13. http://lists.midrange.com/mailman/listinfo/midrange-l
>   14. mailto:MIDRANGE-L-request@xxxxxxxxxxxx
>   15. http://archive.midrange.com/midrange-l
>   16. mailto:support@xxxxxxxxxxxx
>   17. http://amzn.to/2dEadiD
>   18. http://www.dilgardfoods.com/
>   19. mailto:MIDRANGE-L@xxxxxxxxxxxx
>   20. http://lists.midrange.com/mailman/listinfo/midrange-l
>   21. mailto:MIDRANGE-L-request@xxxxxxxxxxxx
>   22. http://archive.midrange.com/midrange-l
>   23. mailto:support@xxxxxxxxxxxx
>   24. 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