![]() |
Chapter 23. Analyzing Problems -- Enhanced Integration for NetWare
![]() User Enrollment Problems This section describes how you can view the QNETWARE and QPRFSYNCH job logs and work with enrollment status to solve the various problems that you might encounter when you enroll AS/400 profiles on NetWare. The QNETWARE job handles the NetWare profile enrollment requests. The QNETWARE job, which runs in the QSYSWRK subsystem under the QSYS profile, logs error messages received during all profile enrollment operations. Most errors are written to the QNETWARE job log; more severe errors are written to the QSYSOPR message queue. To view the status of the QNETWARE job, and to obtain a list of previous QNETWARE jobs:
![]() +--------------------------------------------------------------------------------+ | Select Job ROCHSYS | | 07/31/96 10:20:38 | | Type option, press Enter. | | 1=Select | | | | Entered | | Option Job User Number Type -----Status----- System | | 1 QNETWARE QSYS 001476 BATCH ACTIVE 07/30/96 | | QNETWARE QSYS 000962 BATCH OUTQ 07/19/96 | | | | | | | | | | | | | | | | | | | | | | | | | | Bottom | | F3=Exit F12=Cancel | | | +--------------------------------------------------------------------------------+
![]() The QPRFSYNCH job (program QSYS/QFPAPRFJ) is used to evaluate user profile create or change requests, and to determine if the requests require enrollment on any NetWare servers. If enrollment is required, this job notifies the QNETWARE job of the necessary work to be done. This job runs when:
![]() When the QSYSWRK subsystem is started, an autostart job (QFSIOPJOB) runs and submits both the QNETWARE and QPRFSYNCH jobs to run in this subsystem if needed. If either job ends, the jobs are restarted automatically when one of the following actions occur:
If an error code appears, use option 16 to view the error message that is associated with the error code. Although the message text associated with the error appears, substitution text, such as the server name, does not. However, when the message is sent to the QNETWARE job log, the substitution text does appear. Some error codes have a one-to-one relationship with an associated error message. Many of the NetWare-specific messages, however, simply show the NetWare error code, with a generic message indicating an error occurred while calling a NetWare function. In this case, the error message has some explanatory text for some of the common NetWare errors. Not all errors, however, are described in the message text. The following error codes might appear:
For example, if a new group profile is created and then defined to have all its group members enrolled on a NetWare server. If the QRETSVRSEC value is set to 0, passwords for the group members are not immediately available, so the 6011 error appears for all the group members. If one of these users signs on to AS/400, the password information is captured automatically and the 6011 error is resolved. Until the user signs on, or the password is changed using the CHGPWD or CHGUSRPRF command, this profile remains in a pending state. This error can also occur if the QRETSVRSEC system value is set to 1, and the user password has never been set or changed since the system value was set. To resolve the error, either the user needs to sign on to AS/400 or the password needs to be changed using the CHGPWD or CHGUSRPRF command. Message FPE0232 - User not connected to serverRead the second level help text of this message. Usually the problem is because there is not an authentication entry in the user profile for the server specified. See previous messages and if the diagnostic error is FPE0215, then an authentication entry does not exist. Use the WRKNTWAUTE command and add an authentication entry for the NDS tree the server is in (or the server if the server is NetWare 3.12). Another option is to use the STRNTWCNN command to manually start a connection to the server that is documented in the second level help text of this error. Note that the STRNTWCNN is active only until the user signs off, whereas setting up an authentication entry automates this process. Another way to automate this process by having the authentication entries automatically created for you, is to use AS/400 user enrollment. See Chapter 21. "Managing User Enrollment". If the previous diagnostic error is FPE0234, then an authentication entry was used, but the password in the authentication entry was *STRNTWCNN. This can happen if it is purposely set this way, or the QRETSVRSEC system value is set to 0 (passwords cannot be stored in the authentication entry). See page "Step 2--Set Up AS/400 for User Enrollment" for changing the QRETSVRSEC system value. After this is done, you then need to update the authentication entries with the correct password by using the WRKNTWAUTE command. Another option is to manually start a connection and specify the password. This is only active for the current session. If AS/400 returns error FPE023F when a user enters the End NetWare Connection (ENDNTWCNN) command or error CPFA448 when a user enters the Submit NWS Command (SBMNWSCMD) command, the user does not have operator rights to the system object. If you want the user to have the rights to do this function, you must add the user to the system object in the NDS tree.
Supervisor Optionsand then File Server Console Operatorsto view or change the list of operators. Communication Errors Message FPE0250 - Request to server failed with communication error Read the second level text. If the reason code is not documented then it is most likely the server is not active. Use the documented recovery actions by checking the IPX status using the WRKIPXSTS command, option 3. CPFE00E from WRKIPXSTS means that IPX has not been started. In order to use Enhanced Integration for NetWare, you must start IPX using the STRIPX command. See page Chapter 15. "Configuring Enhanced Integration for NetWare" for configuring IPX support. Cannot access the NetWare Enhanced Integration NLM If trying to use commands that access the Enhanced Integration for NetWare NLM on a server, such as using the QNetWare file system, WRKNTWVOL, or WRKNTWCNN for starting a connection, and the server is not responding, your problem could be that you have either not installed the NLM or you have installed the NLM, but it is not loaded. If you have not installed the NLM on the server (a local Integrated PC Server or a remote server), see "Step 3--Install the Enhanced Integration for NetWare NLM on the Servers". This section also explains how to automatically have the NLM loaded whenever the server is restarted. To see if AS/400 has the server in its IPX list, use the WRKIPXSTS command, option 3. If the server is in the list with a service type of *ENHNTWINTG, the Enhanced Integration for NetWare NLM is running on the server. If you get the error CPFE00E from WRKIPXSTS, then you have not started IPX. See page Chapter 15. "Configuring Enhanced Integration for NetWare" for configuring IPX support. You can also do RCONSOLE to the server and use the NetWare command MODULES to see if the AS4NW410 or AS4NW312 NLM is loaded. If the server is a local Integrated PC Server, use the command: SBMNWSCMD CMD(MODULES) SERVER(server_name) SVRTYPE(*NETWARE) CMDTYPE(*NETWARE)
![]() SBMNWSCMD CMD('LOAD SYS:AS4NW\AS4NW410') SERVER(server_name) SVRTYPE(*NETWARE) CMDTYPE(*LCLNTW)Storage space not automatically partitioned A new network server storage space for a local Integrated PC Server is automatically partitioned by the monitor job if the Enhanced Integration for NetWare NLM is loaded and is contacted by the monitor job. Sometimes this takes a few minutes. If you need to create a volume for the storage space and it has not been partitioned yet, you can use LOAD INSTALL from RCONSOLE and manually partition it. This would need to be done if you do not have Enhanced Integration for NetWare as well. If the Enhanced Integration for NetWare NLM is not running on the local Integrated PC Server, then automatic partitioning cannot occur. Use the SBMNWSCMD command, as documented in the previous section, to see what modules are loaded on your local server. If automatic partitioning is still not occurring, you can try to restart
the monitor job from the WRKNWSSTS panel, option 14. Sometimes the Enhanced
Integration for NetWare NLM is loaded after the monitor job has stopped
retrying to contact it, so the monitor job must be restarted to attempt
to contact the NLM again.
QNetWare File System Problems This section describes various problems that you might encounter when you work with the QNetWare file system.
Make sure AS/400 can see the NLM by using WRKIPXSTS option 3 and looking for a *NTWEHNINTG entry for the server. For better performance, the list of servers is only updated periodically. To force the entire list of servers to be updated, enter CALL QFPNTWE/QFPZCTL PARM(*UPDSRVL).
Information passed to this operation was not valid.For NetWare 3.12, make sure the user exists in the NetWare Bindery for the server. For NetWare 4.1, make sure the user exists in the NDS tree and that the NDS context is correct. The user's context must be set either to the context the user exists in or to the job context, or the system context must be set to the correct context.
Auditing is not supported by QNetWare so you need to specify CRTOBJAUD(*NONE).
Do one of the following: DTAAUT(*NONE) OBJAUT(*NONE)If error CPFA0BC occurs when you use the MKDIR command with DTAAUT(*NONE) OBJAUT(*NONE). Use DTAAUT(*INDIR) OBJAUT(*INDIR) instead.
Information passed to this operation was not valid.For NetWare 3.12, make sure that each user authorized to the file and the owner of the file exist in the NetWare Bindery for the server. For NetWare 4.1, make sure that each user authorized to the file and the owner of the file exist in the NDS tree and that their NDS context is correct. The user's context must be set either to the context the user exists in or to the job context, or the system context must be set to the correct context. You can use the DSPAUT command to display the authorized users and owner of a file.
![]() Requests for network resources or services require identification of the NDS object context so the object can be located or created. The current context is the position of the NetWare object in the NDS tree The current context remains in effect until the job ends or until you change it using the CHGNDSCTX command. The current context is changed only for the job in which the command is run. To identify NDS objects, list the current context and the path from the object to the current position in the NDS tree. Applying a PTF to a Enhanced Integration for NetWare NLM When you apply a PTF to a Enhanced Integration for NetWare NLM, AS/400 does not automatically activate the changes. The PTF puts the updated version of the NLM into the AS/400 Integrated File System in the /qdls/qfpntwe directory. To activate the changes when applying a PTF to an NLM, copy the appropriate NLM from the AS/400 Integrated File System to the AS4NW directory on the SYS: volume of each NetWare server in your network that has the Enhanced Integration for NetWare NLM product installed on it.
![]()
Do the following on each NetWare server to be updated:
If the server is running NetWare 4.10 or higher, run the following command at the server's console: load sys:as4nw\as4nw410If the server is running NetWare 3.12, run the following command at the server's console: load sys:as4nw\as4nw312 modulesThe description of the Enhanced Integration for NetWare NLM provides its version number. If the version currently on the server is equal to or greater than the NLM version listed in the PTF cover letter, you do not need to update the NLM on this server. Skip the remaining instructions. ![]()
You must be enrolled in the AS/400 directory to access /qdls/qfpntwe. If you are not enrolled in the directory, use the ADDDIRE command to enroll.
To establish a connection to the server, enter WRKNWSSTS. Page down to the server and select Start connection. If you don't have an authentication entry for the server being updated, establish a connection to the server using the STRNTWCNN command.
If the server is running NetWare 4.10 or higher run
CPY OBJ('/qdls/qfpntwe/as4nw410.nlm')
RMVLNK OBJLNK('/qnetware/server1.svr/sys/as4nw/as4nw312.nlm') CPY OBJ('/qdls/qfpntwe/as4nw312.nlm') TODIR('/qnetware/server1.svr/sys/as4nw')
Wait until the server's file system in not use by the Integrated File System of any AS/400 system. If the server is running NetWare 4.10 or higher, run the following commands at the server's console: unload as4nw410 load sys:as4nw\as4nw410If the server is running NetWare 3.12, run the following commands at the server's console: unload as4nw312 load sys:as4nw\as4nw312 [ Top of Page | Previous Page | Next Page | Table of Contents | Index ] |