Chapter 14. Installing NetWare Applications

This chapter gives you examples of how to install NetWare applications by documenting how to install NetWare for SAA: AS/400 Edition and Lotus Notes** on an Integrated PC Server-based NetWare server. Throughout this chapter, references to NetWare servers refer to Integrated PC Server-based NetWare servers. 

* figure attn not displayed.
This chapter describes information in reference to a non-IBM product and IBM assumes no responsibility for its accuracy or completeness. The use of this information or the implementation of any of these techniques is a customer responsibility and depends on the customers ability to evaluate and integrate them into the customer's operational environment. While each item has been reviewed by IBM for accuracy in a specific situation, there is no guarantee that the same or similar results will be obtained elsewhere. Customers attempting to adapt these techniques to their own environments do so at their own risk. 
Most of the available NetWare applications and NLMs work with the NetWare server on the Integrated PC Server. Be aware of some special requirements and considerations when using the Integrated PC Server and NetWare on the Integrated PC Server: 
  • The Integrated PC Server does not have a console display or keyboard. 
  • The Integrated PC Server does not have a COM or a LPT port. 
  • The Integrated PC Server does not have a diskette drive. 
  • The Integrated PC Server can only use token-ring or Ethernet communications. 
  • NetWare runs on OS/2. 
  • OS/2 uses from 11MB to 14MB of the Integrated PC Server memory. 
  • The Integrated PC Server can also be used as a host communication adapter. 
In general, the installation of NetWare applications and the administration of the applications on the Integrated PC Server is the same as on a PC-based server. But because the Integrated PC Server has no console, the administrator must do most of the work from a PC remote console session. For more information on how to start RCONSOLE, see "Using RCONSOLE"

For examples of how to install a product on the NetWare server on the Integrated PC Server, see "Installing NetWare for SAA: AS/400 Edition" and "Installing Lotus Notes** for NetWare"


Installing NetWare for SAA: AS/400 Edition

This section illustrates how to install NetWare for SAA and discusses the special considerations for installing NetWare for SAA on the Integrated PC Server. 

We tested the following section using Disk 5 in the Novell Software Connection Library. NetWare for SAA: AS/400 Edition for NetWare is shipped in the SAA400 directory. 

We also used the NetWare for SAA: AS/400 Edition Installation Guide, which was located in the SAA400\README\ directory as SAA400INS.EXE. 

NetWare for SAA is a gateway application for NetWare requesters that runs IPX or TCP/IP to communicate with the AS/400. For detailed information about this product, see the product documentation. 

tip 
If you have Client Access for Windows 95 installed on your workstation, you do not need to install NetWare for SAA to communicate with AS/400. You can use the IPX communications stack provided with Client Access to communicate with both NetWare and AS/400. 
note 
See the NetWare for SAA: AS/400 Edition Installation Guide for important information about bindery emulation, a read/write replica of the partition where the server is defined, and required rights. 
task 
To install NetWare for SAA: AS/400 Edition: 

 

 

Refer to the NetWare for SAA: AS/400 Edition Installation Guide for information on copying software to a NetWare volume. This book provides detailed instructions for installing a NetWare server. The only variation to those instructions concerns the license diskette. With the Integrated PC Server, you need to copy the data from the license diskette to the E: drive of the NetWare server that is using RCONSOLE. 

If you copy the Novell NetWare files on a NetWare volume from CD-ROM, note that you will copy diskette images rather than product files. Therefore, you may need to follow the CD-ROM instructions during installation. 

  1. Login to the NetWare server and copy the source files into a directory. 

  2. You must install COMMEXEC from the server console because NetWare for SAA uses the PINSTALL.NLM, which cannot be loaded remotely. Thus, the installation program does not support the remote workstation installation path. 

    To copy the source files: 

    1. Map a drive to a user volume on your NetWare server. 
    2. Create a source directory on your NetWare server with two subdirectories: COMMEXEC and NWSAA. 
    3. Copy the files to the server. 

    4. In the following example, the G: drive is a local CD-ROM drive and the N: drive is a mapped NetWare drive. 

      XCOPY G:\COMMEXEC\*.*  N:\SOURCE\COMMEXEC /S
      
      XCOPY G:\NWSAA\*.*    N:\SOURCE\NWSAA /S
  3. Copy the contents of your license diskette to the E: drive of the network server description: 
    1. Prepare the drive by creating a directory with the Submit Network Server Command (SBMNWSCMD) command, which is shown in Figure 14-1. This procedure keeps all files from a specific product license together. 

    2.  
