Frequently Asked Questions about using OS/400 Integration Products for NetWare. 



    General topics - Questions
  1. I'm trying to configure TCP/IP with Token-Ring and I need a LOAD ROUTE statement so my clients can connect to the server from another ring, but when I vary off and then vary on my server, the LOAD ROUTE statement is removed from the NETINFO.CFG file. Why is the ROUTE statement being removed? 
  2. Can I run Intel LANDesk components of ManageWise 2.1 on my Integrated PC Server? 
  3. Where can I find more information regarding support of Novell Client32? 
  4. Should I vary off my NWSDs before powering down the system? 
  5. After my server varies on, how can I access it from RCONSOLE when it does not show up in the list? 
  6. Why do I receive many "Loader cannot find public symbol" messages when I use the LOAD INETCFG command on RCONSOLE for an Integrated PC Server running NetWare for SAA? 
  7. What are some common commands to check my NetWare server? 
  8. What is the Enhanced Integration for NetWare NLM? 
  9. What is the difference between the configuration status and the NWS status? 
  10. When using SBMNWSCMD, why do I get CPFA448 (The user does not have the necessary console rights)? 
  11. Why can I not access the Enhanced Integration for NetWare NLM using Enhanced Integration functions on the AS/400? 
  12. What is the difference between a local (*LCL) and a remote (*RMT) server as shown on the WRKNWSSTS display? 
  13. Why does the configuration status of my server, which worked yesterday, remain at VARYON PENDING? 
  14. What differences are there between my PC server and the Integrated PC Server running on the AS/400? 

    Install - Questions
  1. Why does the configuration status remain at VARYON PENDING after installing NetWare on an Integrated PC Server and then varying it on for the first time? 
  2. I need to re-create my NWSD. What steps should I follow? 
  3. How do I upgrade a NetWare 4.10 server to 4.11? 
  4. Why do I get invalid path error when installing NetWare 4.11 on V3R2? 
  5. Why do I get CPDA488 with reason code 2 when installing NetWare 4.11 on V3R7? 
  6. When attempting to copy other files as described in the AS/400 integration for Novell NetWare manual, the PC running RCONSOLE seems to hang during the copy. Is there something I can do about this? 
  • How long should I expect the INSNTWSVR command to run when copying the CD to the server storage space of a RISC system? 
    1.  
      User enrollment - Questions

      Setup

    2. What steps should I perform before I start user enrollment? 
    3. What are authentication entries and how are they used? 
    4. How can I tell if the users are being propagated properly; where are the error codes displayed? 
    5. I'm trying to propagate users for the first time, and I get a 3401 error. Why? 
    6. I'm trying to propagate users for the first time, and I get a 6004 error. Why? 
    7. I'm trying to propagate users for the first time, and I get a 245 error. Why? 
    8. I'm trying to propagate users for the first time, and I get a 6000 error. Why? 
    9. I'm trying to propagate users for the first time, and I get a 601 error. Why? 
    10. I'm trying to propagate users for the first time, and I get a 613 error. Why? 

    11.  

       
       
       
       
       


       
      User and group propagation
    1. Why don't the user profiles on the AS/400 change when I make changes on the NetWare server? 
    2. Can I still create users with Novell NetWare while enrolling users from the AS/400? 
    3. In that case, can I have groups on the NetWare server that are not on the AS/400? 

    4.  

       
       
       
       
       


       
      Group-specific propagation
    1. I enrolled a group with several users, but the users were not created on the NetWare server. What could be wrong? 
    2. I enrolled a group why does the WRKNWSENR screen show a 6011 error? 
    3. How can I display users within groups on the WRKNWSENR display? 

       

      Miscellaneous enrollment topics

    1. I just removed a server, and am now trying to delete all the users that were on the server, but they are now all at *DLTFAIL. How can I get rid of all these errors, because the server's not really even there any more? 
    2. I've been doing enrollment for awhile now, and all of a sudden I'm getting 245 errors everywhere. Why? 
    3. When I select option 16 on the WRKNWSENR display to look at error details, why are replacement symbols(&1, &2, etc.) displayed instead of the actual values? 
    4. What is QRETSVRSEC and how can it be changed? 

      Monitor job - Questions
    1. Why is the message "Basic functions available for network server" sent in the monitor job? 
    2. How can I cause the monitor job to contact the Enhanced Integration for NetWare NLM again? 
    3. Why can't I find the joblog for a monitor job that ended previously? 
    4. When viewing the monitor joblog or message queue for the running Integrated PC Server, why are the NetWare console messages often repeated? 

      QNetWare file system - Questions
    1. What is the QNetWare file system? 
    2. How can the QNetWare file system be used? 
    3. Can I write applications to access the QNetWare file system? 
    4. What should I do if the server does not show up under /QNetWare when using the WRKLNK command? 
    5. What should I do if the next level of server volumes is not displayed when using the WRKLNK command? 
    6. What should I do if I am not authorized to a file or directory? 
    7. What should I do if I can't make a directory using the MKDIR command? 
    8. What should I do if I can't move a file using the MOV command? 
    9. How can I check the NDS context? 

    10.  

      Connections - Questions
    1. Why do I get message FPE0232 (User not connected to server) when using NetWare commands from the AS/400? 
    2. Why do I get message FPE0234 (Password *STRNTWCNN not allowed) when I have an authentication entry set up? 
    3. Why do I get message FPE0215 (Could not find authentication entry)? 

      Volumes - Questions
    1. What is the *IOSYSCFG authority that I need before using any of the volume management commands? 
    2. Why do the CRTNTWVOL and CHGNTWVOL CL commands receive an "invalid device" error for a storage space, even though that storage space was just created and linked to the server? 
    3. When creating or changing a volume, why does message FPE023F (Server operator privileges required) result? 
    4. Why can I still use the WRKNTWVOL (Work with NetWare volumes) and DSPNTWVOL (Display NetWare Volume) commands if I do not have server operator privileges? 

      NetWare tape support - Questions
    1. What tape drives are supported? 
    2. What tape drives are not supported? 
    3. What tape drives will be certified by NetWare and Cheyenne? 
    4. ARCserve has the capability to use multiple tape drives concurrently to backup server data. Can I also use multiple AS/400 tape drives concurrently with NetWare tape support? 
    5. Why do I see 63903005 errors in the Product Activity Log ? 
    6. What Licensed Internal Code Log Entry IDs are used by NetWare tape support? 
    7. How can I prevent the tape from unloading when the AS/400 tape device is varied off? 
    8. Why does the error "QFPANW.NLM:021-AS/400 tape device 'x' NOT allocated, lost connection with OS/2 device driver VT400.SYS." occur when I try to allocate or deallocate a tape device? 

      SAV/RST - Questions
    1. How can I adjust the buffer sizes used for SAV/RST of NetWare data? 
    2. Why and how do I place my network server in a Restricted state.? 

       
      Pentium Integrated PC Server - Questions
    1. What steps are required to upgrade from a 6506 to a 6616 Pentium Integrated PC Server? 
    2. What steps are required when moving from a 6616 Pentium Integrated PC Server back to a 6506 Integrated PC Server? 
    3. How can I dump the memory of the Integrated PC Server if it is greater than 64MB? 

      General topics - Answers

    1. I'm trying to configure TCP/IP with Token-Ring and I need a LOAD ROUTE statement so my clients can connect to the server from another ring, but when I vary off and then vary on my server, the LOAD ROUTE statement is removed from the NETINFO.CFG file. Why is the ROUTE statement being removed?

    2. The NETINFO.CFG file is modified during every vary on of the NetWare server to ensure the correct LAN drivers are being loaded and the correct IPX network numbers are being used. This is done by removing all the statements related to LAN drivers and IPX circuits including the LOAD ROUTE statements. The items are then put back into the NETINFO.CFG file based on the information in the line description attached to the NWSD and the IPXCCT attached to the line description. There are two ways you can ensure ROUTE is loaded for the board and frame type needed.

      1. Add an IPX circuit of frame type *SNAP for the line where TCP/IP will be used using the following command. This example adds the IPX circuit to line NWSDNAME01 and specifies the IPX external network number as 12345678.
      2. ADDIPXCCT CCTNAME(SNAPCCT02) LIND(NWSDNAME01) IPXNETNBR(12345678) FRAMETYPE(*SNAP)
      3. If there is a problem creating an IPXCCT for *SNAP because you do not want any IPX traffic on the line, then add the following statement to the end of the AUTOEXEC.NCF file. This example is loading route on board 1.

      4. LOAD ROUTE NAME=QFP_TOK_1_TSP DEF GBR MBR RSP=AR TIME=20

    1. Can I run Intel LANDesk components of ManageWise 2.1 on my Integrated PC Server?

    2. No. The Intel LANDesk components in ManageWise 2.1 are not supported on an Integrated PC Server running NetWare for OS/2. Novell has issued a technical information document (2921269) regarding this matter including a statement from Intel. Serious problems have been encountered in this environment including server abends. 


    1. Where can I find more information regarding support of Novell Client32?

    2. The AS/400 Informational APAR II10455 contains more information regarding support of Novell Client32. 


    1. Should I vary off my NWSDs before powering down the system?

    2. Yes, it is recommended that the NWSDs for the NetWare servers be varied off before the system is powered down. This is especially necessary when the system is powered down with the *IMMED option since there is not enough time for the NetWare server(s) to come down correctly. Use the VRYCFG command or the WRKCFGSTS *NWS command to vary off your *NETWARE NWSDs before powering down the AS/400 system. 


    1. After my server varies on, how can I access it from RCONSOLE when it does not show up in the list?

    2. It usually takes a few minutes for IPX to advertise that the server is available.

      To access the server from RCONSOLE before it shows up in the list, bring up RCONSOLE, press the INSERT key and type in the IPX internal network number. This can be found on the AS/400 by using the WRKIPXD CL command and using option 5 to display the IPX description created for your server (if you used the INSNTWSVR command to install your NetWare server, the IPX description is the same as your NetWare server name).


    1. Why do I receive many "Loader cannot find public symbol" messages when I use the LOAD INETCFG command on RCONSOLE for an Integrated PC Server running NetWare for SAA?

    2. The NetWare for SAA: AS/400 edition contains some MPR 3.0 modules from Novell. Among these modules is ICM_SPX.NLM which exports some of the same symbols as CSLSTUB.NLM (which ships with NetWare). This problem occurs when a user installs NetWare for SAA: AS/400 Edition on Netware 4.11 (which does not come with ICM_SPX.NLM but does ship a newer CSLSTUB.NLM). The newer CSLSTUB.NLM and the ICM_SPX.NLM will conflict because they do export some of the same symbols but not all of the symbols that are exported by CSLSTUB.NLM.

      The resolution is to rename ICM_SPX.NLM on the server. This does not affect the NetWare for SAA: AS/400 edition IPX/SNA gateway. In the absence of ICM_SPX.NLM, CSLSTUB.NLM will load the functionality of all other modules is maintained.

      See Novell's Technical Information Document (TID) #2917279 for more details.


    1. What are some common commands to check my NetWare server?

    2. There are several commands you can use to check to see what state your local NetWare server on the AS/400 is in:

      1. WRKHDWRSC *CMN - displays the communication resources, including the Integrated PC Server (FSIOP) cards and the hardware status of the cards. Verify the status is operational.
      2. WRKCFGSTS *NWS - displays the NWSDs that you have created and displays the status. If status is VARY ON PENDING, your server is not active yet.
      3. WRKNWSSTS SVRTYPE(*NETWARE) - shows status of NetWare servers. If you do not have Enhanced Integration for Novell NetWare product, then only the local servers are shown. With Enhanced Integration for Novell NetWare product, both local and remote servers are displayed.
      4. WRKACTJOB SBS(QSYSWRK) - the name of the job for your local server is the name of the NetWare server. You can take option 5 and then option 10 to display the job log. Press F10 to see the detailed messages in the job log. If you did not specify a specific message queue on the MSGQ parameter of INSNTWSVR, the NetWare server console messages are also in this log.
      5. DSPMSG MSGQ(message-queue) - If you specified a message queue on the MSGQ parameter of the INSNTWSVR, you can display the NetWare server console log using this command. To check your message queue for your server, use the WRKNWSD command and select option 5 to display the details of your server. One of the values displayed is the 'Server message queue'. (If you did not specify a server message queue on the NWSD, all server messages and console activity will be logged to the monitor job's joblog.)
      6. SBMNWSCMD CMD(TIME) SERVER(server-name) SVRTYPE(*NETWARE) CMDTYPE(*OS2) - a command that submits a request to OS/2 running on the NetWare server. Press F10 to see the results if you are not displaying detailed messages. This verifies OS/2 is active.
      7. SBMNWSCMD CMD(VERSION) SERVER(server-name) SVRTYPE(*NETWARE) CMDTYPE(*LCLNTW) - a NetWare command is submitted via NetBios to the NetWare server. Press F10 to see the results if you are not displaying detailed messages. This verifies that the NetWare server is active.
      8. WRKIPXSTS option 3 - shows the IPX service information. The service name should be your NetWare server name. The type *FILESVR should show up after you have installed NetWare licenses on your NetWare server. The type *NTWENHINTG should show when the Enhanced Integration for NetWare NLM is loaded on the NetWare server.
      9. STRNTWCNN - if you have the Enhanced Integration for NetWare NLM loaded on the NetWare server you are trying to make connection to, you can use the STRNTWCNN command and fill in the parameters with the correct information to verify that you can make a connection to that specific server. This connection will be active until you sign off or do an ENDNTWCNN.

    1. What is the Enhanced Integration for NetWare NLM?

    2.  

       
       
       
       
       
       
       

      The Enhanced Integration for NetWare NLM runs on a NetWare 4.10, NetWare 4.11 or NetWare 3.12 server and provides NetWare services for AS/400 operators and users when OS/400 Enhanced Integration for Novell NetWare is installed. The NetWare 4.10 or NetWare 4.11 server can be an Integrated PC Server (FSIOP) or a PC-based server. The NetWare 3.12 server must be PC-based server.

      This NLM provides for simplification of user management tasks with user profile propagation, allows AS/400 users to access NetWare file systems, and supports printing to NetWare-managed printers. See the product description for more information on OS/400 Enhanced Integration for Novell NetWare.

      The name of the NetWare 4.1x Enhanced Integration for NetWare NLM is AS4NW410. (This NLM runs on either NetWare 4.10 or 4.11 servers.) The name of the NetWare 3.12 Enhanced Integration for NetWare NLM is AS4NW312. The latest NLMs can be downloaded from the download page.


    1. What is the difference between the configuration status and the NWS status?

    2.  

       

      The configuration status is displayed when you issue the command:

      WRKCFGSTS CFGTYPE(*NWS)

      The NWS status is displayed when you issue the command:

      WRKNWSSTS SVRTYPE(*NETWARE)

      A configuration status of Active indicates that the device drivers are loaded and operational.

      A NWS status of Active indicates that the OS/2 Administration Application has been loaded and is communicating with the monitor job for that server.


    1. When using SBMNWSCMD, why do I get CPFA448 (The user does not have the necessary console rights)?

    2.  

       
       
       
       
       

      To submit a command to the NetWare server:

      SBMNWSCMD SVRTYPE(*NETWARE) CMDTYPE(*NETWARE)

      the submitter of the command must have operator rights for the server.

      To grant operator rights:

      • For NetWare 4.1 servers, use the NetWare NWADMIN utility to find the system object for your NetWare server and then add the appropriate user objects to the operator list.
      • For NetWare 3.12 servers, use the NetWare SYSCON utility. Select Supervisor Options and then File Server Console Operators to view or change the list of operators.
      For a local Integrated PC Server, if you cannot obtain console rights to the server but you have AS/400 security officer (*SECOFR) authority, you can use the command:

      SBMNWSCMD SVRTYPE(*NETWARE) CMDTYPE(*LCLNTW)

      from the AS/400 that holds the Integrated PC Server's NetWare NWSD configuration object.


    1. Why can I not access the Enhanced Integration for NetWare NLM using Enhanced Integration functions on the AS/400?

    2. If you are trying to access the Enhanced Integration for NetWare NLM on a server, such as using the QNetWare file system, WRKNTWVOL or WRKNTWCNN commands, and the server is not responding, check the following:

      • Ensure the server is running. Use the command

      • WRKNWSSTS SVRTYPE(*NETWARE)

        to verify that the server reached the Active state.

      • Ensure the Enhanced Integration for NetWare NLM is installed and loaded. Use WRKIPXSTS and select 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 error CPFE00E from the WRKIPXSTS command in the previous step, you need to Start IPX using the STRIPX CL command. If you have not set up IPX on your system, see Chapter 14 - Configuring Enhanced Integration for NetWare in the Integrating AS/400 with Novell NetWare publication.

    1. What is the difference between a local (*LCL) and a remote (*RMT) server as shown on the WRKNWSSTS display?

    2. A local (*LCL) server represents an Integrated PC Server on the AS/400 system on which the WRKNWSSTS command was issued. A remote (*RMT) server may be either a PC server in the network or an Integrated PC Server on another AS/400 system in the network. If you do not have Enhanced Integration for Novell NetWare installed, then only the local servers are shown. With Enhanced Integration for Novell NetWare, both local and remote servers are displayed.


    1. Why does the configuration status of my server, which worked yesterday, remain at VARYON PENDING?
      • Did you install any new Novell fixes or patches? It may be that the fixes or patches were not correctly installed or configured, or that not all of the required fixes were installed together. If you made a backup of your server's drives prior to installing the Novell fixes and patches, try using the backup drives and see if the server works. This will isolate the problem to improper Novell fix or patch installation.
      • Check the Informational APAR for your specific release to determine that you have the most recent PTFs installed. If you find missing PTFs they should be applied and you should then vary off the NetWare server and try again.
      • Verify that the OS/2 operating system within the FSIOP is still active by submitting a command using the Submit NWS Command (SBMNWSCMD) AS/400 command. It should complete normally and display the command output in your joblog. The following example shows the OS/2 "time" command being submitted along with the expected output. If the SBMNWSCMD fails it indicates a problem with your server.

      • > SBMNWSCMD CMD(TIME) SERVER(MYSERVER) SVRTYPE(*NETWARE) CMDTYPE(*OS2)
        Current time is: 11:52:54.85
        Enter the new time:
        Command submitted to network server
        MYSERVER.
      • Verify that the NetWare operating system within the FSIOP is still active by submitting a command using the Submit NWS Command (SBMNWSCMD) AS/400 command. It should complete normally and display the command output in your joblog. The following example shows the NetWare "volumes" command being submitted along with the expected output on a V3R7 machine. Prior to V3R7 the value for CMDTYPE parameter is *NETWARE. If the SBMNWSCMD fails it indicates a problem with your server.

      • > SBMNWSCMD CMD(VOLUMES) SERVER(MYSERVER) SVRTYPE(*NETWARE) CMDTYPE(*LCLNTW)
        MYSERVER:VOLUMES
        Mounted Volumes Name Spaces Flags
        SYS DOS Cp Sa
        Command submitted to network server 
        MYSERVER.
      • Check that the SYS: volume is mounted. This is shown as output of the "volumes" command submitted in the previous item. If it is not mounted, then try to mount the volume using SBMNWSCMD to submit the NetWare command "mount sys".
      • Refer to Chapter 21, Analyzing Problems - Integration for NetWare, in the Integrating AS/400 with Novell NetWare publication.

    1. What differences are there between my PC server and the Integrated PC Server running on the AS/400?

    2. A major difference between NetWare running on an AS/400 Integrated PC Server and a server running on a PC is the underlying operating system. Most PC servers are started from a DOS environment but the Integrated PC Server is started from OS/2. Here are a few things to note about the OS/2 environment.

      • Memory is shared between OS/2 and NetWare. The initial configured values in the NET.CFG file give only enough memory for OS/2 to exist and run acceptably while giving NetWare as much memory as possible.
        • A single port Integrated PC Server will use approximately 11 megabytes of memory for OS/2 leaving the rest for NetWare.
        • A dual port Integrated PC Server will use approximately 13 megabytes of memory for OS/2 leaving the rest for NetWare.
        This means a dual port Integrated PC Server with 64 megabytes of memory installed will show about 51 megabytes of memory when running the MEMORY command from RCONSOLE.
      • CPU cycles are shared between OS/2 and NetWare. This could be a performance issue if you require a high speed application server. The initial configured values in the NET.CFG file give OS/2 no more than 20 percent of the CPU cycles and give NetWare the rest of the CPU cycles. Performance numbers show that this is comparable to a PC server with similar CPU and memory specifications.
      • Some applications do not seem to run the same using NetWare for OS/2 as they do on a DOS NetWare server. For example:
        • The BTRIEVE.NLM that is shipped on the NetWare 4.10 CD may cause hangs or cause other applications to abend when using NetWare for OS/2. To alleviate this problem we have shipped an alternative version of BTRIEVE.NLM that should replace the BTRIEVE.NLM shipped on the CD. If you run the NetWare modules command and see BTRIEVE.NLM version 6.10c being used you should replace it with the version located in F:\QFPNTWI\NW410\SYSTEM.

        • To copy a file from the F: drive to the SYS: volume, use an NLM called QFPPUTSY.NLM. For example:
          LOAD QFPPUTSY S=F:\QFPNTWI\NW410\SYSTEM\BTRIEVE.NLM D=SYS:SYSTEM
          When BTRIEVE.NLM is unloaded and reloaded, the version should be 6.10e.

          If you are using NetWare 4.11, BTRIEVE.NLM version 6.10f is included and works fine.

        • LDISCAN.NLM which is used with ManageWise has a problem with NetWare for OS/2. It will abend your server. Novell is currently investigating the problem and will hopefully have a fix for this problem soon.
      • A NetWare printer physically attached to the server does not work because the printer needs to have a printer driver installed for OS/2 before it can be installed as a NetWare printer. But, without the physically attached keyboard and display, installing the printer driver is very difficult.
      • Dial in support to the NetWare server via modem is unsupported. It may be possible with the FSIOP-3 and FSIOA cards, but has not been tested.

    Back to the top.

      Install - Answers
    1. Why does the configuration status remain at VARYON PENDING after installing NetWare on an Integrated PC Server (FSIOP) and then varying it on for the first time?
      • When a new *NETWARE NWSD is varied on for the first time it will run the Novell NetWare install NLM to load NetWare onto the SYS: volume. The process of running this install process and setting up the SYS: volume may take up to 30 minutes. Once this step is completed the status of the NWSD will change to ACTIVE. So be sure and allow time for this process to complete.
      • Check the Informational APAR for your specific release to determine that you have the most recent PTFs installed. If you find missing PTFs they should be applied and you should then vary off the NetWare server and try the install again.
      • Verify that the OS/2 operating system within the FSIOP is still active by submitting a command using the Submit NWS Command (SBMNWSCMD) AS/400 command. It should complete normally and display the command output in your joblog. The following example shows the OS/2 "time" command being submitted along with the expected output. If the SBMNWSCMD fails it indicates a problem with your server.
      • > SBMNWSCMD CMD(TIME) SERVER(MYSERVER)SVRTYPE(*NETWARE) CMDTYPE(*OS2)
        Current time is: 11:52:54.85
        Enter the new time:
        Command submitted to network server MYSERVER.
      • Verify that the NetWare operating system within the FSIOP is still active by submitting a command using the Submit NWS Command (SBMNWSCMD) AS/400 command. It should complete normally and display the command output in your joblog. The following example shows the NetWare "volumes" command being submitted along with the expected output on a V3R7 machine. Prior to V3R7 the value for CMDTYPE parameter is *NETWARE. If the SBMNWSCMD fails it indicates a problem with your server.

      • > SBMNWSCMD CMD(VOLUMES) SERVER(MYSERVER) SVRTYPE(*NETWARE) CMDTYPE(*LCLNTW)
        MYSERVER:VOLUMES
        Mounted Volumes Name Spaces Flags
        SYS DOS Cp Sa
        Command submitted to network server MYSERVER
      • Check that the SYS: volume is mounted. This is shown as output of the "volumes" command submitted in the previous item. If it is not mounted, then try to mount the volume using SBMNWSCMD to submit the NetWare command "mount sys".
      • Check the contents of the NetWare install error file. This file is on drive E:\ of the FSIOP and has the name "E". To view the file use SBMNWSCMD to submit the OS/2 command "type e:\e". The contents of the file will be displayed in the joblog. It should contain the following text, which is normal. Any other error messages indicate a problem with the NetWare install process.

      • The system volume (SYS:) either is not 
        mounted or does not exist.(INSTALL-4.1-269) Command submitted to network server
        MYSERVER.
      • When you are varying on a new NWSD with a SYS: volume that was previously installed and functional, the NetWare install may require user interaction via RCONSOLE in order to complete. This would normally occur if you had a functional NetWare server and for some reason were forced to delete and re-create the NWSD. In this case the NetWare install process will still run and will set up the SYS: volume. However, if the SYS: volume contains fixes to certain NetWare NLMs which are newer than those supplied with the NetWare CD-ROM, then the install may prompt the user about overwriting newer files. In this case you should try to connect to your server using RCONSOLE and if necessary answer the prompt. If you can not get RCONSOLE working you may need to submit the NetWare command "sys:etc\initsys.ncf" to get it working.
      • Refer to Chapter 21, Analyzing Problems - Integration for NetWare, in the Integrating AS/400 with Novell NetWare publication.

    1. I need to re-create my NWSD. What steps should I follow?

    2. In some cases it might be necessary to re-create an NWSD (for example, to repair a damaged E: drive). However, since the NWSD maintains complex relationships with other related system objects, it is not advisable to simply delete and re-create the NWSD. Instead, follow these steps:

      • Delete the NWSD using the DLTNWSD NWSD(nwsd-name) command.
      • Delete the following related objects, if they exist:
        • IPX Description. Use the command WRKIPXD IPXD(nwsd-name) to determine if an IPX Description exists that is associated with the specified NWSD.
        • IPX Circuits. Use the command WRKIPXCCT to determine if there are any IPX circuits associated with the NWSD.
        • Line Description. Use the command WRKLIND LIND(nwsd-name*) to locate any line descriptions associated with the NWSD specified.
      • Do not delete the SYS: and user volumes.
      • Run the INSNTWSVR command again to create the NWSD and related objects and specify a different server storage space name for the NWSSTG keyword -- this will cause a new, unique SYS: volume to be created -- with a minimum size of 100 (megabytes).
      • Vary on the NWSD and wait for the server to come up.
      • Vary off the NWSD.
      • Use the command WRKNWSSTG NWSSTG(*ALL) NWSD(nwsd-name) to display the network server storage spaces currently linked to the NWSD. Use option 11 (Remove link) to unlink the new SYS: volume and then delete it using option 4 (Delete). Use option 10 (Add link) to link the original SYS: volume to the NWSD.
      • Vary on the NWSD.
      These steps will result in the NetWare install occurring from the F: drive to the new SYS: volume without changing the original SYS: volume (and therefore any files that had been updated on the original SYS: volume remain intact).

      An alternative to this process which does not include re-installing NetWare and running the INSNTWSVR command again is:

      • Delete the NWSD using the DLTNWSD NWSD(nwsd-name) command (but retain all other objects).
      • Create a new NWSD of the same name using the CRTNWSD NWSD(nwsd-name) command.
      • Create a new SYS: volume using the CRTNWSSTG NWSSTG(diff-name) command and link it to the NWSD using the ADDNWSSTGL command.
      • Vary on the NWSD and wait for the server to come up.
      • Vary off the NWSD.
      • Use the command WRKNWSSTG NWSSTG(*ALL) NWSD(nwsd-name) to display the network server storage spaces currently linked to the NWSD. Use option 11 (Remove link) to unlink the new SYS: volume and then delete it using option 4 (Delete). Use option 10 (Add link) to link the original SYS: volume (the default name is the same as the NWSD name) to the NWSD.
      • Vary on the NWSD.

    1. How do I upgrade a NetWare 4.10 server to 4.11?

    2. If you currently have NetWare 4.10 installed on your Integrated PC Server and wish to upgrade to NetWare 4.11, you need to follow the procedure documented in the informational APAR II09535 for V3R2 and II09667 for V3R7. The Service and Support page provides access to these and other informational APARs.

      If you do not currently have NetWare 4.10 installed on your Integrated PC Server, you can follow the documented install process except use the NetWare 4.11 CDROM instead of the NetWare 4.10 CDROM.


    1. Why do I get invalid path error when installing NetWare 4.11 on V3R2?

    2. First ensure you are referencing the NetWare 4.11 CD or IntranetWare CD or CDROM image.

      If the error during the workstation install is :
      'xcopy D:\NW410\BOOT\NATIVE\SERVER.EXE c:\QFPTMP'
      with error 'Invalid path' followed by error
      FPI1420 'CDROM image does not match language specified, or path to CDROM image is invalid'
      then you do not have the correct level of PTFs that support NetWare 4.11.

      View the QFP.LOG file and error

       
      QFPWSP2 QFP_READERROR C:\QFPTMP\qfpntwcp.err, rc=4
      should also be contained in the file.

      See informational APAR II09535 for V3R2 for the list of PTFs needed for NetWare 4.11.


    1. Why do I get CPDA488 with reason code 2 when installing NetWare 4.11 on V3R7?

    2. If the first line in the QFPILOG file has the directory 'NW410' after the path that you entered for NTWSRCDIR, you do not have the correct level of PTFs that support NetWare 4.11. Enter WRKSPLF and then option 5 to view the QFPILOG file. See informational APAR II09667 for V3R7 for the list of PTFs needed for NetWare 4.11.

      Ensure you have the NetWare 4.11 CD or the IntranetWare CD in the CDROM drive, or you are specifying a path to a NetWare 4.11 CDROM image.

      You can verify the path name to the CDROM by using the WRKLNK command. For example, if the NetWare 4.11 CD is in the CDROM device on the AS/400, enter WRKLNK OBJ('/QOPT'), then use option 5 to display the volume name. If the volume name is NW411, then for the parameter NTWSRCDIR on the INSNTWSVR command, you would enter '/QOPT/NW411'.


    1. When attempting to Copy NetWare Files as described in the Integrating AS/400 with Novell NetWare V3R7 book, the PC running RCONSOLE seems to hang during the copy. Is there something I can do about this?

    2. If the RCONSOLE session hangs while doing the copy files option, you might be able to restart the operation from where the copy hang occurred. Try the following:

      1. Press Alt+F2 and exit the RCONSOLE session.
      2. Restart RCONSOLE to your NetWare server.
      3. When you get access to the console screen, your server will have a pink screen displayed. Press Enter to acknowledge the error.
      4. Choose Retry copying file from the popup window.
      5. Copying of the files should continue.
      When you are done copying files, remember to install the minimum OS, NLM, and File Updates from http://support.novell.com/misc/patlst.htm. A fix to the problem that caused this to happen may already be available.

    1. How long should I expect the INSNTWSVR command to run when copying the CD to the server storage space of a RISC system?

    2. The time it takes to copy the CD to the F: drive is dependent on the AS/400 model being used and the NetWare version being copied. For NetWare 4.10, approximately 40 megabytes is copied from the CD to the F: drive. For NetWare 4.11, approximately 90 megabytes is copied from the CD to the F: drive. The following table should give an idea of how much time to expect when running INSNTWSVR NWSD(*CPYONLY).

       
      NetWare version  Advanced Entry Model 184 Advanced System Model 500 
      NetWare 4.10  40 minutes  30 minutes 
      NetWare 4.11  1 hour 40 minutes  1 hour 17 minutes 
    Back to the top.

      User enrollment - Answers

      Setup

    1. What steps should I perform before I start user enrollment?

    2. Good question. :-) Let's go through it step by step:

      1. Install Enhanced Integration for NetWare on your AS/400. Refer to the /netware/Integrating AS/400 with Novell NetWare publication for more information.
      2. Create a user named QNETWARE on each of your 3.12 servers and NDS trees in which you want to enroll users. You must give QNETWARE enough rights to be able to create and delete users. Each QNETWARE user can have the same or different password. Having the same password is easier to manage, but different passwords can give you more security options. You should verify that this works by logging into the server as QNETWARE and creating and deleting a test user manually.
      3. Next we have to set the QNETWARE user profile password on the AS/400 to have the same password as the QNETWARE user on the NetWare server. Recall that when Enhanced NetWare was installed on your AS/400 system, a QNETWARE user profile was created with a password of *NONE. If all of your QNETWARE users on the NetWare servers have the same password, you can issue this command:

      4. CHGUSRPRF USRPRF(QNETWARE) PASSWORD(your_password)

        to give the AS/400 QNETWARE user profile the same password as your NetWare QNETWARE user. If you use different passwords, you will have to use authentication entries which will be explained later. If you find that authentication entries are necessary, you can just leave the AS/400 QNETWARE user profile password as *NONE and the password in the authentication entry will be used instead.

      5. If you have only 3.12 servers and the same QNETWARE password is used on every server, there is nothing more to do. If you have NDS trees, you must set in which context the QNETWARE user is in the tree. There are two ways to do this: you can either propagate the QNETWARE user to each tree, or use authentication entries. To propagate the QNETWARE user, use CHGNWSUSRA and specify each tree and context, and optionally a default server under NDS tree list. If you have both NDS trees and 3.12 servers, you can use the NetWare 3.12 server list option in CHGNWSUSRA to specify your servers, but this is not necessary for successful user enrollment.
      6. Enroll a user on one of your servers with the CHGNWSUSRA command. Everything should work smoothly at this point. If not, review the above steps and make sure each has been done completely. If there are still problems, review the rest of this FAQ to see if the problem is referenced elsewhere.

    1. What are authentication entries and how are they used?

    2. Glad you asked! Authentication entries allow a single AS/400 user profile to log into multiple servers with different passwords without specifying a password every time. They must be used if you have multiple trees or servers with different QNETWARE passwords, but can be used even if the passwords are the same. An authentication entry for the QNETWARE user profile should be created for every tree or server you plan to propagate to. For example, to create an authentication entry on an NDS tree for the QNETWARE user profile:

      ADDNTWAUTE SVRTYPE(*NDS) NDSTREE(tree_name) USRPRF(QNETWARE) NDSCTX(context) NTWUSER (QNETWARE) PASSWORD(password)

      or on a 3.12 server:

      ADDNTWAUTE SVRTYPE(*NETWARE3) SERVER (server_name) USRPRF(QNETWARE) NTWUSER(QNETWARE) PASSWORD(password)

      This is all that must be done to allow propagation to proceed. Note that for successful propagation, you must have both USRPRF and NTWUSER set to QNETWARE. That is, the user on both the AS/400 and on the NetWare server must be named QNETWARE. During enrollment, the AS/400 logs into the specified tree or server with the QNETWARE user, and first checks the information in the authentication entry. If there is no authentication entry, it then checks the password for the QNETWARE user profile itself. For this reason, the AS/400 QNETWARE user profile can have a password of *NONE if authentication entries are used.


       
      How can I determine if the users are being propagated properly; where are the error codes displayed?

      Use the WRKNWSENR command to display the Work with NWS User Enrollment screen. This lists the users that are enrolled in your various trees and servers. By default it lists each user, and you can display the groups that each user belongs to by pressing F10. This screen is very helpful when determining the various problems that arise, and any error codes are displayed here.


       
      I'm trying to propagate users for the first time, and I get a 3401 error. Why?

      This is occurs when the AS/400 is unable to find the QNETWARE user on the server or tree. You should check that:

      • The 3.12 server is running, or there is a working server in the NDS tree.
      • There is a QNETWARE user created on the 3.12 server or the NDS tree.
      • If you are using NDS trees, you have specified the correct context.
      • The AS/400 user profile is not disabled.

       
      I'm trying to propagate users for the first time, and I get a 6004 error. Why?

      This is caused when the AS/400 has found a QNETWARE user, but cannot login to the server or tree with it. Check that:

      • You didn't misspell the name of the server or the tree when doing a CHGNWSUSRA..
      • The same password is specified for the QNETWARE user profile on the AS/400 as on the NetWare server or NDS tree.
      • The password on the NetWare server or NDS tree is not disabled.

       
      I'm trying to propagate users for the first time, and I get a 245 error. Why?

      This is caused when a valid connection is found, but enrollment is not completed. Make sure that the QNETWARE user on the NetWare server has authority to create users. This usually means in having a security equivalence of SUPERVISOR in 3.12 servers, or of ADMIN in NDS trees.


       
      I'm trying to propagate users for the first time, and I get a 6000 error. Why?

      This is probably due to either mistyping a NDS tree name, or somehow not being able to connect to the specified tree. Verify that the NDS tree name is specified correctly in the authentication entry.


       
      I'm trying to propagate users for the first time, and I get a 601 error. Why?

      Verify that the user context for the NDS tree is correct.


       
      I'm trying to propagate users for the first time, and I get a 613 error.

      This is usually caused by a problem with the Profile Object that is specified with the CHGNWSUSRA command. Verify that the name is spelled correctly, and that the object exists in NetWare.


       
      User and group propagation

      Why don't the user profiles on the AS/400 change when I make changes on the NetWare server?

      The AS/400 user enrollment is often referred to as synchronization, which can be misleading. Currently the user enrollment is designed for AS/400 administrators to do NetWare administration from their console. Because of this all calls are one-way only: from the AS/400 to the NetWare server. Any changes made on the NetWare server are not propagated to the AS/400.


    1. Can I still create users with Novell NetWare while enrolling users from the AS/400?

    2. Yes. But since Enhanced Integration for NetWare is designed from the AS/400 side, there are some differences. For example, a user is free to change his or her password via NetWare, but the password will then be out-of-sync with the password on the AS/400 -- the AS/400 still has the old password. This does not cause any problems, though -- if the AS/400 password is changed, it is propagated to the NetWare server, and this becomes the new password on both sides, no matter what the password previously was on the NetWare server. Just remember that the AS/400 is not aware of any user or group changes that occur on the NetWare server.


      In that case, can I have groups on the NetWare server that are not on the AS/400?

      Yes. If you create a user or a group with the NetWare SYSCON or NWADMIN commands, the AS/400 will not be aware of them. You can do anything you could normally do from NetWare with these users, but none of the enhanced function on the AS/400 will be available to them. If a user is created on the AS/400 with the same name as a user on the NetWare server, and is then enrolled on that server, a merge is done of the two users. The user will be a member of the groups that both servers specify, but if any conflicts arise (different passwords, text, etc.) the AS/400 data will automatically be used. If that user is then removed from the AS/400 enrollment, the user will still be there because it was created from the NetWare server, not the AS/400.


       
      Group-specific propagation

      I enrolled a group with several users, but the users were not created on the NetWare server. What could be wrong?

      You probably enrolled the group without specifying PRPGRPMBR(*ALL) -- that's Propagate Group Members -- on the CHGNWSUSRA command. The default is to not propagate any of the users when the group is enrolled.


       
      I enrolled a group and when I used WRKNWSENR, it gave a 6011 error. Why?

      6011 means invalid password. This usually occurs when the CHGNWSUSRA command is issued for a group profile without specifying PRFTYPE(*GROUP). The default is *USER, and so when you propagate your group without changing the default, you tell the AS/400 that it is a user.


       
      How can I display users within groups on the WRKNWSENR display?

      Issue the WRKNWSENR command and specify PRFTYPE(*GROUP).


       
      Miscellaneous enrollment topics

      I just removed a server, and am now trying to delete all the users that were on the server, but they are now all at *DLTFAIL. How can I get rid of all these errors, because the server's not really even there any more?

      Probably the best solution to this is to stop enrollment from the server before you take it down. If this is not viable, your next option is to use WRKNWSENR and do an option '4' next to every user or group marked as *UPDFAIL. This will stop the AS/400 from propagating the user or group, but will not cause any changes on the server.


       
      I've been doing enrollment for awhile now, and all of a sudden I'm getting 245 errors everywhere. Why?

      This means that we have a valid connection, but can no longer do propagation. This usually means that something happened to the QNETWARE user on the NetWare server. The most likely cause is that the password expired, in which case you can just reset the password on the NetWare server. If for some reason the QNETWARE user has been deleted, just recreating the user will not quite be enough. After you create a new user and set it up as described above, you should use the WRKNTWCNN command to remove the current connection to the client, and then let the AS/400 automatically start a new connection to the new QNETWARE user.


       
      When I select option 16 on the WRKNWSENR display to look at error details, why are replacement symbols(&1, &2, etc.) displayed instead of the actual values?

      This is how it is supposed to work. To look at the error message with all the replacement text, you must look in the QNETWARE job log. QNETWARE, besides being the name of a user profile, is a batch job that runs in the QSYSWRK subsystem that sends the propagation requests to the server. To look at the job, type WRKJOB JOB(QNETWARE), select the specific job with option '1', then look at the job log with option '10'. At this point you should see >> CALL QFPNTWE/QFPANTWJ. Just press F10, and this will show you the detailed job log. Press F1 on a specific message and the error message from the WRKNWSENR screen will be displayed, but with the replacement text included.


       
      What is QRETSVRSEC and how can it be changed?

      If you run DSPSYSVAL SYSVAL(QRETSVRSEC), this will display the "Retain server security data" system value, or QRETSVRSEC. This value determines whether passwords are stored in the system or not. Concerning user enrollment, it means that if it is set to 0, passwords will not be saved on the system, and whenever a propagation change is made from the AS/400, it will not go through until the user has logged in, or the password has been reset. Setting the value (with CHGSYSVAL SYSVAL(QRETSVRSEC) ) will actively remove all passwords on the system, so changing it from 1 to 0 and back to 1 will result in all the passwords being removed and propagation ending until users' passwords are re-entered.
       
       


    Back to the top.

      Monitor job - Answers
    1. Why is the message "Basic functions available for network server" sent in the monitor job?

    2. The NetWare monitor job for an Integrated PC Server on may provide either basic functions or enhanced functions.

      Basic functions will be provided by the monitor job when:

      • Enhanced Integration for NetWare (option 25) is not installed.
      • an Integrated PC Server is varied on for the first time after installing NetWare and Enhanced Integration for NetWare (option 25) is installed on the system. In this case we know that the Enhanced Integration for NetWare NLM is not yet installed on the server so the monitor job makes no attempt to contact the NLM. When the Integrated PC Server is varied on again, the monitor job will attempt to contact the Enhanced Integration for NetWare NLM. If the NLM has not be loaded, the attempt to contact the NLM will fail and basic functions will be provided.
      • a communication failure occurs after having contacted the Enhanced Integration for NetWare NLM.
      Enhanced functions will be provided by the monitor job when:
      • Enhanced Integration for NetWare (option 25) is installed the Enhanced Integration for NetWare NLM is loaded and has been successfully contacted by the monitor job.

    1. How can I cause the monitor job to contact the Enhanced Integration for NetWare NLM again?

    2.  

       
       
       

      You can restart the monitor job which will cause it to attempt to recontact the NLM. This is useful if the NLM was loaded after the monitor job had already failed in its attempt to contact it or if a communication failure occurred that resulted in a loss of contact with the NLM. To restart the monitor job, issue the command WRKNWSSTS SVRTYPE(*NETWARE) and select option 14 (Restart server). This will cause the monitor job for the *NETWARE server to be restarted. If there is already a monitor job that is running, it will be ended by the new job.


    1. Why can't I find the joblog for a monitor job that ended previously?

    2.  

       
       
       

      The monitor job is submitted using the QGPL/QBATCH job description. This job description's default message logging level is LOG(4 00 *NONE) which will not produce a joblog. Change the QGPL/QBATCH job description using the command:

      CHGJOBD JOBD(QGPL/QBATCH) LOG(4 00 *SECLVL)

      This will cause the joblog for the monitor job to be retained after the job ends.


    1. When viewing the monitor joblog or message queue for the running Integrated PC Server, why are the NetWare console messages often repeated?

    2.  

       
       
       

      When there is an update to the Rconsole screen, NetWare notifies an OS/2 process running on the Integrated PC Server. This process will in turn report the information to the monitor job. Since it cannot be determined how much of the Rconsole screen has changed, the entire screen image is processed.

      Currently, a message is sent containing the server name only to separate each screen of Rconsole data. In a future release, this message will be sent with the server name and a row of asterisks (instead of blanks) to help further differentiate each Rconsole screen that is processed.


    Back to the top.

       
      QNetWare file system - Answers
    1. What is the QNetWare file system?

    2.  

       
       
       

      The QNetWare file system provides access to NetWare files, directories, and NetWare Directory Services (NDS) objects through the AS/400 integrated file system (IFS).

    3. How can the QNetWare file system be used?

    4.  

       
       
       

      You can use the QNetWare file system to:

      • Access data stored on a local or remote Integrated PC server (FSIOP) running Novell NetWare 4.1x.
      • Access data stored on PC servers running Novell NetWare 3.12 or 4.1x. You can access data on these servers and Integrated PC Servers simultaneously by using AS/400 authentication entries.
      • Access NetWare Directory Services (NDS) objects.
      • Dynamically mount NetWare file systems over any local mountable file system. Flexible mount options, similar to the MAP command, simplify and speed access to NetWare files.
      • Store data in stream files.
    5. Can I write applications to access the QNetWare file system?

    6.  

       
       
       

      Of course! In addition to the Integrated File System commands and menus, OS/400 provides API programs that enable ILE C/400 programs to perform functions on files and directories in all file systems, including the QNetWare file system.

      The Integrated File System API support is useful for integrating the AS/400 database with Enhanced Integration for NetWare data.

      Be aware that there are some additional considerations to using the Integrated File System API programs to access the QNetWare file system compared to other file systems. To write ILE C/400 programs to use the QNetWare file system see the AS/400 System API Reference V3R7, SC41-4801-01, for a detailed description of each API program. See AS/400 ILE Concepts V3R7, SC41-4606-01, ILE C/400 V3R7.0 Programmer's Guide, SC09-2069-01, and ILE C/400 V3R7.0 Programmer's Reference, SC09-2070-01, for more information about ILE and ILE C/400.

    7. What should I do if the server does not show up under /QNetWare when using the WRKLNK command?
      • Verify that the Enhanced Integration for NetWare NLM is loaded on the server.
      • Verify that the AS/400 system recognizes the NLM. Use the WRKIPXSTS command and select option 3. There should be an entry that specifies *NTWEHNINTG for the server.

      •  

         
         
         

        For improved performance, this list of servers is updated periodically rather than dynamically. To force the entire list of servers to be updated, enter the command:

        CALL QFPNTWE/QFPZCTL PARM(*UPDSRVL)

    8. What should I do if the next level of server volumes is not displayed when using the WRKLNK command?

    9.  

       
       
       
       
       

      Verify that the user either has a connection started to the NetWare server or has an authentication entry defined for the NetWare server or NDS tree.

    10. What should I do if I am not authorized to a file or directory?

    11.  

       
       
       

      For NetWare 3.12, verify the user exists in the NetWare Bindery for the server.

      For NetWare 4.1x, verify 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.

    12. What should I do if I can't make a directory using the MKDIR command?

    13.  

       
       
       

      Try one of the following:

      • Specify no *PUBLIC authority on the MKDIR command as shown?

      •  

         
         
         

        MKDIR DIR(dir-name) DTAAUT(*NONE) OBJAUT(*NONE)

      • Verify the NetWare group EVERYONE is created in your NDS tree and that your job or system NDS context is set to the context that contains EVERYONE.
    14. What should I do if I can't move a file using the MOV command?

    15.  

       
       
       

      For NetWare 3.12, verify 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, verify 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.

    16. How can I check the NDS context?

    17.  

       
       
       

      Users may want to check the NDS context if they experience problems such as authorizing other users to files or directories or moving a file using the MOV command. To display or change the current context:

      • for a user...

      • use the DSPNWSUSRA or CHGNWSUSRA commands
      • for a job...

      • use the DSPNDSCTX or CHGNDSCTX commands
      • for the system...

      • use the DSPNWSA or CHGNWSA commands

    Back to the top.

       
      Connections - Answers
    1. Why do I get message FPE0232 (User not connected to server) when using NetWare commands from the AS/400?

    2. Usually the problem is because there is not an authentication entry in the user profile for the server or NDS tree. See previous messages, and if the diagnostic error is FPE0215, then an authentication entry does not exist. You must have an authentication entry so the AS/400 can automatically authenticate to a NetWare server. You can manually authenticate to a NetWare server or NDS tree by using the STRNTWCNN command, but that connection is only valid for that session until you sign off.

      Authentication entries can get added a couple of ways. One is by using AS/400 user enrollment. This is explained in Chapter 20 - Managing User Enrollment in the Integrating AS/400 with Novell NetWare publication. Another way is to manually add NetWare authentication entries using the WRKNTWAUTE command and selecting option 1. Once you have authentication entries, the AS/400 will automatically authenticate to a NetWare 3.12 server or an NDS tree.


    1. Why do I get message FPE0234 (Password *STRNTWCNN not allowed) when I have an authentication entry set up?

    2. Check the QRETSVRSEC system value to see if it is set to 0 (Do not Retain data). Use the command WRKSYSVAL SYSVAL(QRETSVRSEC) and then option 5 to display the system value. If the value is 0, then the passwords on the authentication entries cannot be saved and they are set to *STRNTWCNN. If you wish to retain the passwords, you need to change the QRETSVRSEC system value to 1. Use the command WRKSYSVAL SYSVAL(QRETSVRSEC) and then option 2 to change the value.

      After the value has been changed, the authentication entries can be updated with the correct password using the WRKNTWAUTE CL command.


    1. Why do I get message FPE0215 (Could not find authentication entry)?

    2.  

       
       
       

      Usually this error is a result of not having an authentication for the server or tree that is specified in the FPE0215 error message. You must have an authentication entry so the AS/400 can automatically authenticate to a NetWare server. You can manually authenticate to a NetWare server or NDS tree by using the STRNTWCNN command, but that connection is only valid for that session until you sign off.

      Authentication entries can get added a couple of ways. One is by using AS/400 user enrollment. This is explained in Chapter 20 - Managing User Enrollment in the Integrating AS/400 with Novell NetWare publication. Another way is to manually add NetWare authentication entries using the WRKNTWAUTE command and using option 1. Once the authentication entries are created, the AS/400 will automatically authenticate to a NetWare 3.12 server or an NDS tree.
       
       


    Back to the top.

       
      Volumes - Answers
    1. What is the *IOSYSCFG authority that I need before using any of the volume management commands?

    2. *IOSYSCFG is an AS/400 special authority that is required before you can use configuration-related AS/400 commands like those for NetWare volume management. This authority is granted by a user profile with *SECADM authority using the CHGUSRPRF command and specifying SPCAUT(*IOSYSCFG)

    3. Why do the CRTNTWVOL and CHGNTWVOL CL commands receive an "invalid device" error for a storage space, even though that storage space was just created and linked to the server?

    4. The usual reason is because the storage space that was created does not have a NetWare partition on it. If the Enhanced Integration for NetWare NLM is running on the server -AND- the monitor job has made contact with the NLM, the storage space will be automatically partitioned (usually this occurs within 15 minutes after the NWSD is varied on). See the related question on the monitor job and contacting the Enhanced Integration for NetWare NLM.

      If you do not have the Enhanced Integration for NetWare NLM running on your Integrated PC Server, then you need to use the RCONSOLE utility LOAD INSTALL and select "Disk options" to create a NetWare disk partition. You could do this even if the Enhanced Integration for NetWare NLM is running on your server.

      Once the disk has a NetWare partition on it, you can then run the CRTNTWVOL or CHGNTWVOL CL commands and specify the storage space name or device number. 

    5. When creating or changing a volume, why does message FPE023F (Server operator privileges required) result?

    6. You must have operator rights for the server in order to create or change a volume.

      To grant operator rights:

      • For NetWare 4.1 servers, use the NetWare NWADMIN utility to find the server object for your NetWare server and then add the appropriate user objects to the operator list.
      • For NetWare 3.12 servers, use the NetWare SYSCON utility. Select Supervisor Options and then File Server Console Operators to view or change the list of operators.
    7. Why can I still use the WRKNTWVOL (Work with NetWare volumes) and DSPNTWVOL (Display NetWare Volume) commands if I do not have server operator privileges?

    8. The WRKNTWVOL (Work with NetWare volumes) and DSPNTWVOL (Display NetWare Volume) commands are passive volume operations while the CRTNTWVOL (Create NetWare Volume), CHGNTWVOL (Change NetWare Volume) and DLTNTWVOL (Delete NetWare Volume) commands are considered active volume operations.

      The WRKNTWVOL and DSPNTWVOL commands display information about existing volumes. You must have operator rights to the server before you can create, change or delete volume(s).

      To grant operator rights:

      • For NetWare 4.1 servers, use the NetWare NWADMIN utility to find the server object for your NetWare server and then add the appropriate user objects to the operator list.
      • For NetWare 3.12 servers, use the NetWare SYSCON utility. Select Supervisor Options and then File Server Console Operators to view or change the list of operators.

    Back to the top.

       
      NetWare tape support - Answers
    1. What tape drives are supported?

    2.  

       

      The following tape drives have been tested extensively:

      • 6380 (1/4" cartridge)
      • 6390 (8mm cartridge)
      • 3590 (1/2" cartridge)
      • 3570 (1/2" cartridge)
      Other tape drives (except those identified as not supported in the following question and answer) are supported but have not been tested extensively.

    1. What tape drives are not supported?
      • 1/2-inch reel tape drives (2440, 3422, 3430, 9347, 9348)
      • 1/2-inch cartridge tape drives (3480/3490/3490e)

    1. What tape drives will be certified by Novell and Cheyenne Software, Inc.?
      • 6380 (1/4" cartridge device)
      • 6390 (8mm cartridge device)
      • 3590 (1/2" cartridge device)

    1. ARCserve has the capability to use multiple tape drives concurrently to backup server data. Can I also use multiple AS/400 tape drives concurrently with NetWare tape support?

    2.  

       
       
       

      No, this is currently not supported. You can only allocate one AS/400 tape drive to use from the Integrated PC Server at a time.


    1. Why do I see 63903005 errors in the Product Activity Log ?

    2.  

       

      These are "blank tape" or "BOT encountered" errors. They are caused by SBACKUP and ARCserve positioning the tape. They can be ignored.


    1. What Licensed Internal Code Log Entry IDs are used by NetWare tape support?
    2. Major Code Minor Code Meaning
      2700  0000  Exception in router. 
      2700  0010  IPCF connection failed to 
      open to IOP entity. 
      2700  0100  Too many tape devices 
      detected on AS/400. 
      2700  0101  Invalid tape device state. 

    1. How can I prevent the tape from unloading when the AS/400 tape device is varied off?

    2.  

       

      Use the following AS/400 command to prevent the tape device from unloading when the device is varied off:

      • CHGDEVTAP DEV(tapedev) UNLOAD(*NO)
    3. Why does the error "QFPANW.NLM:021-AS/400 tape device 'x' NOT allocated, lost connection with OS/2 device driver VT400.SYS." occur when I try to allocate or deallocate a tape device?

    4.  

       

      This error message will occur if you are using a 1/2" cartridge tape drive (ie. 3590, 3570) with NetWare tape support for OS/400, and load the tape immediately before you ALLOCATE or DEALLOCATE the drive from the NetWare console (RCONSOLE).

      This error will cause the tape drive to hang and it won't be useable from AS/400 or NetWare. To recover the tape drive you must vary off the NetWare server where you attempted to ALLOCATE or DEALLOCATE the drive.

      To assure that this error does not occur, follow these steps when you are ready to ALLOCATE the tape drive:

      • Vary on the tape from the AS/400
      • Vary off the tape drive from the AS/400
      • DO NOT load the tape drive with a tape.
      • ALLOCATE the drive from NetWare
      • Now load the tape in the tape drive.

    Back to the top.

       
      SAV/RST - Answers
    1. How can I adjust the buffer sizes used for SAV/RST of NetWare data?

    2.  

       
       
       

      The buffers allocated on a NetWare server while saving or restoring data using AS.400 SAV or RST commands can be adjusted in one of two ways:

      1. When loading the AS4NW410 or AS4NW312 NLM, the SRBUFNUM and SRBUFLEN switches can be used to specify the number of buffers to be used and the length of each buffer.

      2.  

         
         
         

        For example, on a NetWare 4.10 server, to use 4 buffers, each 512K in length, type:

        • LOAD SYS:AS4NW/AS4NW410 / 
        SRBUFNUM= 4 /SRBUFLEN=524288
      3. To accomplish the same effect after the AS4NW410 or AS4NW312 NLM has been loaded, type:
        • AS4NW /SRBUFNUM=4
        • AS4NW /SRBUFLEN=524288
    3. Why and how do I place my network server in a Restricted state?

    4.  

       
       
       

      The purpose of placing a local network server in a Restricted state is to limit access of the QNetWare file system during a save or restore operation. Only local connections will be granted while the network server is in this state.

      To place your network server in a Restricted state you must end the monitor job associated with the NWSD. This requires that Enhanced Integration for NetWare (option 25) is installed and the Enhanced Integration for NetWare NLM is running on the server. The monitor job must be in successful communication with the NLM in order to enter Restricted state. After ending the monitor job, display the network server status:

          WRKNWSSTS SVRTYPE(*NETWARE)
      
      
      
      to confirm that the server is in a Restricted state. You can also display messages in QSYSOPR and the monitor job log to determine if any problems occurred while placing the server in a Restricted state.
      To place a *NETWARE network server in a Restricted state, you cannot end the monitor job by ending the QSYSWRK subsystem. Placing the server in a Restricted state requires the use of IPX communications which also runs in the QSYSWRK subsystem. End the monitor job only to place the server in a Restricted state. 

    Back to the top.

       
      Pentium Integrated PC Server - Answers
    1. What steps are required to upgrade from a 6506 to a 6616 Pentium Integrated PC Server?

    2.  

       

      If you create a new server (NWSD) after the correct level of V3R7 or V3R2 is installed, you do not need to do anything special to enable the Pentium Integrated PC Server.

      If you have an existing server (NWSD) on your AS/400 system, you need to change the resource name associated with the server after you install the new Pentium Integrated PC Server. For *NETWARE type NWSDs, you will also need to update some configuration files. See Informational APAR II09535 for V3R2 or II09667 for V3R7 for these additional steps.

    3. What steps are required to move back from a 6616 Pentium Integrated PC Server to a 6506 Integrated PC Server?

    4.  

       

      If you use the same NWSD that had been used for the 6616 Pentium Integrated PC Server, simply change the resource name to that of the 6506 Integrated PC Server. Otherwise, create a new NWSD specifying the resource name of the 6506 Integrated PC Server along with the other required and optional parameters. 


    1. How can I dump the memory of the Integrated PC Server if it is greater than 64MB?

    2.  

       

      You can dump the memory of OS/2 and the NetWare operating systems. This might be necessary if an SRC of 6506 6224 is reported by an Integrated PC Server. This error indicates that OS/2 running in the Integrated PC Server has detected a fatal fault. You would only create a dump if requested by IBM or Novell service.

      To link a dump disk to the server, you must vary off the network server description, then issue one of the following commands from a user profile with *ALLOBJ special authority:

      For an OS/2 dump, issue the following AS/400 command:

        CALL QSYS/QFPDMPSS PARM(nwsdname *LINK 'size')
    
    
    
      For a NetWare dump, issue the following AS/400 command:
        CALL QSYS/QFPDMPSS PARM(nwsdname *LINKNW 'size')
    
    
    
      The 'size' must be at least as large as the actual memory installed on the Integrated PC Server and can be one of the following values:
      • '*32' - 32 MB
      • '*64' - 64 MB (default if 'size' is not specified)
      • '*96' - 96 MB
      • '*128' - 128 MB
      • '*160' - 160 MB
      • '*192' - 192 MB
      • '*224' - 224 MB
      • '*256' - 256 MB
      This program creates a server storage space object in library QUSRSYS with a name based on the NWSD name (nwsdnameDP for OS/2 and nwsdnameNW for NetWare). The program initializes the *SVRSTG object and then links it to the network server description as drive J: (OS/2) or drive I: (NetWare).

      After you have linked the storage space, vary on the NWSD and try to reproduce the failure. When a dump occurs, it is written to the storage space.

      See Memory Dump in Integrating AS/400 with Novell NetWare V3R7, SC41-4124-01 for more information.


      Back to the top.