Re: User Profile API Question - CL Program and Command to Re-Enable NetServer Users -- MIDRANGE-L

Thanks Paul, I already have that part of the puzzle in play.

Rich

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

On 1/5/2017 11:04 AM, Steinmetz, Paul wrote:

CPIB682 will appear in QSYSMSG

In my MPLUS/HALCYON monitoring program, check for CPIB682 ,
if a netserver user becomes disabled, I automatically re-enable them.

Netserver Disabled-renable

Opt Seq I/E Message ID Type Sev Job User Cmp Usage
10 I CPIB682 *ALL *ALL *ALL N 3431
User profile &1 disabled for IBM i Support for Win

IBM supplies the below source.

[1]http://www-01.ibm.com/support/docview.wss?uid=nas8N1010992

I created a command called RSTNETUSR

Command:
SBMJOB CMD(RSTNETUSR USER('&1')) JOB(RSTNETUSR) JOBQ(QSYSNOMAX)
USER(PRODUCT)

Paul

-----Original Message-----
From: MIDRANGE-L [[2]mailto:midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Rich Loeber
Sent: Thursday, January 05, 2017 10:22 AM
To: Midrange Systems Technical Discussion
Subject: Re: User Profile API Question

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: [[3]1]glenn.gundermann@xxxxxxxxx
Work: (905) 486-1162 x 239
Cell: (416) 317-3144

On 5 January 2017 at 09:46, Jeff Crosby [2][4]<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][5]<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][6]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][7]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: [[8]6]MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: [7][9]http://lists.midrange.com/mailman/listinfo/midrange-l
or email: [[10]8]MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at [9][11]http://archive.midrange.com/midrange-l.

Please contact [[12]10]support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: [11][13]http://amzn.to/2dEadiD
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing

list

To post a message email: [[14]12]MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: [13][15]http://lists.midrange.com/mailman/listinfo/midrange-l
or email: [[16]14]MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at [15][17]http://archive.midrange.com/midrange-l.

Please contact [[18]16]support@xxxxxxxxxxxx for any subscription related questions.

Help support midrange.com by shopping at amazon.com with our affiliate
link: [17][19]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: [[20]19]MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: [20][21]http://lists.midrange.com/mailman/listinfo/midrange-l
or email: [[22]21]MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives at [22][23]http://archive.midrange.com/midrange-l.

Please contact [[24]23]support@xxxxxxxxxxxx for any subscription related questions.

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

References

Visible links
1. [26]mailto:glenn.gundermann@xxxxxxxxx
2. [27]mailto:jlcrosby@xxxxxxxxxxxxxxxx
3. [28]mailto:Kevin@xxxxxxxxxxxxxxxxxxx
4. [29]http://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/apis/qzlslsti.ht
5. [30]mailto:midrange-l-bounces@xxxxxxxxxxxx
6. [31]mailto:MIDRANGE-L@xxxxxxxxxxxx
7. [32]http://lists.midrange.com/mailman/listinfo/midrange-l
8. [33]mailto:MIDRANGE-L-request@xxxxxxxxxxxx
9. [34]http://archive.midrange.com/midrange-l
10. [35]mailto:support@xxxxxxxxxxxx
11. [36]http://amzn.to/2dEadiD
12. [37]mailto:MIDRANGE-L@xxxxxxxxxxxx
13. [38]http://lists.midrange.com/mailman/listinfo/midrange-l
14. [39]mailto:MIDRANGE-L-request@xxxxxxxxxxxx
15. [40]http://archive.midrange.com/midrange-l
16. [41]mailto:support@xxxxxxxxxxxx
17. [42]http://amzn.to/2dEadiD
18. [43]http://www.dilgardfoods.com/
19. [44]mailto:MIDRANGE-L@xxxxxxxxxxxx
20. [45]http://lists.midrange.com/mailman/listinfo/midrange-l
21. [46]mailto:MIDRANGE-L-request@xxxxxxxxxxxx
22. [47]http://archive.midrange.com/midrange-l
23. [48]mailto:support@xxxxxxxxxxxx
24. [49]http://amzn.to/2dEadiD
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list To post a message email: [50]MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit: [51]http://lists.midrange.com/mailman/listinfo/midrange-l
or email: [52]MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at [53]http://archive.midrange.com/midrange-l.