Figure 14-1. NetWare for SAA license directory.
+--------------------------------------------------------------------------------+
|              Submit Network Server Command (SBMNWSCMD)                         |
|                                                                                |
| Type choices, press Enter.                                                     |
|                                                                                |
| Command  . . . . . . . . . . . . > 'md e:saalic'                               |
|                                                                                |
|                                                                                |
| Server . . . . . . . . . . . . . > NWCC08                                      |
|                                                                                |
| Server type  . . . . . . . . . . > *NETWARE      *NWSUSRA, *NWSA...            |
| Command type . . . . . . . . . .   *OS2          *SVRTYPE, *OS2, *NETWARE...   |
|                                                                                |
|                                                                                |
|                                                                                |
|                                                                                |
|                                                                                |
|                                                                                |
|                                                                                |
|                                                                                |
|                                                                                |
|                                                                         Bottom |
| F3=Exit   F4=Prompt   F5=Refresh   F12=Cancel   F13=How to use this display    |
| F24=More keys                                                                  |
|                                                                                |
+--------------------------------------------------------------------------------+
    1. Start a remote console session and use ALT+F1 to display the RCONSOLE menu. 
    2. Select the Transfer Files to Server option to copy the data. Use a source drive of A:*.* and a destination drive of E:SAALIC, as shown in Figure 14-2. SAALIC is the directory in which the SAA license files were installed. 
    3. * figure tip not displayed.
      It is important that you enter the destination path without a slash at the end. 
      Figure 14-2. NetWare RCONSOLE License Copy
+------------------------------------------------------------------------------+
|                                                                              |
|                                                                              |
|                                                                              |
|                                                                              |
|               +---------------------------------------------------+          |
|               |            Source path on workstation             |          |
|               +---------------------------------------------------+          |
|               |>A:*.*                                             |          |
|               +---+-----------------------------------------+-----+          |
|                   | |Select A Screen To View                |                |
|                   | |Directory Scan                         |                |
|               +---+-----------------------------------------+-----+          |
|               |              Target path on server                |          |
|               +---------------------------------------------------+          |
|               |>E:SAALIC                                          |          |
|               +---+-----------------------------------------+-----+          |
|                   | |Configure Keystroke Buffering          |                |
|                   +-----------------------------------------+                |
|                                                                              |
|                                                                              |
|                                                                              |
|                                                                              |
+------------------------------------------------------------------------------+

      The license files are copied to a volume on the NetWare server. 
  1. Because NetWare for SAA consists of two components, you must first install the COMMEXEC product and then the NWSAA product. After you have successfully installed COMMEXEC, install NWSAA. 

  2. To do this: 

    1. Enter LOAD INSTALL from the RCONSOLE display and then choose Product options
    2. Select the Install a product not listed option and press Enter. Press the F3 key and then enter the path of your source directory. For example: SYS:\SOURCE\COMMEXEC\DISK1

    3. After you have successfully installed COMMEXEC, install NWSAA. 

    4. Select the Install a product not listed option and then press Enter. Press the F3 key and then enter the path of your source directory. For example: SYS:\SOURCE\NWSAA\DISK1
    tip 
    Remember that when you are asked to apply the SAA license, you need to change the drive letter from A: to E:SAALIC. 
  3. For the proper operation of NetWare for SAA you must be sure that the NetWare Btrieve** NLM is loaded with a special parameter. Change your AUTOEXEC.NCF file so that you have the Btrieve statement run with -u=1 before any other NetWare NLM is started. 
  4. Add the following load statements to a customized batch file (*.NCF) that is called from AUTOEXEC.NCF: 
  5. LOAD COMMEXEC
    LOAD NWSAA
    LOAD AS400PCS
  6. Verify that the AS/400 line description allows you to automatically create controllers, or manually create a controller for NetWare for SAA. 
