Chapter 3. Configuring OS/400 Integration for Novell NetWare
* figure nicube not displayed. 
This topic covers the configuration of OS/400 Integration for Novell NetWare, assuming you have completed installing the feature, as described in Figure 2-2. Skip this topic if you are not using OS/400 Integration for Novell NetWare. 
This topic consists of the following steps: 
point 
If you are using Integrated PC Servers as NetWare 4.10 servers, you can upgrade all of your Integrated PC Servers to NetWare 4.11 on your AS/400 system by using the procedure described in Appendix C. "NetWare 4.1 Considerations"

Step 1--Insert the NetWare 4.1 CD into the AS/400 CD drive

The NetWare CD-ROM can be either NetWare 4.10 or NetWare 4.11. NetWare 4.11 can be the NetWare 4.11 version on the IntranetWare CD-ROM. 

If you want to access the NetWare 4.1 CDROM from another device on your LAN, or if you have copied the CDROM image to a folder on the AS/400 system, AS/400 prompts for the location of the NetWare image later. 


Step 2--Collect Information for the Install NetWare Server (INSNTWSVR) Command

After you have installed the OS/400 features (5716-SA2 and 5716-SA3), you run the Install NetWare Server (INSNTWSVR) command. The INSNTWSVR command simplifies the installation and configuration process for NetWare servers running on the Integrated PC Server. You can copy only the NetWare source, or you can install the NetWare server. When you install the NetWare server, the INSNTWSVR command does the following: 

  • Optionally copies the NetWare source to the server storage space. 
  • Creates an IPX description 
  • Creates a network server description 
  • Creates one or more line descriptions 
  • Adds one or more IPX circuits 
  • Creates a network server storage space for the SYS: volume 
  • Links the network server storage space to the network server description 
  • Varies on the network server description if *YES was specified for the vary configuration (VRYCFG) prompt 
You need the information discussed in the following topics ready before you run the INSNTWSVR command. You can write the information into the spaces provided in Figure 3-1

Figure 3-1. INSNTWSVR Planning Information
 

The Install NetWare Server display is shown in Figure 3-2


Step 3--Run the Install NetWare Server (INSNTWSVR) Command

Use the information collected in Step 2 to complete the parameter values for this command. The command runs for a number of minutes. 

Type insntwsvr, and press F4. 

When you have entered the parameter values, press Enter to run the command. You see a message that the INSNTWSVR command is running. This is a long running command and takes several minutes to complete. 

Figure 3-2. Install NetWare Server (INSNTWSVR) Display

+--------------------------------------------------------------------------------+
|                      Install NetWare Server (INSNTWSVR)                        |
|                                                                                |
|Type choices, press Enter.                                                      |
|                                                                                |
|Network server description . . .(1)SERVER4      Name, *CPYONLY                  |
|Resource name  . . . . . . . . .(2)CC04         Name                            |
|Port 1:                       (3)                                               |
|  Line type  . . . . . . . . . .   *ETH         *ETH, *TRN4M, *TRN16M           |
|  Local adapter address  . . . .   020040000010  020000000000-7FFFFFFFFFFF      |
|  IPX circuit information:                                                      |
|  IPX network number . . . . . .   00000010      00000001-FFFFFFFD              |
|  Frame type . . . . . . . . . .   *SSAP         *SSAP, *SNAP, *ETHV2, *ETHNTW  |
|                + for more values                                               |
|Port 2:                                                                         |
|  Line type  . . . . . . . . . .                  *ETH, *TRN4M, *TRN16M         |
|  Local adapter address  . . . .                  0200 00000000-7FFFFFFFFFFF    |
|  IPX circuit information:                                                      |
|  IPX network number . . . . . .                  00000001-FFFFFFFD             |
|  Frame type . . . . . . . . . .   *SSAP         *SSAP, *SNAP, *ETHV2, *ETHNTW  |
|                + for more values                                               |
|                                                                       More...  |
| F3=Exit   F4=Prompt   F5=Refresh   F12=Cancel   F13=How to use this display    |
| F24=More keys                                                                  |
|                                                                                |
+--------------------------------------------------------------------------------+
+--------------------------------------------------------------------------------+
|                                                                                |
| Type choices, press Enter.                                                     |
|                                                                                |
| Copy NetWare source  . . . . . .(4)*YES          *YES, *NO                     |
| Vary on configuration  . . . . .(5)*YES          *YES, *NO                     |
| IPX internal network number  . .(6)*RANDOM       00000001-FFFFFFFE, *RANDOM    |
| Server message queue . . . . . .(7)*JOBLOG       Name, *JOBLOG, *NONE          |
|   Library  . . . . . . . . . . .                 Name, *LIBL, *CURLIB          |
| Network server storage space:   (8)                                            |
|   Name . . . . . . . . . . . . .  *NWSD          Name, *NWSD                   |
|   Size . . . . . . . . . . . . .  200            100-8000                      |
| FSIOP language version . . . . .(9)*PRIMARY      *PRIMARY, 2  963, 2966, 2980..|
| Country code . . . . . . . . . .   *LNGVER       *LNGVER, 001, 002, 031, 033...|
| Code page  . . . . . . . . . . .   *LNGVER       *LNGVER, 437, 850, 852, 857...|
| NetWare language:             (10)                                             |
|   Language number  . . . . . . .   4   0-99                                    |
|   Language name  . . . . . . . .   *DFT           Name, *DFT                   |
| NetWare source directory . . . .(11)                     &cont.                |
| Text 'description' . . . . . . .   NetWare Server4 - LAB 15                    |
|                                                                                |
|                                                                                |
|                                                                                |
|                                                                                |
|                                                                                |
|                                                                        Bottom  |
| F3=Exit   F4=Prompt   F5=Refresh   F12=Cancel   F13=How to use this display    |
| F24=More keys                                                                  |
+--------------------------------------------------------------------------------+
When the command is finished, the following message appears: 
NetWare initialization completed.
 

INSNTWSVR Command Parameter Values

This topic explains how to determine which values to use for the parameters on the INSNTWSVR command. 

The initial server name (8 character maximum) 

