Resolving The Problem
Note: DSPUSRPRF does not indicate whether a user profile is disabled for NetServer use. The STATUS setting on a user profile displays either *ENABLED or *DISABLED, but a profile can be disabled for NetServer use even though the STATUS of the profile is *ENABLED.
- Option 1: Using Navigator for i
Navigator for i can be used to display a list of user profiles that are disabled for NetServer use. Access the Disabled User IDs screen by taking the following steps in Navigator:
1. Expand Network 2. Expand All Tasks 3. Expand IBM i NetServer 4. Select Disabled User IDs
- Option 2: Examining the QSYSOPR Message Queue
A message CPIB682 - User profile &1 disabled for IBM i Support for Windows Network Neighborhood access is sent to the QSYSOPR message queue when a profile is initially disabled for NetServer use. The QSYSOPR message queue can be displayed by running the following command on an OS/400 or i5/OS command line:
Press the Enter key.
DSPMSG is of limited use for determining which profiles are disabled for i5/OS NetServer use because the message is only issued when the profile is initially displayed. Because the QSYSOPR message queue receives many messages, if it's more that a few minutes since the profile became disabled for NetServer, it might be difficult to find the message.
Note: See IBM technote N1010973 CPIB682 Message Recovery Text is Outdated.
- Option 3: Examining the QHST History Log
Examining the QHST History Log is a more reliable way of determining which profiles are disabled for NetServer use. When the CPIB682 message is sent to the QSYSOPR message queue, it is also sent to the QHST History Log and remains there until the current log is deleted. To view the messages in the QHST History Log, run the following command on an i5/OS command line:
Press the Enter key.
All instances of CPIB682 generated since the current history log began are displayed by the DSPLOG command.
Note: See IBM technote https://www.ibm.com/support/pages/cpib682-message-recovery-text-outdated
- Option 4: Using the GO NETS Tool
The IBM i NetServer home page contains information about the GO NETS tool, which is a command line interface to the NetServer APIs. The tool provides a menu that can be used to run the commands and is part of the Example Tools Library, which is Option 7 of the OS/400 product.
At all currently supported OS/400 versions, GO NETS code is shipped with OS/400 and is located in the QUSRTOOL library.
However, the GO NETS menu must be created before it can be used. Follow directions in IBM technote N1021773 'How to manage IBM i NetServer without Navigator'. Technote N1021773 can be found online at:
The NETS menu (on current versions of the tool) includes Option 12, Work with NetServer Users, which displays a list of profile disabled for NetServer use (similar to the list in System i Navigator).
Enabling User Profiles
In the past, the CHGUSRPRF command could be used to reenable profiles for NetServer use.
The following PTFs for NetServer remove the ability of the CHGUSRPRF command to reset, or reenable, a user that is disabled for NetServer access - see APAR MA42015. Individual users can be reenabled by using the GO NETS menu, by using IBM i Navigator, or writing a program that makes use of the QZLSCHSI API.
540: MF55657 (not included on any Cumulative PTF Package)
545: MF55658 (not included on any Cumulative PTF Package)
610: MF55659 (on Cumulative PTF Package 2305)
611: MF55660 (on Cumulative PTF Package 2305)
710: MF55661 (on Cumulative PTF Package 2279)
All of the PTFs became available in May 2012.
The following technotes provide sample as-is CL programs (no support provided for these programs) that use the QZLSCHSI API to reenable NetServer users.
N1010992 CL Program and Command to Re-Enable NetServer Users
N1010645 Automatically Re-Enable a Disabled IBM i NetServer User Profile
Note: All profiles are reenabled for i5/OS NetServer use when NetServer is restarted from the System i Navigator screen or by running the STRTCPSVR *NETSVR command. All profiles are also reenabled for NetServer use when the IBM i system is IPL'd.
18 December 2019