To customize the NetWare for SAA server, use the NetWare for SAA Administrator tool that is shipped on the NetWare for SAA: AS/400 Edition CDROM. 
* figure tip not displayed.
If you want to use NetWare for SAA to connect to the same AS/400 in which your Integrated PC Server is installed, you must have either a second port on this Integrated PC Server or a separate token-ring or Ethernet card. You cannot specify the NetWare for SAA 802.2 node address as the remote 802.2 node address. 

Customizing NetWare for SAA 2.0 for a DOS Workstation

This section describes the installation of NetWare for SAA 2.0 on the workstation. You must have Client Access/400 for Extended DOS installed. 

Installing the NetWare Router 

* figure task not displayed.
To install the NetWare Router: 
  1. Log in to the server from your workstation and use the following command to map the NetWare for SAA 2.0 directory to your F drive, for example: 
  2.      MAP F:=SYS:\SYSTEM\NWSAA\AS400
  3. From the F: drive run the configure NetWare router program with the following command: 
  4.     CFGNRTR
  5. This program displays the screen shown in Figure 14-3

  6.  

     

    Figure 14-3. NetWare Router Configuration Main Menu

+------------------------------------------------------------------------------+
|   +-------------------------------------------------------------+            |
|   |           Configuration Main Menu                           |            |
|   +-------------------------------------------------------------+            |
|   |   | Modify STARTPCS.BAT To Use The NetWare AS/400 Router    |            |
|   |   | Create/Edit Client Access/400 Configuration File        |            |
|   +-------------------------------------------------------------+            |
|                                                                              |
+------------------------------------------------------------------------------+
  1. Select Modify STARTPCS.BAT To Use The NetWare AS/400 Router and enter the path that contains your STARTPCS.BAT file, for example:
  2.    C:\PCS\STARTPCS.BAT
    
    
  3. Press Enter and the program prompts you for your LAN protocol (either IPX or TCP/IP). The program then replaces the STARTRTR command in your STARTPCS.BAT file with STRNRTR or STRNTCP and also adds a statement called RTRMAP. This statement is required when using the NetWare router with the Client Access/400 DOS Extended client. 

  4.  

     

    By default, RTRMAP is configured to have a 4KB memory buffer. In some cases, where users are using many Client Access/400 sessions, you may need to increase the buffer size. You can set a different size (up to 64KB) by specifying RTRMAP /s=xx. A size of at least 16KB is recommended. 

  5. Return to the previous menu and select the Create/Edit Client Access/400 Configuration File option from the configuration menu and specify the path for your CONFIG.PCS file, for example:
  6.    C:\PCS\CONFIG.PCS
    
    
    Figure 14-4 is then displayed. 

    Figure 14-4. Edit AS/400 PC Support Configuration File

+------------------------------------------------------------------------------+
| +-----------------------------------------------------+                      |
| |  Edit Client Access/400 Configuration File          |                      |
| |-----------------------------------------------------|                      |
| |  Default server name (CSNA):   NWCC08               |                      |
| |  NetWare user ID (CSID):       CSADMIN              |                      |
| |                                                     |                      |
| |  Local LU name (RTLN):         PC1                  |                      |
| |  Common user id (RTCU):        USER1                |                      |
| |  Software Interrupt (INTL):    68 hex               |                      |
| |                                                     |                      |
| |  ASCII to EBCDIC table (A2ET):                      |                      |
| |  EBCDIC to ASCII table (E2AT):                      |                      |
| |                                                     |                      |
| |  AS/400 system links:        |  SYSNAM55            |                      |
| |                              |                      |                      |
| |                              |                      |                      |
| |                              |                      |                      |
| |                              |                      |                      |
| |                              |                      |                      |
| |  Default system name (RTDN):                        |                      |
| +-----------------------------------------------------+                      |
|                                                                              |
+------------------------------------------------------------------------------+

  1. Enter the name of your NetWare for SAA server for the default server name. You can press Insert for a list of available servers. This name is used to create a CSNA statement in the CONFIG.PCS file. 
  2. Enter your NetWare user ID for the NetWare user ID. If you have configured for NetWare for SAA security (in CSCON), then specifying a user ID allows you to be prompted only for the password. 
  3. Use the local LU name as the name of the PC. This value is used to create a device description on the AS/400. 
  4. Specify the conversion tables that are used by Client Access/400 in the ASCII to EBCDIC conversion table values. In the United States, the default tables (held in the PCS/MRI2924 directory) are used and you do not need to specify your table. 

  5.  

     

    For other countries you should specify the directory holding the table for your national language version. For this example, if you wanted to specify German you would use 2929. 

        C:\PCS\MRI2929\PCSATOE.TBL
        C:\PCS\MRI2929\PCSETOA.TBL
    
    
  6. Press Enter to see a list of the defined AS/400 system links ( Figure 14-5). The list shows you the links that are already defined in your CONFIG.PCS file. 

  7.  

     

    Figure 14-5. List System/Additional Systems