(1) 
Choose a name for the server that is unique in your network. Once the server installation has completed, you can change the name of the server to a longer name, if needed. The NetWare server will be known to the network with this new name. However, commands such as ADDNWSSTGL, WRKNWSSTG, VRYCFG, for example, must use the 8 character NWSD name associated with that server when executing those commands. "Server" commands like WRKNWSSTS, DSPNWSUSR, WRKNTWVOL use the longer server name. You need to remember the correlation of the names if you choose to use longer ones. 
* figure note not displayed.
Notes: 
  • The *CPYONLY option allows you to copy only the NetWare source from the CD-ROM image to the AS/400. No other activity for installation is done; such as creating a NWSD or line description. You may want to use this option if you are upgrading the NetWare server. 
  • To change the server name to a longer name, change the AUTOEXEC.NCF file from RCONSOLE using EDIT NLM or using the INSTALL NLM. 
The resource name of the Integrated PC Server 
(2) 
You can determine this by using the Work with Hardware Resources (WRKHDWRSC) command and specifying *CMN for the Type value. "Determining the Hardware Resource Name--Example" explains in detail how to find the resource name. 

 

 
 
 
 
 
 

If you have multiple Integrated PC Servers, you select the resource for the Integrated PC Server on which you are installing NetWare. 

Determining the Hardware Resource Name--Example

You must determine the name of the resource before you run the INSNTWSVR command. To do this, use the Work with Hardware Resources (WRKHDWRSC) command specifying *CMN. The Integrated PC Server is displayed as a File Server IOP or a File Server IOA. Associated with the Integrated PC Server is a resource name. 

  • For most Integrated PC Servers, the resource name is in the format CCxx, where xx is the number associated with the resource. 
  • For the AS/400 Advanced Entry models, the resource name of the Integrated PC Server is in the format LINxx, where xx is the number associated with the resource. The Integrated PC Server is listed as type 2850. 
You can also determine whether you have a one- or two-port Integrated PC Server by using the Work with Hardware Resources display. As Figure 3-3 shows, the 486-processor Integrated PC Server adapter type is 6506. You can see this on CC01 and CC02. A one-port 486-processor Integrated PC Server shows a LAN Adapter of type 6510, and a two-port 486-processor Integrated PC Server shows a LAN Adapter of type 6520. All pentium Integrated PC Servers support two ports and show a LAN adapter type depending on whether they are Ethernet or token-ring. You can see this on CC03. 

The descriptive text for the ports states that a port is either Ethernet or token ring. Or, if no physical cable is attached, the descriptive text indicates that this is a LAN port. 

Figure 3-3. Work with Hardware Resources Display

+--------------------------------------------------------------------------------+
|                                                             System:   SYSAS400 |
| Type options, press Enter.                                                     |
|  5=Work with configuration descriptions   7=Display resource detail            |
|                                                                                |
|Opt  Resource        Type  Status                Text                           |
|     CMB01           9162  Operational           Combined function IOP          |
|       LIN01         2609  Operational           Comm Adapter                   |
|         CMN01       2609  Operational           V.24 Port                      |
|         CMN02       2609  Operational           V.24 Port                      |
|     CC01            6506  Operational           File Server IOP                |
|       LIN02         6510  Operational           LAN Adapter                    |
|         CMN03       6510  Operational           Token-Ring Port                |
|         CMN04       6510  Inoperative           Token-Ring Port                |
|     CC02            6506  Operational           File Server IOP                |
|       LIN03         6520  Operational           LAN Adapter                    |
|         CMN08       6520  Operational           LAN Port                       |
|     CC03            6616  Operational           File Server IOP                |
|       LIN04         6149  Operational           LAN Adapter                    |
|         CMN14       6149  Operational           Token-Ring Port                |
|       LIN05         6181  Operational           LAN Adapter                    |
|         CMN15       6181  Operational           Ethernet Port                  |
|                                                                       More...  |
|F3=Exit   F5=Refresh   F6=Print   F12=Cancel                                    |
+--------------------------------------------------------------------------------+


Port information
(3) 
If you have two ports and decide to configure only one port now, later you will need to create a line description and add an IPX circuit entry to use the second port. The port information includes the following: 
  1. The line type 
  2. Ethernet 
    Use *ETH for Ethernet. You can specify up to 4 unique external IPX numbers and unique frame types in Element 3. When AS/400 creates the line description for the Ethernet line, the Ethernet standard is set to *ALL. 
    Token Ring 
    Use *TRN4M for 4MB token ring, or use *TRN16M for 16MB token ring. 

     

     
     
     
     
     

    For most installations, *SSAP is the correct choice. 

  3. The local adapter address. 

  4.  

     
     
     

    For line type *ETH,use an address for the adapter that is between 020000000000-7EFFFFFFFFFF. For line type *TRN4M or *TRN16M, use an adapter address that is in the range of 400000000000-7FFFFFFFFFFF. 

  5. The IPX external network number 

  6.  

     
     
     

    Choose a number for your network address, unless you already have a NetWare network. If you already have a NetWare network, enter its network address. The network address must be the same for all the NetWare servers on this LAN segment. 

    * figure tip not                      displayed. 
    The external network number is often called the network address. To find the network address on an existing NetWare server, go to the server and type CONFIG. The network address appears under LAN Protocol. 

     

     
     
     
     
     

    The IPX external network number is a hexadecimal number, one to eight digits ( 1 to FFFFFFFE). The IPX external network number is a hexadecimal number, one to eight digits ( 1 to FFFFFFFE). The number must be unique within your connected IPX internetwork. Novell has a registry method that you can use to guarantee uniqueness. For more information about the IPX external network number, see the Internetwork Packet Exchange (IPX) Support and the Novell NetWare Concepts books. 

    atten 
    If you have two LAN adapters on the Integrated PC Server, the following restrictions apply when configuring the same frame type for both adaptors: 
    1. If the two adapters are connected to different LAN segments, you must specify different IPX external network numbers for the two adapters. 
    2. If the two adapters are connected to the same LAN segment, the two adapters must be the same type (both ethernet or both token-ring), and you must specify the same IPX external network number for both adapters. 
    3. If the two adapters are connected to the same LAN segment but the two adapters are different types (one ethernet and one token-ring), it is not valid to configure the same frame type on both adapters. 
    Note that if the two adapters are connected to separate physical LANs but a bridge is used to connect the two LANs, the two physical LANs form one logical LAN segment. In this case, restrictions b and c in the preceding list apply. 
  7. The frame type being used on your network. 

  8.  

     
     
     
     
     

    The frame type is controlled by the source service access points (SSAP) of the line description being used by the circuit. The values are *SSAP, *SNAP, *ETHV2, *ETHNTW. Use *SSAP to bind the 802.2 frame type to IPX. Use *ETHNTW to bind the 802.3 Raw frame type to IPX. 

    Ethernet Standards

    Different Ethernet standards use different frame formats. You must have your NetWare clients set up with the same frame type(s) as your NetWare servers. This is specified in the NET.CFG file on the NetWare client PC using the frame statement. The frame types are: 

    *SSAP (802.2) 
    NetWare 4.1 uses the IEEE 802.2 standard by default. 
    *ETHNTW (802.3) 
    Used as the default for NetWare 3.11 and earlier versions. This frame type is also called the 'Raw' frame. 
    *ETHV2 (Ethernet II) 
    Used on networks that communicate with DEC** minicomputers and on computers that use AppleTalk Phase I. 
    *SNAP (Ethernet SNAP) 
    The IEEE 802.2 frame type with an extension (SNAP) added to the header. Used on networks that communicate with workstations using protocols such as AppleTalk Phase II. 
    Token Ring

    If you are using token ring (Line type is *TRN4M or *TRN16M) then you can specify either *SSAP and *SNAP for the frame type. To run NetWare TCP/IP with source routing bridges, you must include the *SNAP frame type. This associates an IPX circuit with the *SNAP frame type with the line description. See "Installing TCP/IP" for a more detailed description. 

    You can specify up to 4 unique frame types for Ethernet and 2 unique frame types for token ring. These circuits do not communicate with each other, but coexist in the same network. 