Please contact [54]support@xxxxxxxxxxxx for any subscription related questions.

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

References

Visible links
1. http://www-01.ibm.com/support/docview.wss?uid=nas8N1010992
2. mailto:midrange-l-bounces@xxxxxxxxxxxx
3. mailto:1]glenn.gundermann@xxxxxxxxx
4. mailto:jlcrosby@xxxxxxxxxxxxxxxx
5. mailto:Kevin@xxxxxxxxxxxxxxxxxxx
6. http://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/apis/qzlslsti.ht
7. mailto:midrange-l-bounces@xxxxxxxxxxxx
8. mailto:6]MIDRANGE-L@xxxxxxxxxxxx
9. http://lists.midrange.com/mailman/listinfo/midrange-l
10. mailto:8]MIDRANGE-L-request@xxxxxxxxxxxx
11. http://archive.midrange.com/midrange-l
12. mailto:10]support@xxxxxxxxxxxx
13. http://amzn.to/2dEadiD
14. mailto:12]MIDRANGE-L@xxxxxxxxxxxx
15. http://lists.midrange.com/mailman/listinfo/midrange-l
16. mailto:14]MIDRANGE-L-request@xxxxxxxxxxxx
17. http://archive.midrange.com/midrange-l
18. mailto:16]support@xxxxxxxxxxxx
19. http://amzn.to/2dEadiD
20. mailto:19]MIDRANGE-L@xxxxxxxxxxxx
21. http://lists.midrange.com/mailman/listinfo/midrange-l
22. mailto:21]MIDRANGE-L-request@xxxxxxxxxxxx
23. http://archive.midrange.com/midrange-l
24. mailto:23]support@xxxxxxxxxxxx
25. http://amzn.to/2dEadiD
26. mailto:glenn.gundermann@xxxxxxxxx
27. mailto:jlcrosby@xxxxxxxxxxxxxxxx
28. mailto:Kevin@xxxxxxxxxxxxxxxxxxx
29. http://www.ibm.com/support/knowledgecenter/ssw_ibm_i_73/apis/qzlslsti.ht
30. mailto:midrange-l-bounces@xxxxxxxxxxxx
31. mailto:MIDRANGE-L@xxxxxxxxxxxx
32. http://lists.midrange.com/mailman/listinfo/midrange-l
33. mailto:MIDRANGE-L-request@xxxxxxxxxxxx
34. http://archive.midrange.com/midrange-l
35. mailto:support@xxxxxxxxxxxx
36. http://amzn.to/2dEadiD
37. mailto:MIDRANGE-L@xxxxxxxxxxxx
38. http://lists.midrange.com/mailman/listinfo/midrange-l
39. mailto:MIDRANGE-L-request@xxxxxxxxxxxx
40. http://archive.midrange.com/midrange-l
41. mailto:support@xxxxxxxxxxxx
42. http://amzn.to/2dEadiD
43. http://www.dilgardfoods.com/
44. mailto:MIDRANGE-L@xxxxxxxxxxxx
45. http://lists.midrange.com/mailman/listinfo/midrange-l
46. mailto:MIDRANGE-L-request@xxxxxxxxxxxx
47. http://archive.midrange.com/midrange-l
48. mailto:support@xxxxxxxxxxxx
49. http://amzn.to/2dEadiD
50. mailto:MIDRANGE-L@xxxxxxxxxxxx
51. http://lists.midrange.com/mailman/listinfo/midrange-l
52. mailto:MIDRANGE-L-request@xxxxxxxxxxxx
53. http://archive.midrange.com/midrange-l
54. mailto:support@xxxxxxxxxxxx
55. http://amzn.to/2dEadiD