+------------------------------------------------------------------------------+
| +-----------------------------------------------------+                      |
| |  List System/Additional Systems                     |                      |
| |-----------------------------------------------------|                      |
| |  Modify Link System:          SYSNAM00              |                      |
| |                                                     |                      |
| |  Additional Systems:          |                     |                      |
| |                               |                     |                      |
| +-----------------------------------------------------+                      |
+------------------------------------------------------------------------------+

  1. Press Insert to show Figure 14-6, which allows you to define additional links. Here you can specify another AS/400 and, if you like, another NetWare for SAA server. One of the advantages of NetWare for SAA 2.0 is the ability to specify multiple servers from one client. The AS/400 user ID specified here overrides the default common user ID that you specified in step 8 on page 6. In this way you can use one user ID on AS/400 A, and another on AS/400 B. 

  2. Figure 14-6. Defined AS/400 Systems Links

+------------------------------------------------------------------------------+
|   +-----------------------------------------------------+                    |
|   | Modify Link System           System Name: SYSNAM55  |                    |
|   +-----------------------------------------------------+                    |
|   |  Link type:  802.2                                  |                    |
|   |  AS/400 system user ID: USER1                       |                    |
|   |  Server name: NWCC08                                |                    |
|   |  Adapter address: 4000 00000049  hex                |                    |
|   |                                                     |                    |
|   +-----------------------------------------------------+                    |
|                                                                              |
|                                                                              |
|                                                                              |
|                                                                              |
|                                                                              |
|                                                                              |
|                                                                              |
|                                                                              |
|                                                                              |
|                                                                              |
|                                                                              |
|                                                                              |
+------------------------------------------------------------------------------+

  1. Exit and save your file after completing the configuration. The program then updates your CONFIG.PCS file for NetWare for SAA 2.0 adding statements similar to the following example:
  2.      CSNA NWCC08
         CSID CSADMIN
         RTYP ITRN
         RTLN APPN.PC1
         SFLR 1,I,,SYSNAM03
         TRLI SYSNAM30,400000CC0800,,USER1
         TRLI SYSNAM55,400000000049,,USER1
         TRMF 2048
    
    

Customizing the NetSoft** Router for NetWare for SAA

This section explains the installation procedure for the Novell-supplied NS/Router**. 

Installing the NetSoft Router