Whether to copy NetWare source to the system 
(4) Specify *YES to copy the NetWare source the first time you are installing a NetWare server. 

 

 
 
 
 
 

Use *NO if the NetWare source was already copied. If you do specify *NO but the NetWare source was not already copied, then AS/400 issues an error message. 

If you specify *YES when the NetWare source was already copied, then AS/400 copies the source again, overlaying what exists on the system. Therefore,if the NetWare source was already copied, and you do not want the source overlaid at this time, specify *NO for Copy NetWare source. 

* figure note not displayed.
The value that AS/400 sets for this parameter varies. If the NetWare source is already copied, then AS/400 sets the value to *NO. If the source is not already copied, AS/400 sets the value to *YES. 

 

 
 
 

This parameter is not needed if NWSD(*CPYONLY) is specified. This parameter is only used to copy the NetWare source when installing a NetWare server (when the NWSD parameter specifies a name). 

Vary on configuration 
(5) 
Select *YES, which causes AS/400 to vary on the network server description (NWSD) that is created by this command using the Vary Configuration (VFYCFG) command. AS/400 also validates the resource name that is specified to ensure it exists and is not already in use. 

 

 
 
 
 
 

If you specify *NO, AS/400 does not vary on the network server description (NWSD) that is created by this command. The resource name is not validated. 

Later, you can vary the NWSD off to create more storage for NetWare to use. 