* figure task not displayed.
To install the NS/Router: 
  1. Put the NS/Router installation diskette in the A: drive. 
  2. Choose File and Run from Windows. Enter A:\SETUP at the prompt. 

  3. You can use the Single User option to install the NS/Router code on your PC. The other options available on the screen allow you to use a PC file server to make one copy of the NS/Router code available to multiple PCs on a LAN. 

  4. Choose between an express or a custom install on the next screen. 
  5. Specify a directory name into which the NS/Router code is installed (some code is also installed into the Windows directory). The default directory is \NSROUTER. 
  6. Select Continue. Files are copied from the installation diskette. 
  7. Select the Launch NS/Router Configurator when the Setup Complete screen is displayed. 
  8. Choose Change... followed by Add... from the Link Information box to input the SAA server information. On the Add Server Name screen, enter the name of the NetWare for SAA server at the prompt. Select OK until you return to the main configurator screen. 
  9. Select Add... from the AS/400 System Information box. 
  10. Enter the System Name and Destination Adapter Address for the AS/400 that you are connecting to through the NetWare for SAA server. Enter the user ID and password information if you do not want to be prompted for this when you start the AS/400 connection. Select OK to return to the main configurator screen. 
  11. Enter the name of the PC in the Location Name box. 
  12. Select Preferences... from the bottom of the main configurator screen and the options are displayed. 
    • Select Automatically Start All Systems to force the NS/Router connection to be started to the AS/400s defined in the configuration file, as soon as the router is activated. 
    • Select Minimized on Startup to have an icon display for the router session. 
    • Select Default Auto Start Router Configuration File to enable you to specify the name of the configuration that is used if Rumba is started without an active NS/Router link. In this situation, the router is automatically started with the specified configuration. 
    Select OK to return to the main configurator screen. 
  13. Select File followed by Save from the menu bar and give the configuration a name with an extension of .RTR. 
  14. This completes the installation and configuration of the NS/Router. Select File followed by Exit from the menu bar to leave the configuration program. 
The NS/Router group is created on the Windows desktop. 
Starting the NS/Router

Before you start the router, change the Autodisconnect statement from 60 to 0 in the profile for the NetSoft Router. This allows you to eliminate annoying messages that occur because the NetSoft Router tries to disconnect every 60 seconds. 

* figure task not displayed.
To start the NS/Router: 

 

 

The NS/Router can be started manually from within Windows. To test your configuration, do the following: 

  1. Select the NS/Router icon from the NS/Router group. 
  2. Choose File and Open and select the configuration file to be used, then select OK

  3. If you chose the option to automatically start all systems on the screen, the connection to the AS/400 is established. Unless you specified the user ID and password information in step 9, you are prompted to sign on at this stage. 

    * figure note not                      displayed.
    Depending on how the NetWare for SAA server has been set up, you may be asked for your NetWare logon. 
    If the connection is not made automatically in this way, you can activate the link either by dragging the entry from Inactive AS/400 System Links box into the Active AS/400 System Links box with the mouse, or by selecting Router followed by Start from the menu bar. Select the AS/400 system to connect to and then select OK
Automating the Connection

The NS/Router connection can be automated such that when Windows is started, the connection is established without any user intervention. 

* figure note not displayed.
You can also configure the NS/Router to start when a Rumba session is started. To do this you must define which NS/Router configuration file you want to be used as the default. Select Default Auto Start Router Configuration File from the screen and enter the name of the configuration file. 

 

 

Rather than use this approach it is recommended that you automate the connection at Windows startup time to avoid the situation described in "Start NS/Router Before Client Access for Windows"

There are two alternative methods that can be used to automate the router connection when Windows starts:  Using the Startup Group
* figure task not displayed.
To automate the connection using the Startup Group: 
  1. Ensure that when you configure your NS/Router connections you include the following: 
    • The user ID and password information on the screen unless you want to be prompted for this when the connection starts. 
    • The option to automatically start all systems on the screen. 
  2. Create an icon for the NS/Router configuration: 
    1. Select the group for which you want to create the icon with a single click on the mouse (for example, the NS/Router group). Then select File followed by New from the Program Manager menu bar. 
    2. Enter Program Item and OK and fill in the information. The full entry for the Command Line prompt is
    3. C:\NSROUTER\NSROUTER.EXE C:\WINDOWS\<profilename.rtr>
      where <profilename.rtr> is the name of the NS/Router configuration file that you created in step 12
    4. Select OK, and the icon is created in the Windows group. You could now start the NS/Router connection by selecting the icon. 
  3. Copy the icon created in step 3 to the Windows Startup group to automate the connection when Windows starts: 
    1. Open the Windows Startup group by selecting it from the Program Manager. 
    2. Select the icon to be copied with a single click on the mouse, and then select File followed by Copy from the Program Manager menu bar. 
    3. Select the Startup group as the group to copy to then select OK
Using the WIN.INI File
* figure task not displayed.
To automate the connection using the WIN.INI File: 
  1. Ensure that when you configure your NS/Router connections you include the following: 
    • The user ID and password information on the screen unless you want to be prompted for this when the connection starts. 
    • The option to automatically start all systems on the screen. 
  2. Edit the WIN.INI file in the Windows directory to include the following run= entry in the [windows] section: 
  3. run=C:\WINDOWS\<profilename.rtr>
    where <profilename.rtr> is the name of the NS/Router configuration file that you created in step 12
APPC DLL Initialization

If you try to start the NS/Router without having started the NetWare requestor before loading Windows, you receive the error: 

APPC DLL is not initialized.
NO SYSTEMS CAN BE STARTED!
Start NS/Router Before Client Access for Windows

Always start the NS/Router before starting any Client Access for Windows function. If you start a Client Access for Windows function first you get the following error: 

Cannot find EHNAPPC.DLL entry points!
Verify that you have the correct
library and start the Router again.
To correct this error you must exit and restart Windows. 

The best way of ensuring that the NS/Router is started first is to follow the procedure described in "Automating the Connection"


Installing Lotus Notes** for NetWare

This section documents the special considerations for installing Lotus Notes on an Integrated PC Server-based NetWare server. Thus, these steps do not include every detail of the installation process. 

Lotus Notes provides: 

  • Tools and interfaces that enable users to easily create and share information. 
  • Support for sending, receiving, and managing electronic mail. 
  • An environment for creating and running Notes applications that are customized to business needs. 
note 
When you follow these steps to install Lotus Notes on a NetWare server, you are not installing the OS/400 Integration of Lotus Notes program. Therefore, you will not benefit from the following capabilities that are available with Lotus Notes Integration: 
  • Integration of the Notes address book with the AS/400 distribution directory. 
  • Exchange of Notes mail with OfficeVision on AS/400. 
  • Integration of Notes data with the AS/400 DB2 relational database. 
task 
To install Lotus Notes on a NetWare server: 
  1. Install the Notes client on a Windows workstation that is also a NetWare requester. You will need to install the Lotus Notes server files from this client workstation later. 

  2. To install the Notes client, follow the instructions provided with Lotus Notes. 

  3. Login to the NetWare server on which you want to install Lotus Notes. 
  4. Map a drive to the volume on the NetWare server in which you want to install the Lotus Notes server. 
  5. Insert the Lotus Notes CD-ROM into the drive of your Windows workstation and then either use the Run command or double-click the Install icon in the NetWare folder. 
  6. Provide the necessary information and proceed through the installation windows. 
  7. When the Install Options window appears, select the Drive you just mapped to a NetWare volume on your NetWare server. 

  8. By default, the Lotus Notes server files are installed in the \notes\ directory and a Lotus Applications folder is created. 

  9. Complete the installation. 
  10. Start RCONSOLE and add the following lines to a custom batch file in the SYS volume on your NetWare server. For example, you might have a batch file named AUTOSTR.NCF that is called from AUTOEXEC.NCF. 
  11.    search add sys:notes
       load mathlib
       load notessrv
    where notes is the name of your Notes directory. 
  12. Exit RCONSOLE. 
  13. Vary off and then vary on the NetWare server. To do this, enter WRKCFGSTS CFGTYPE(*NWS) from an AS/400 session and then use option 2 and then option 1. 

  14. Lotus Notes is now installed on your NetWare server, and you are ready to set up the Notes server. 

  15. Start RCONSOLE for the NetWare server on which you installed Notes. 
  16. Double-click Lotus NotesNetWare Administration in the Lotus Applications folder. 

  17. After you select OK on the Notes Server Setup window, the First Server Setup window appears. 

  18. Type the required information and then select NetWare SPX as the Network type. Then select OK. 

  19. The Advanced Server Setup Options window appears. 

  20. Type the domain name and make sure the checkboxes are checked for creating an organization certifier ID, a server ID, and an administrator ID, and then click OK 
  21. Select your time zone and then click OK. 