If you want to create additional storage spaces for user volumes, let the Vary on configuration (VRYCFG) value default to *YES. After the server is varied on, do the following: 
  1. Vary off the server (using the Vary Configuration (VRYCFG) command, 
  2. Create and link the storages spaces, 
  3. Then vary back on the server using the VRYCFG command. 
* figure tip not displayed.
If you do vary on a server for the first time with multiple storage spaces, you cannot control which storage space becomes the SYS: volume, and the other storage spaces automatically get volumes assigned to them. 
An IPX internal number for your server 
  1. (6) You can enter a number here, or you can let AS/400 generate one (*RANDOM). Valid values range from 00000001 through FFFFFFFE. 
The IPX internal network number identifies an individual NetWare server. Each server on the network must have a unique IPX internal network number. 

If you assign a number that is easy to remember, you can save the time it takes to look up the number AS/400 generated later. You may need this number to connect to your RCONSOLE session. The internal number is also used for tracing and for advertising the presence of your server on the network as well as for accessing NLMs that reside on this server. 

A server message queue
(7) 
Specify the name of a message queue to receive NetWare console messages and other server-related messages. You should not send NetWare console messages to your AS/400 QSYSOPR message queue. 

 

 
 
 

If you specify a message queue name that does not exist, the INSNTWSVR command creates the message queue for you. If you specify both a message queue and a library name and neither exists, the INSNTWSVR command fails. The library is not created and if it does not exist, the command cannot complete. 

*JOBLOG 
Console messages from the server are placed in the job log of the NetWare server's AS/400 monitor job. The monitor job name is derived from the server name specified for the NWSD ("The initial server name (8 character maximum)"). The monitor job name is: 
  NWSDname/QSYS/nnnnnn
where NWSDname is the name of the network server description (*NWSD) that is varied on and "nnnnnn" is the job number. The monitor job runs under the QSYS user profile in the QSYSWRK subsystem. The job starts when you vary on the network server description (NWSD). 
*NONE 
No server messages are sent to a message queue or to the monitor job log. 
* figure note not displayed.
The NetWare console log can contain password information. Take the appropriate steps to secure this information on AS/400. For tips about how to manage message queues, see "Hints for Setting Up Message Queues"
Network Server Storage Space 
(8) 
Specify the storage space size to be used. AS/400 uses this storage space to create the SYS: volume for the NetWare server. Specify enough space for the NetWare server, NDS, NLMs and other software that you keep in your system volume. 

 

 
 
 

The default (200 megabytes) is a guideline. Storage spaces can range from 100 to 8000 megabytes. 

Use *NWSD to have the same name for the storage space and for the NWSD. Or choose a name that has a maximum length of 10 characters. 

* figure tip not displayed.
You can create additional storage spaces later to store your user's data and programs. This enables you to save and restore storage spaces containing user data without affecting your NDS information stored on the system volume. 
FSIOP Language Version
(9) 
Use *PRIMARY, the default, to specify the same language for OS/2 Warp as you are using for AS/400. The OS/2 Warp language version does not apply to the language version of NetWare 4.1 that is installed. You can install any NetWare 4.1 SBCS language with any OS/2 SBCS languages. 
* figure tip not displayed.
Tips: 
  • OS/2 messages are rarely shown and therefore English is appropriate for all NetWare SBCS languages. NetWare Japanese requires OS/2 Japanese (language version 2962). 
  • Country code and code page are mapped to the AS/400 language, when the default, *LANGVER, is used. 
For more information about language versions supported, see Appendix D. "National Language Support"
NetWare Language
(10) 
Specify the same NetWare language number and directory associated with NetWare language stored on the CD-ROM image. Novell has identified language IDs for languages. The ID number and associated language name is required when copying files. The NetWare language can be different from the OS/400 language. 

 

 
 
 
 
 

The language directories for NetWare reside in two different places on the CD-ROM image with different names in each. Under the SYS:/SYSTEM/NLS the language directories are named with numbers: 0,1,2,.... The corresponding directories under SYS:/PUBLIC/NLS have the name of the language in that language. 

See Appendix D. "National Language Support" for the NetWare languages that have been defined. 

NetWare source directory 
(11) 
Specify the path name of the OS/400 IFS directory name associated with the CD-ROM image that is used as the source for the copy. The NetWare CD-ROM can be either NetWare 4.10 or NetWare 4.11. NetWare 4.11 can be the NetWare 4.11 version on the IntranetWare CD-ROM. 

 

 
 
 

The directory name may reference a CD-ROM volume (QOPT/volume), a folder (QDLS/folder) or a NetWare volume (QNETWARE/server_name/volume_name). Note that the CD-ROM volume is the volume of a CD-ROM and not a NetWare volume name. An example CD-ROM volume path name would be 

/QOPT/NW410
You can copy the NetWare source from elsewhere on the AS/400 integrated file system, if the image is stored there. The location could be a: 
  • Folder: 
  • /QDLS/folder_name
  • NetWare volume: 
  • /QNetWare/server00.SVR/cdrom
    Where: server00 is the name of the server to which the CD-ROM is attached. cdrom is the name of the CD-ROM drive volume on that server. 
The Work with Object Links (WRKLNK) command will show the integrated file system directory names on the system. 

Step 4--Install NetWare Client

If you have not already done so, install the NetWare client on the workstation you plan to use for this installation. You need the NetWare client to set up the NetWare server installed on the Integrated PC Server. The AS/400 system does not have a console to the NetWare server on the Integrated PC Server. RCONSOLE on a NetWare client provides this console. The NetWare client needs to establish an IPX connection to your AS/400 system. Your NetWare documentation from Novell explains how to install and use a NetWare client. Example documents are NetWare** Installation and NetWare** Client for DOS and MS Windows User Guide


Step 5--Install the RCONSOLE and NWADMIN Utilities

This topic explains the purpose of the utilities, then how to install them. 

What are RCONSOLE and NWADMIN?

Remote Console (RCONSOLE) is a DOS application that allows you to manage a NetWare server from a remote PC or workstation. In this case your NetWare server is running on the Integrated PC Server and the remote console is any workstation on the network that has RCONSOLE installed. You must have at least one workstation on the network that has RCONSOLE installed to configure the Integrated PC Server for OS/400 Integration for Novell NetWare support. RCONSOLE allows you to do the following:

  • Use console commands as you would at a NetWare server console. 
  • Scan directories and edit text files in both NetWare and DOS partitions on a server. 
  • Transfer files to a server. 
  • Install a license, NDS**, and utilities. 
  • Install or upgrade NetWare on a remote server. 
* figure tip not displayed.
Tips: 
  • Make sure that you are running the NetWare 4.1 version of remote console on your PC. The NetWare 3.12 version of RCONSOLE does not contain all the support required to install and use NetWare on the Integrated PC Server. 
  • If the server from the AS/400 does not show up in the RCONSOLE list, press the Insert key and input the internal IPX number from the IPX description on the AS/400 system. To determine the internal IPX number on the AS/400 system, use the Work with IPX Descriptions (WRKIPXD) display and then option 5 to display the details of the IPX description that has the same name as your NWSD. 

  •  
Figure 3-4. Finding the Internal Network Number on AS/400
+----------------------------------------------------------------------------+
|                            Display IPX Description                SYSNAM00 |
|                                                         08/27/96  15:08:20 |
| IPX description  . . . . . . . . . :   SERVER01                            |
| IPX internal network number  . . . :   CABCE572                            |
+----------------------------------------------------------------------------+



NetWare Administration (NWADMIN) is the utility that enables you to manage objects in the NDS tree, and information associated with those objects. For example, you can manage user objects in the NDS tree, and the rights assigned to those user objects. 

You must be logged in to the server before you can use NWADMIN. For more information on how to use NWADMIN and RCONSOLE, see the Novell NetWare documentation on Supervising the Network. 

This topic steps through installing the RCONSOLE and NWADMIN utilities on a workstation. You need these utilities to manage your NetWare server. You need to run the NetWare 4.1 version of RCONSOLE from a PC. If you have an earlier version of RCONSOLE, take the option to install RCONSOLE during this step. If you already have these utilities on the workstation which you are using, you can skip this step. 

* figure task not displayed. 
Installing RCONSOLE and the NWADMIN utility 
You must be running Windows. 
  1. Click on the File pulldown on the Program Manager window. 
  2. Click on the Run... option in the File pulldown. 
  3. Insert the diskette labeled OS/400 Integration for Novell NetWare into the A: drive of the workstation (where A: is the 3.5 inch diskette drive). 
  4. Type A:INSTALL in the Command line of the Run window and click on OK. 

  5.  

     
     
     

    The popup window indicating "Loading files ..." displays for approximately 15 seconds to one minute. 

    After this display, a README file appears that describes the installation process. Review the README file for various NetWare installation considerations. 

  6. Click on the Continue button once you have read this file. 
  7. Select one or both components: 
    • RCONSOLE 
    • NWADMIN 
    As you select the components you need, the number of bytes needed to install those components on your personal computer are displayed. 
  8. Select the directories where you want to install the RCONSOLE and NWADMIN components. The default is C:/QFPNWRC for RCONSOLE and C:/QFPNWAD for NWADMIN. 
  9. Click on the Install button when you have made your selections. 
  10. You are then prompted to select the NetWare language name, the NetWare language identifier, and the source of the CD-ROM image. 

  11.  

     
     
     
     
     

    The source of the CD-ROM image is one of the following: 

    • The CD-ROM drive attached to this workstation 
    • The drive and path of the CD-ROM image on a network drive 
  12. Click on the OK button. 

  13.  

     
     
     

    As the NetWare components load, you see a display that shows the files being copied. This display is similar for the RCONSOLE and NWADMIN components. 

    For each component you install, you receive a message stating that installation on the workstation was successful. 

    Click on the OK button to continue. 

  14. Exit the NetWare Integration utility. 
  15. Exit Windows. 

Step 6--Set Up the NetWare Server on the Integrated PC Server

The last stage of installing Integration for NetWare on an Integrated PC Server is to set up a NetWare server. This stage is part of the normal NetWare server installation process. It includes making the connection from your NetWare client and starting RCONSOLE. Then you can use RCONSOLE to install the licenses, configure NetWare directory services, and if needed, add additional languages. 

After you have completed the configuration on the console, you can log in to the server. You can then use NWADMIN to configure users, create user login scripts, and assign security rights to directories and files. For more information on using NWADMIN, refer to the Novell NetWare documentation. 

Using RCONSOLE

* figure task not displayed. 
To use RCONSOLE: 
  1. Click on the NetWare Integration icon that is located on your desktop. 
  2. Double click on the RCONSOLE icon in the NetWare Integration window. 

  3.  

     

    The default password for RCONSOLE is the name of the NWSD. You should change the password immediately after you have installed the license to minimize any security exposure. To change the password, the NetWare administrator needs to use RCONSOLE and then type LOAD INETCFG. Then take the options to Manage Configuration and then Configure Remote Access to this Server. You can change the password from this display. 

    * figure tip not displayed.
    If your Integrated PC Server ports are currently connected to more than one LAN segment, you must ensure that the workstation running RCONSOLE is connected to the correct LAN segment. This is necessary because only one LAN connection is initially active. It is important, therefore, to determine which port has the active connection. 
    The order that is given to loading and binding the sessions is the following: 
    1. Token-ring 
    2. Ethernet 
    3. Port 1 
    4. Port 2 
    As an example, if you have configured port 1 to be Ethernet and port 2 to be token-ring, port 2 is connected (bound) first and gets the RCONSOLE session because the token-ring statements are before the Ethernet statements in the NETINFO.CFG. As a second example, if you have configured both ports to be Ethernet, port 1 is connected. This is because the port 1 statements are run before the port 2 statements. 
    * figure tip not displayed.
    If you experience problems running RCONSOLE in the Windows 3.1 environment, exit Windows and run RCONSOLE from a native DOS environment. 
    Figure 3-5. RCONSOLE Server Selection

    * figure rv3z1833 not                displayed.
     

  4. Select your NetWare (as shown in Figure 3-5), then enter the password. 
  5. * figure tip not displayed.
    Tips: 
    • The default password for the Remote Console is the name of the NWSD object on the AS/400. You should change this password for better network security by using INETCFG. The password is no longer located in AUTOEXEC.NCF as in previous versions of NetWare. 
    • If the server list is empty, press the Insert key to enter the server's internal IPX address. 

    •  

       
       
       

      You can determine the NetWare server's IPX internal network number by using the OS/400 Work with IPX Descriptions (WRKIPXD) CL command. See Figure 3-4 for instructions. 

  6. You then see the console screen of the new server. This server is not fully installed or configured. To finish the setup of the NetWare server, you must do the following: 
    • Install a valid NetWare license 
    • Install NetWare Directory Services (NDS) 
    • Copy additional files to the server 

Step 7--Install a Valid NetWare License
* figure task not displayed. 
To install a valid NetWare license: 
  1. Type LOAD INSTALL from the server console. This loads the INSTALL utility. 

  2.  

     
     
     

    The NetWare license diskette must be accessible from your remote workstation's diskette drive. 

  3. Select License Option from the menu, which is shown in Figure 3-6

  4.  

     
     
     

    Figure 3-6. License Option Selection

+------------------------------------------------------------------------------+
| NetWare Server Installation  4.1                    NetWare Loadable Module  |
|                                                                              |
|  +-----------------------------------------------------------+               |
|  |                   Installation Options                    |               |
|  +-----------------------------------------------------------+               |
|  | |Driver options    (load/unload disk and network drivers) |               |
|  | |Disk options      (configure/mirror/test disk partitions)|               |
|  | |Volume options    (configure/mount/dismount volumes)     |               |
|  |>|License option    (install the server license)           |               |
|  | |Copy files option (install NetWare system files)         |               |
|  | |Directory options (install NetWare Directory Services)   |               |
|  | |NCF files options (create/edit server startup files)     |               |
|  | |Product options   (other optional installation items)    |               |
|  | |Server options    (install/upgrade this server)          |               |
|  | |Exit                                                     |               |
|  +-----------------------------------------------------------+               |
|                                                                              |
|                                                                              |
+------------------------------------------------------------------------------+



  1. Press F4 to indicate that the server must use the remote workstation A: drive as shown in Figure 3-7

  2.  

     
     
     

    Figure 3-7. Selecting the Remote Workstation A: Drive

+------------------------------------------------------------------------------+
|                                                                              |
|   NetWare Server Installation  4.1                   NetWare Loadable Module |
|                                                                              |
|  +-----------------------------------------------------------+               |
|  |      +----------------------------------------------------+----------+    |
|  +------+                                                               |    |
|  | |Driv|  The license file will be installed from drive A:. Insert the |    |
|  | |Disk|  disk labeled, "SERVER CONNECTION LICENSE", (which contains   |    |
|  | |Volu|  the file "SERVER.MLS") into the drive.  Licenses currently   |    |
|  |>|Lice|  installed on this server allow a total of 50 connections.    |    |
|  | |Copy|                                                               |    |
|  | |Dire|  Warning:  Do not try to install this same license on any     |    |
|  | |NCF |  other server.  Doing so will cause a copyright violation     |    |
|  | |Prod|  warning to be issued.                                        |    |
|  | |Serv|                                                               |    |
|  | |Exit|      Press <F3> to specify a different path;                  |    |
|  +------+      Press <F4> to specify a remote workstation path;         |    |
|         |      Press <Enter> to continue.                               |    |
|         |                                                               |    |
|         +---------------------------------------------------------------+    |
+------------------------------------------------------------------------------+



  1. Ensure that the license diskette is inserted in the workstation A: drive and press Enter. 
  2. When the license is installed, a message indicates that the license installation was successfully completed. 
* figure note not displayed.
Now you can install NetWare Directory Services (NDS) on the server. You use the INSTALL utility to do this. This is different from installing NetWare on a PC server where installation of directory services is performed without the INSTALL utility. Follow these steps to ensure all information is provided for the installation. 

Step 8--Install NetWare Directory Services
* figure task not displayed. 
To install NetWare Directory Services (NDS): 
  1. Select Directory options from the menu (Figure 3-8). 

  2.  

     
     
     

    Figure 3-8. Directory Service Option Selection

    * figure rv3z1837 not                displayed.
     

  3. Select Install Directory Services onto this server from the menu (Figure 3-9). 

  4.  

     
     
     
     
     

    Figure 3-9. Install Directory Services

    * figure rv3z1838 not                displayed.
     

  5. If this is not the first tree, you are provided a list of trees into which you can install this server. (Figure 3-10). 

  6.  

     
     
     
     
     

    Figure 3-10. Tree Selection

    * figure rv3z1854 not                displayed.
     

  7. If this is the first tree on the LAN or you want to create a new tree, press the Insert key. You are then asked for the name of the tree to be created (Figure 3-11). 
  8. * figure note not displayed.
    If you are installing the server in an existing NetWare environment, do so only with the approval of the network administrator. You must use the user ID of ADMIN with the appropriate password. This is even more important if you want to install the server in an existing tree. 
    Figure 3-11. Creating a New Tree
+-----------------------------------------------------------------------+
| NetWare Server Installation  4.1             NetWare Loadable Module  |
|                                                                       |
|+-----------------------------------------------------------+          |
||                   Installation Options                    |          |
|+-----------------------------------------------------------+          |
|| |D+-------------------------------------------------------+--+       |
|| |D|                Directory Services Options                |       |
|| |V+----------------------------------------------------------+       |
|| |L|>|Install Directory Services onto this server             |       |
|| |C| |Remove Directory Services from this server              |       |
|| |D| |Upgrade NetW+---------------------------------------+ory|       |
|| |N| |Upgrade moun| Enter a name for this Directory tree: |   |       |
|| |P| |Return to th+---------------------------------------+   |       |
|| |S+--------------+>NW                                    ++--+       |
|| |Exit            +---------------------------------------+|          |
|+-----------------------------------------------------------+          |
|                                                                       |
|                                                                       |
|                                                                       |
|                                                                       |
|                                                                       |
|                                                                       |
+-----------------------------------------------------------------------+
 

* figure tip not displayed.

    You should use the NetWare administrator user ID (ADMIN) and the associated password. 
  1. Select the time zone in which this server is located for time synchronization (Figure 3-12). 

  2. Figure 3-12. Time Zone Selection
+----------------------------------------------------------------------------------+
|   NetWare Server Installation  4.1                    NetWare Loadable Module    |
| +------------------------------------------------------------------------------+ |
| |                  Verify/Enter Time Configuration Parameters                  | |
| +------------------------------------------------------------------------------+ |
| | Time server type:                               Single Reference             | |
| |                                                                              | |
| | Standard time zone abbreviation:                CST                          | |
| | Standard time offset from UTC:                  6:00:00  BEHIND              | |
| |                                                                              | |
| | Does your area have daylight saving time (DST): YES                          | |
| | DST time zone abbreviation:                     CDT                          | |
| | DST offset from standard time:                  1:00:00  AHEAD               | |
| | DST Start: First Sunday of April at  2:00:00 am                              | |
| | DST End:   Last Sunday of October at  2:00:00 am                             | |
| ++-----------------------------------------------------------+-----------------+ |
|  +-----------------------------------------------------------+                   |
| +------------------------------------------------------------------------------+ |
| |  End Of Daylight Saving Help                                                 | |
| |                                                                              | |
| |  Press <Enter> and follow the prompts to specify the day and time that       | |
| |  daylight saving ends and standard time begins.                              | |
| |                                                                              | |
| +------------------------(To scroll, <F7>-up <F8>-down)------------------------+ |
+----------------------------------------------------------------------------------+



  1. Specify the context of the NetWare server as it is illustrated in Figure 3-13

  2.  

     
     
     
     
     

    Figure 3-13. Context for Server and Tree

+----------------------------------------------------------------------------------+
|   NetWare Server Installation  4.1                    NetWare Loadable Module    |
| +------------------------------------------------------------------------------+ |
| |                           Context For This Server                            | |
| +------------------------------------------------------------------------------+ |
| | Company or Organization:                    NW                               | |
| | Level 1 Sub-Organizational Unit (optional): AS400                            | |
| | Level 2 Sub-Organizational Unit (optional):                                  | |
| | Level 3 Sub-Organizational Unit (optional):                                  | |
| |                                                                              | |
| | Server Context:     OU=AS400.O=NW                                            | |
| |                                                                              | |
| | Administrator Name: CN=Admin.O=NW                                            | |
| | Password:                                                                    | |
| ++-----------------------------------------------------------+-----------------+ |
|  +-----------------------------------------------------------+                   |
| +------------------------------------------------------------------------------+ |
| |  Password Help                                                               | |
| |                                                                              | |
| |  Enter the password for the Administrator Name above.                        | |
| |                                                                              | |
| |                                                                              | |
| +------------------------(To scroll, <F7>-up <F8>-down)------------------------+ |
+----------------------------------------------------------------------------------+



    A message indicates that NDS is installed. When that message is displayed, exit RCONSOLE. 
For more information on using NetWare 4.1, see the Novell documentation listed in Appendix F. "Bibliography"

Step 9--Copy NetWare Files
* figure task not displayed. 
To copy NetWare files: 
During installation, only the required files are copied from the CD-ROM to the SYS: volume. You must install additional files on the SYS: volume to support utilities that you plan to use. To copy these files, the CD-ROM must be available to the server either from the workstation CD-ROM drive or from an image of the CD-ROM on the network. 
* figure tip not displayed.
Ensure that you exit Windows and run RCONSOLE from DOS during this step of the server installation. If you run RCONSOLE under Windows during this step, unpredictable results can occur and the copy process might not complete. 
    To copy additional files to the NetWare server, select the Copy files option from the Installation Options menu as shown in Figure 3-14
     

    Figure 3-14. Copy Files Option Selection

    * figure rv3z1855 not                displayed.
     

  1. Depending on the level of NetWare code you have, you may receive a warning message indicating that you do not have an A: drive. Press Enter to confirm. 

  2.  

     
     
     
     
     

    Figure 3-15. Drive A Warning Message

                 +----------------------------+
                 | Directory path A:\ is      |
                 | invalid. (INSTALL-4.1-265) |
                 |                            |
                 | Press <Enter> to continue. |
                 +----------------------------+
    Press F4 to specify a remote workstation path (Figure 3-16). 


    Figure 3-16. Selecting the Path for Copying

    * figure rv3z1856 not                displayed.
     

  3. Specify the complete path of the workstation that contains the installation files (Figure 3-17). 

  4.  

     
     
     
     
     
     
     

    For example, specify E:/PRODUCTS/NW411/ INSTALL/IBM/OS2/XXX/ENGLISH for NetWare 4.11. Specify E:/NW410/INSTALL/ENGLISH for NetWare 4.10. If necessary, change the language directory to match the language on your CD-ROM. 

    Figure 3-17. Path to the Data

    * figure rv3z1857 not                displayed.
     

  5. Specify the path that contains the SERVER.EXE (Figure 3-18). This is on the Integrated PC Server that is held on the root directory of the E: drive. 

  6.  

     
     
     
     
     

    Figure 3-18. Server Boot Path

    * figure rv3z1858 not                displayed.
     

  7. You must specify which file groups to load. Press F10 to accept the default settings. 

  8.  

     
     
     
     
     
     
     

    Figure 3-19. File Group Selection

    * figure rv3z1859 not                displayed.
     

    The unmarked files were already copied to your NetWare server during server creation. You do not need to copy these files. 

    * figure note not displayed.
    Not all of the groups are shown in Figure 3-19. Additional groups can be displayed by scrolling down. 

     

     
     
     
     
     

    When installing NetWare-J (Japanese version of NetWare), you should select the groups 'NetWare System Files' and 'NetWare 4.1 Japanese Message Files' to replace NetWare versions of these files with the NetWare-J versions. 

    If a file already exists, you are asked if you want to overwrite that file as shown in Figure 3-20. If a file already exists, it was copied during creation. 

    Figure 3-20. Warning Message about Existing Files

+------------------------------------------------------------------------------+
|   NetWare Server Installation  4.1                   NetWare Loadable Module |
|                                                                              |
|  +--+----------------------------------------------------------------------+ |
|  |  |                  File Copy Status (Preliminary Copy)                 | |
|  +--+                                                                      | |
|  | ||   +--------------------------------------------------------------+   | |
|  | ||   +--------------------------------------------------------------+   | |
|  | ||                                  0%                                  | |
|  | |+----------------------------------------------------------------------+ |
|  | || Warning:  A file that is being installed would downgrade existing    | |
|  | || file SYS:\SYSTEM\NLS\4\ADSP.MSG to an older version. Currently       | |
|  | || installed software that uses this file may not work correctly if you | |
|  | || allow it to be overwritten. It probably should not be overwritten.   | |
|  | ||                                                                      | |
|  | || However, in the confirm box that follows, you may continue and       | |
|  +--+ overwrite this file anyway, if you wish. (INSTALL-4.1-451)           | |
|     |                                                                      | |
|     | Press <Enter> to continue.                                           | |
|     +---+--------------------------------------------------------------+---+ |
|     |   |                                                              |   | |
|     |   +--------------------------------------------------------------+   | |
|     +----------------------------------------------------------------------+ |
+------------------------------------------------------------------------------+



  1. Indicate whether you want to overwrite any existing files (Figure 3-21). Because several files are pre-installed with newer dates than those on the CD-ROM, you should normally not overwrite existing files. 

  2.  

     

    Figure 3-21. File Copy Status Display

+------------------------------------------------------------------------------+
|  NetWare Server Installation  4.1                   NetWare Loadable Module  |
|                                                                              |
|  +--+----------------------------------------------------------------------+ |
|  |  |                  File Copy Status (Preliminary Copy)                 | |
|  +--+                                                                      | |
|  | ||   +--------------------------------------------------------------+   | |
|  | ||   +--------------------------------------------------------------+   | |
|  | ||                                  0%                                  | |
|  | ||                                                                      | |
|  | ||   File group: +--------------------------------------+les            | |
|  | ||   Remote sourc|          Select an action:           |               | |
|  | ||   Destination +--------------------------------------+               | |
|  | ||   +-----------| |Continue and overwrite file ADSP.MSG+-----------+   | |
|  | ||   |->Installin| |Do not overwrite the file           |           |   | |
|  | ||   |->Installin| |Always overwrite newer files        |           |   | |
|  +--+   |->Installin|>|Never overwrite newer files         | Files"    |   | |
|     |   |(2/3).     | |Abort copying                       |           |   | |
|     |   |           +--------------------------------------+           |   | |
|     |   |                                                              |   | |
|     |   |                                                              |   | |
|     |   +--------------------------------------------------------------+   | |
|     +----------------------------------------------------------------------+ |
+------------------------------------------------------------------------------+



  1. When updating the NetWare boot directory, you receive a warning message indicating that the files cannot be opened (for example, NWOS2.EXE and NWOS2.MSG). These files are open for this procedure. Continue copying the next file as shown in Figure 3-22

  2.  

     

    Figure 3-22. File Copy Error Display

+------------------------------------------------------------------------------+
|   NetWare Server Installation  4.1                   NetWare Loadable Module |
|                                                                              |
|  +--+----------------------------------------------------------------------+ |
|  |  |                     File Copy Status (Main Copy)                     | |
|  +--+      +-----------------------------------------------------------+   | |
|  | ||      |xxx                                                        |   | |
|  | ||      +-----------------------------------------------------------+   | |
|  | ||                                  4%                                  | |
|  | ||                                                                      | |
|  | ||   File group: NetWare 4.1 OS/2 Server executable and boot files      | |
|  | ||   Source p+----------------------------------------------+           | |
|  | ||   Destinat| File "E:\NWOS2.EXE" cannot be opened. Error: |           | |
|  | ||   +-------| error code 32 (20 hex). (INSTALL-4.1-235)    +-------+   | |
|  | ||   |->Copyi|                                              |       |   | |
|  | ||   |->Copyi| Press <Enter> to continue.                   |       |   | |
|  +--+   |->Copyi+----------------------------------------------+       |   | |
|     |   |->Copying file "LANSHARE.LDI".                                |   | |
|     |   |->Copying file "MSM.NLM".                                     |   | |
|     |   |->Copying file "NWOS2.EXE".                                   |   | |
|     |   |->Copying file "NWOS2.EXE".                                   |   | |
|     |   +--------------------------------------------------------------+   | |
|     +----------------------------------------------------------------------+ |
+------------------------------------------------------------------------------+



  1. Press Enter and select Continue copying the next file for both files. 

  2. Figure 3-23. Continue Copying the Next File Display

+------------------------------------------------------------------------------+
|   NetWare Server Installation  4.1                   NetWare Loadable Module |
|                                                                              |
|  +--+----------------------------------------------------------------------+ |
|  |  |                     File Copy Status (Main Copy)                     | |
|  +--+    +-------------------------------------------------------------+   | |
|  | ||    |xxxx                                                         |   | |
|  | ||    +-------------------------------------------------------------+   | |
|  | ||                                  4%                                  | |
|  | ||                                                                      | |
|  | ||   File group: NetWare 4.1 OS/2 Server executable and boot files      | |
|  | ||   Source path:+--------------------------------------+               | |
|  | ||   Destination | An error occurred; select an action: |               | |
|  | ||   +-----------+--------------------------------------+-----------+   | |
|  | ||   |->Copying f| |Retry copying file NWOS2.EXE        |           |   | |
|  | ||   |->Copying f|>|Continue copying the next file      |           |   | |
|  +--+   |->Copying f| |Abort copying                       |           |   | |
|     |   |->Copying f+--------------------------------------+           |   | |
|     |   |->Copying file "MSM.NLM".                                     |   | |
|     |   |->Copying file "NWOS2.EXE".                                   |   | |
|     |   |->Copying file "NWOS2.EXE".                                   |   | |
|     |   +--------------------------------------------------------------+   | |
|     +----------------------------------------------------------------------+ |
+------------------------------------------------------------------------------+



  1. When file copying is done, press Enter. NetWare server installation is now complete. 

Step 10--Vary the Server Off, Then Back On
* figure task not displayed. 
To vary off the server: 
  1. Select option 3 on the NWSADM display shown in Figure 3-24

  2. Figure 3-24. Network Server Administration display

+--------------------------------------------------------------------------------+
| NWSADM                  Network Server Administration                          |
|                                                             System:   SYSTEMA  |
| Select one of the following:                                                   |
|                                                                                |
|      1. Configure a network server                                             |
|      2. Start a network server                                                 |
|      3. Stop a network server                                                  |
|      4. Work with network server storage spaces                                |
|                                                                                |
|     10. Change network server attributes                                       |
|     11. Change network server user attributes                                  |
|     12. Work with network server user enrollment                               |
|                                                                                |
|     20. Work with network server status                                        |
|     21. Work with network server aliases                                       |
|                                                                                |
|     30. Submit a network server command                                        |
|                                                                        More... |
| Selection or command                                                           |
| ===>  3                                                                        |
|                                                                                |
| F3=Exit   F4=Prompt   F9=Retrieve   F12=Cancel   F13=Information Assistant     |
| F16=AS/400 Main menu                                                           |
+--------------------------------------------------------------------------------+
  1. Enter the NWSD name you selected in "The initial server name (8 character maximum)"

  2.  

     

    Use option 2 on the Network Server Administration display to vary the server back on. These two menu options (Start and Stop a network server) use the VRYCFG command. 

Varying Off (Downing) the NetWare Server

The process to take down a NetWare server on the Integrated PC Server differs from a PC-based server. When using a PC-based NetWare server, you use the DOWN command to stop the server. When using an Integrated PC Server, you must vary off the network server description using the Vary Configuration (VRYCFG) command. 

During the vary off procedure, the QFPADOWN.NCF file is processed. copying files from the SYS: volume back to the E: drive. These files include NETINFO.CFG and AUTOEXEC.NCF. You can add statements to the QFPADOWN.NCF file, if needed, to allow copying of additional files, or to unload an NLM during the vary off procedure. The QFPADOWN.NCF file is located on SYS:SYSTEM. See "QFPADOWN.NCF" for more information about this file. 

* figure attn not displayed.
Do not use the DOWN command on an Integrated PC Server. Instead, use the VRYCFG command. 


During the vary off procedure, AS/400 runs the DOWN command closing any open files before the dismounting the volumes. In normal operations and for best recovery, the user's application, not the NetWare server, should close the files. 


Step 11--Create Network Server Storage Spaces

The preceding steps create a running server with storage on AS/400 for your NetWare SYS: volume. Now you can set up storage spaces for your user data. To do this, go to Chapter 8. "Managing Storage Spaces"


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