Now your NetWare server is also set up as a Lotus Notes server, and you can create mailboxes and databases for Notes clients. 

Installing an IPX/IP Gateway

This section describes how to install an IPX/IP Gateway on a NetWare server that is on an Integrated PC Server. 

The IPX/IP Gateway allows NetWare clients using IPX to access IP services such as the Internet. You do not need to install IP on the client workstations; you just need to install the IPX/IP gateway on your NetWare server. 

To install IPX/IP Gateway on a NetWare server that is on an Integrated PC Server, do the following: 

  1. Copy the license diskette for Novell Internet Access Server to the E: drive. 
  2. SBMNWSCMD CMD('MD E:NTWLIC') SERVER(SERVER01) SVRTYPE(*NETWARE)
              CMDTYPE(*OS2)
    Use RCONSOLE to transfer the files (Alt+F1). The source is a:*.* and the target is e:\ntwlic

    Refer to Novell's TID 2918956 License disk for NIAS 4 Internet Access Server for more information about the Novell Internet Access Server. This TID can be found at Novell's support site at http://support.novell.com. 

  3. Copy the NIAS subdirectory from CDROM number 3 of the IntranetWare CDROM package to a volume on the server: 
    1. Create a storage space with the size of 80MB using WRKNWSSTG option 1. 
    2. Link it to the server using WRKNWSSTG option 10. 
    3. Use RCONSOLE, LOAD INSTALL, and then Disk options to partition this storage space to be a NetWare partition. 
    4. Use RCONSOLE, LOAD INSTALL, Volume options to create a volume called NIAS4 on this new storage space. 
    5. On your client workstation, from a DOS prompt, enter: 
    6. MAP H:=server1\NIAS4:
      where H: is the drive you want to assign to NIAS4 volume and server1 is the server name. 
    7. From the DOS prompt on your client workstation, copy the data to volume NIAS4, using the following command: 
    8. XCOPY D:\NIAS\*.*  H:\NIAS  /S
      where D: is the CDROM on the workstation and H: is mapped to the NIAS4 volume on the server. 
  4. Use remote console (RCONSOLE) and select the following options: 
    1. LOAD INSTALL 
    2. Product options 
    3. Install a product not listed 
    4. Press <F3> and then specify NIAS4:NIAS\INSTALL 
    5. Enter E:\NTWLIC when prompted for the license 
  5. Vary off the server by using WRKCFGSTS *NWS and then use option 2. 

  6. After the server is varied off, you can unlink the new storage space using WRKNWSSTG option 11. You can then either delete the storage space or link it to other NetWare servers on your AS/400 that you wish to install the IPX/IP Gateway on. Vary back on the server by using WRKCFGSTS *NWS and then use option 1. 

  7. Set up IP on your server if you have not already done so. 

  8. For more information about installing and configuring TCP/IP, see TCP/IP Configuration and Reference

    In order to route TCP/IP outside your local ring, you need to add either LOAD ROUTE BOARD=1 or LOAD ROUTE BOARD=2, depending on your board number that IP is bound to. If your Domain Name Server is outside your local ring, you must add this statement. 

    You can verify TCP/IP connections to other servers from your server by using LOAD PING from the RCONSOLE command line. Attempt to ping the TCP/IP addresses of the other servers. 

  9. For instructions on setting up the IPX/IP Gateway Server, see either Novell's TID 2919554 Configuring the IPX/IP Gateway Server at Novell's support site (http://support.novell.com) or the dynatext document on CDROM #3 in NIAS4:\HTMLDOCS\CONFIG\IPXIPGW.HTML. 
  10. After you install the IPX/IP Gateway on the server, you need to enable it on your client workstations. See the documentation for this on CDROM number 3 from the IntranetWare package (NIAS4:\HTMLDOCS\CONFIG\GWCLIENT.HTM). 
  11. If you are having problems with the IPX/IP Gateway, see the Novell support page at http://support.novell.com. 

  12. Use Search and then search on IPX/IP. This site has some good documents that provide good information and help. 


[ Top of Page | Previous Page | Next Page | Table of Contents | Index ]