Chapter 5. Configuration Objects and Files

When you create the NetWare server with the Install NetWare Server (INSNTWSVR) command, several objects are created on the AS/400 as discussed in "Step 3--Run the Install NetWare Server (INSNTWSVR) Command". This chapter provides information on which objects and configuration files are used. It also provides information on how they are related. 

When using NetWare on the Integrated PC Server, the following objects are needed: network server descriptions, IPX descriptions, line descriptions, IPX circuits, and storage spaces. Depending on your intended use, you may also need other objects such as controllers or devices. The centerpiece of these AS/400 objects is the network server description as shown in Figure 5-1

Figure 5-1. OS/400 Configuration Objects

                         +----------------+
  +----------------+     |                |      +-------------+
  | Network Server |     | Network Server |      |     IPX     |
  | Storage Space  +-----+   Description  +------+ Description |
  | System Volume  |     |     NWCC08     |      |   NWCC08    |
  +----------------+     |                |      +-------------+
   +--------------+      +----+---+-------+
   | OS/2 Storage |           |   |
   |    Spaces    +-----------+   |
   +--------------+               |
          +-----------------------+-------------+
          |                                     |
   +------+------+                      +-------+-----+
   | Token-Ring  |                      |  Ethernet   |
   |    Line     +------+  +------------+    Line     |
   | Description |      |  |            | Description |
   |  NWCC801    |      |  |            |  NWCC0802   |
   +------+------+      |  |            +--------+----+
    +-----+-----+       |  |      +---------+----+----+---------+
+---+---+   +---+----+  |  |  +---+---+ +---+---+ +---+---+ +---+---+
|  IPX  |   |  IPX   |  |  |  |  IPX  | |  IPX  | |  IPX  | |  IPX  |
|Circuit|   |Circuit |  |  |  |Circuit| |Circuit| |Circuit| |Circuit|
|*SNAP  |   | *SSAP  |  |  |  | *SSAP | | *SNAP | |*ETHV2 | |*ETHNTW|
+-------+   +--------+  |  |  +-------+ +-------+ +-------+ +-------+
          +-------------+  +--------------------+
          |                                     |
   +------+-------+                      +------+-------+
   | Controller   |                      | Controller   |
   | Description  |                      | Description  |
   |              |                      |              |
   +------+-------+                      +------+-------+
          |                                     |
   +------+-------+                      +------+-------+
   |   Device     |                      |   Device     |
   | Description  |                      | Description  |
   |              |                      |              |
   +--------------+                      +--------------+



OS/400 Server Configuration Objects

The Install NetWare Server (INSNTWSVR) command creates all of the necessary OS/400 configuration objects needed to run NetWare on the Integrated PC Server. Figure 5-2 shows the relationship between values that are specified on the INSNTWSVR command and values that are used for the related network server, line description, IPX description, and IPX circuit objects. 

Figure 5-2. INSNTWSVR and OS/400 Configuration Objects

+---------------------------------------+    +-----------------------+
| INSNTWSVR                             |    |CRTNWSD                |
|   NWSD(NWCC08)------------------------+----+NWSD(NWCC08)           |
|   RSRCNAME(CC08)----------------------+----+-RSRCNAME(CC08)        |
|   MSGQ(*JOBLOG)                       |    |  TYPE(*NETWARE)       |
|                                       |    |  IPX(NWCC08)|---------+------+
|                                       |    |  MSGQ(*JOBLOG)        |      |
|                                       |    +-----------------------+      |
|                                       |    +-----------------------+      |
|                                       |    |CRTLINTRN              |      |
|                                       |    |  LIND(NWCC0801)-------+-----+|
|                                       |    |  RSRCNAME(*NWSD)      |     ||
|                                       |    |  NWS(NWCC08 1)        |     ||
|                                       |    |  SSAP(*SYSGEN)        |     ||
| PORT1                                 |  +-+-LINESPEED(16M)        |     ||
|   Line type:              *TRN16M-----+--+ |  MAXFRAME(1994)       |     ||
|   Local adapter address:  400044444444+----+-ADPTADR(400044444444) |     ||
|   IPX circuit information:            |    +-----------------------+     ||
|     IPX network number      429F2001--+---+    +-----------------------+ ||
|     Frame type              *SSAP-----+--+|    |ADDIPXCCT              | ||
|                                       |  ||    |  CCTNAME(NWCC0801)    | ||
|                                       |  ||    |  LIND(NWCC0801)|------+-+|
|                                       |  |+----+-IPXNETNBR(429F2001)   |  |
|                                       |  +-----+-FRAMETYPE(*SSAP)      |  |
|                                       |        +-----------------------+  |
|                                       |    +-----------------------+      |
|                                       |    |CRTLINETH              |      |
| PORT2                                 |    |  LIND(NWCC0802)|------+-----+|
|   Line type:              *ETH        |    |  RSRCNAME(*NWSD)      |     ||
|                                       |    |  NWS(NWCC08 2)        |     ||
|                                       |    |  SSAP(*SYSGEN)        |     ||
|   Local adapter address:  020000000020+----+-ADPTADR(020000000020)|      ||
|                                       |    +-----------------------+     ||
|                                       |        +-----------------------+ ||
|                                       |        |ADDIPXCCT              | ||
|                                       |        |  CCTNAME(NWCC0802)    | ||
|   IPX circuit information:            |        |  LIND(NWCC0802)|------+-+|
|     IPX network number      429F2002--+--------+-IPXNETNBR(429F2002)   | ||
|     Frame type              *ETHV2----+--------+-FRAMETYPE(*ETHV2)     | ||
|     IPX network number      429F2003--+---+    +-----------------------+ ||
|     Frame type              *SSAP-----+--+|    +-----------------------+ ||
|                                       |  ||    |ADDIPXCCT              | ||
|                                       |  ||    |  CCTNAME(NWCC0803)    | ||
|                                       |  ||    |  LIND(NWCC0802)|------+-+|
|                                       |  |+----+-IPXNETNBR(49F2003)    |  |
|                                       |  +-----+-FRAMETYPE(*SSAP)      |  |
|                                       |        +-----------------------+  |
|                                       |    +-----------------------+      |
|                                       |    |CRTIPXD                |      |
|                                       |    |  IPXD(NWCC08)|--------+------+
|  IPXNETNBR(DDDDFFFF)------------------+----+-IPXNETNBR(DDDDFFFF)   |
|                                       |    +-----------------------+
+---------------------------------------+



Network Server Description

The network server description (NWSD) is the object you vary on and off to start and stop the NetWare server. The NWSD name, resource name, online status, language, country code, message queue name, and the information text are gathered from information that is specified on the INSNTWSVR command. 

If a local IPX connection is not needed, the LCLIPXCNN parameter value should be *NO. If *YES is specified, but local IPX is not active at the time of the vary on, a warning message is issued to indicate that the vary on completed successfully. However, local IPX is not active and should be started using the Start IPX (STRIPX) command. 

Line Description

The name of the line description (LIND parameter) is the name of the NetWare server plus 01 for the line on port 1 and plus 02 for the line on port 2. For example, if the name of your NetWare server is HQSVR1, the name of the line description will be HQSVR101 for the line on port 1. However, if a line description with that name already exists, the number that is appended to the network server continues to be incremented up to 99. 

The type of line description, the local adapter address, the maximum frame size, and the line speed are used to update the NETINFO.CFG file. 

IPX Circuit

You must have an IPX circuit (IPXCCT) for each frame type to be supported with each of the line descriptions you are configuring. For a token-ring line description, this could be a circuit for *SSAP, *SNAP, or both. For an Ethernet line description, this could be a circuit for *SSAP, *SNAP, *ETHV2, *ETHNTW, or any combination. The IPX network number and the frame type of the IPXCCT is used to bind IPX to the network with the appropriate frame type. 

IPX Description

Every NetWare server on AS/400 has an associated IPX description (IPXD). If you are using IPX on the AS/400 in addition to IPX for the NetWare server, you must also have an IPXD for the AS/400. This IPX description is totally independent from the NetWare server. 

The IPX internal network number is the IPX number of your NetWare server. Use this number with the RCONSOLE command if your server is not shown in the list of available servers. 

If you want to change the IPX internal network number, you must change the value in the AUTOEXEC.NCF file on the SYS: volume. 

* figure tip not displayed.
If you use the default value for the IPX internal network number (IPXNETNBR parameter), the number is generated randomly. We recommend that you note the value generated so that you can reference it later. You may need to locate the NetWare server using this value rather than the server name. 
Storage Space

By default you have one NetWare storage space added to your network server description. This space is used for your NetWare server system volume. The name of the storage space defaults to the name of your network server description. Storage spaces also exist for the OS/2 operating system. See Chapter 8. "Managing Storage Spaces" for more information on the storage spaces that are associated with OS/2. 


OS/2 Server Configuration Files

The OS/2 operating system on the Integrated PC Server uses configuration files such as CONFIG.SYS, STARTUP.CMD, PROTOCOL.INI, and SERVICE.INI when it activates the NetWare server. These files are called Base server configuration files

* figure note not displayed.
It is NOT possible to change any of the base configuration files. 
The Novell NetWare server uses configuration files such as STARTUP.NCF, AUTOEXEC.NCF, NETINFO.CFG, and NET.CFG when it is activated. These files, called NetWare server configuration files, are discussed in the following sections. 

For more information on configuration, see the following: 

STARTUP.NCF

STARTUP.NCF is on the OS/2 E:\ drive. It contains the disk device driver, some NetWare SET statements, and the load of a NetWare fix package. If you have to change this file, use the INSTALL utility from a remote console screen. 

* figure note not displayed.
Notes: 
  • Do not remove the load statements for PM410 and DIAG410 NLMs from STARTUP.NCF. 
  • Do not change or unload the disk device driver (QFPLDISK.DSK). 
  • Do not change or remove the TTS** BACKOUT FLAG=ON statement. 
  • The Maximum Physical Receive Packet Size is updated by OS/400 each time you vary on the Integrated PC Server. It's size is related to the MAXFRAME parameter of your Integrated PC Server line description. That is, the Maximum Physical Receive Packet Size is usually 32 bytes more than the MAXFRAME value on the line description for token-ring lines. 

  • For example, to set the Maximum Physical Receive Packet Size to 4202 in the STARTUP.NCF file, set the MAXFRAME value on the token-ring line description to 4170. 

AUTOEXEC.NCF

AUTOEXEC.NCF is on your NetWare server system volume. It contains the base settings of the NetWare server. For example, it contains the server name and NDS information. 

* figure note not displayed.
To ensure the NetWare server operates properly, do not remove any of the existing LOAD statements or the sys:etc\initsys.ncf' statement in the AUTOEXEC.NCF file. These statements ensure that the NetWare server is connected to the LAN correctly and that RCONSOLE support is started. 
Figure 5-3. AUTOEXEC.NCF
set Time Zone = CST6CDT

set Daylight Savings Time Offset = 1:00:00

set Start Of Daylight Savings Time = (APRIL SUNDAY FIRST  2:00:00 AM)

set End Of Daylight Savings Time = (OCTOBER SUNDAY LAST  2:00:00 AM)

set Default Time Server Type = SINGLE

set Bindery Context = OU=as400.O=nw

; make sure that file server name is valid (<=47 chars)

file server name NWCC08

ipx internal net DDDDFFFF

search add 1 e:\

search add f:\nwos2

search add f:\QFPNTWI

search add f:\QFPNTWI\NW410

load F:\QFPNTWI\NW410\AUTODUMP -F=I:\AUTODUMP.IMG -D=HDISK

load F:\QFPNTWI\QFPANW

load F:\QFPNTWI\QFPAMON


mount all

LOAD CONLOG MAXIMUM=100

LOAD F:\QFPNTWI\QFPPUTSY S=E:\NETINFO.CFG D=SYS:ETC\NETINFO.CFG

LOAD F:\QFPNTWI\QFPPUTSY S=F:\QFPNTWI\IBMMPCFS.LAN D=SYS:SYSTEM\IBMMPCFS.LAN

LOAD F:\QFPNTWI\QFPPUTSY S=F:\QFPNTWI\QFPAILAN.LAN D=SYS:SYSTEM\QFPAILAN.LAN

LOAD F:\QFPNTWI\QFPPUTSY S=F:\QFPNTWI\HDDLAN1.NLM  D=SYS:SYSTEM\HDDLAN1.LAN

LOAD F:\QFPNTWI\QFPPUTSY S=F:\QFPNTWI\HDDLAN2.NLM  D=SYS:SYSTEM\HDDLAN2.LAN

; Network driver LOADs and BINDs are initiated via

; INITSYS.NCF. The actual LOAD and BIND commands

; are contained in INITSYS.NCF and NETINFO.CFG.

; These files are in SYS:ETC.

sys:etc\initsys.ncf



* figure tip not displayed.
You should not use the AUTOEXEC.NCF directly as your main batch file because the default values for this file cannot be reset. For this reason, start your own customized batch file at the end of the AUTOEXEC.NCF file. Locate this file on the E: drive so it can be easily changed or removed if the NetWare server does not start. For example, you can name the file E:\AUTOSTR.NCF then use the NetWare EDIT.NLM to change it ( LOAD EDIT E:\AUTOSTR.NCF). 
  • You can change the NetWare server name by changing its value in the AUTOEXEC.NCF file. Ensure that you have a valid server name statement in your file. 
  • If you are using the RCONSOLE list of servers and do not see the name of your server listed, you can use the IPX internal network number to select the server. To find the IPX number, use the Display IPX Description (DSPIPXD) command on the AS/400 to show IPX description associated with your network server description. 
  • Do NOT make any changes to the LOAD F:\QFPNTWI\QFPPUTSY ... statements. 
  • Do NOT change or remove the sys:etc\initsys.ncf statement. 
  • If you want to switch off the message logging on the AS/400, use the CHGNWSD command to change the MSGQ parameter value to *NONE on the network server description. This change does not stop the exchange of messages between the NetWare server and OS/400. If you want to stop the exchange of messages to save system resources, unload QFPAMON in your own batch file. 
  • If you do not get all the needed information in your NetWare console log, increase the value specified on the LOAD CONLOG MAXIMUM= statement in your AUTOEXEC.NCF file. 
  • An easy way to change the performance value between the OS/2 operating system and NetWare is to add the following line in your AUTOEXEC.NCF file: 
  • SET PERFORMANCE TUNING n
    where n is a value from 1 to 10. See "Performance and Availability Considerations"
NETINFO.CFG

NETINFO.CFG is the configuration file that contains all the network information. Use the NetWare INETCFG utility from a remote console screen to change this file. NETINFO.CFG is located on the NetWare server system volume in the ETC directory. 

* figure note not displayed.
Notes: 
  • Unlike a PC-based server, the NETINFO.CFG file is partially overwritten each time the Integrated PC Server is varied on. 
  • This file was created by the Internetworking Configuration Console. It is intended to be modified ONLY by the configurator (INETCFG.NLM). Tampering with this file may cause severe malfunctioning of the system. The configurator checks for tampering and issues a warning if tampering is detected. 
  • Do not change the AUTOEXEC.NCF or NETINFO.CFG files manually to add other protocols such as TCP/IP. Use the INETCFG NLM to change your NETINFO.CFG file instead. 
* figure tip not displayed.
Tips: 
  • You may see a red warning message on the RCONSOLE display indicating that the NETINFO.CFG has changed. Ignore this message. This message indicates that the file was changed during the last vary on. 
  • Do not change or remove any of the BOARD statements. 
  • Do not change IPX information from RCONSOLE. Use the AS/400 Change IPX Description (CHGIPXD) command to change the IPX information. 
  • Change the default RCONSOLE password, which is the server name, immediately after you have set up the server. 
  • Do not deactivate the RCONSOLE facility. The Integrated PC Server does not have a local console screen. RCONSOLE may be needed later. If you want to temporarily lock the console, use the MONITOR utility to lock it. 
NET.CFG

The NET.CFG file is used as the NetWare for OS/2 configuration file. This file is on the server C: and E: drives. Most of the parameters are used to set priorities between OS/2 and NetWare. An example of this file is shown in Figure 5-4

Figure 5-4. NET.CFG

  NETWARE FOR OS/2

  PERFORMANCE TUNING 8

  INITIALIZATION SCREEN DELAY 1

  BASE SERVER MEMORY 6

  SERVER MEMORY 51

  AUTOMATIC MEMORY SHARING OFF

  BLOCK ALLOCATION SIZE 64

Because the C: drive is read-only, this file cannot be edited. Editing the file on the E: drive has no effect. 
Performance Tuning 
This parameter specifies how much processing time is allocated to NetWare. This value is not used. The NetWare server is configured with a special tuning value for optimal performance in the AS/400 environment. 
Initialization Screen Delay 
This setting specifies the number of seconds you want the NetWare information screen to display during the OS/2 boot. 
Base Server Memory 
This setting allocates a base amount of memory (in MB) for the server at boot time. 
Server Memory 
This setting is used to set the maximum amount of memory (in MB) that NetWare can allocate from OS/2. 
Automatic Memory Sharing 
This setting deactivates the automatic memory sharing (it is active as a default). When automatic memory sharing is active, the system determines the proper amounts of memory for the NetWare and OS/2 as the server is running. 
Block Allocation Size 
This setting specifies the number of memory pages you want to include in a total block of memory that NetWare allocates from OS/2. One memory page is equal to 4 KB of memory. 
Allocate Memory 
This setting requests that memory allocated from OS/2 for the server be allocated above or below the first 16 MB. 
* figure tip not displayed.
For information on resetting NetWare server configuration files, see Chapter 8. "Managing Storage Spaces"
QFPADOWN.NCF

The QFPADOWN.NCF file is run when the OS/400 network server description is varied off. Figure 5-5 shows the initial contents of QFPADOWN.NCF. You can add additional commands to this file that you want to run when the network server description is varied off. Add the lines to the bottom of the file, if needed. 

Figure 5-5. QFPADOWN.NCF
LOAD F:\QFPNTWI\QFPGETSY S=SYS:\ETC\NETINFO.CFG D=E:\NETINFO.CFG

LOAD F:\QFPNTWI\QFPGETSY S=SYS:\SYSTEM\AUTOEXEC.NCF D=E:\AUTOEXEC.SYS

LOAD F:\QFPNTWI\QFPGETSY S=SYS:\ETC\CONSOLE.LOG D=E:\CONSOLE.LOG

LOAD F:\QFPNTWI\QFPGETSY S=SYS:\VOL$LOG.ERR D=E:\VOL$LOG.ERR

LOAD F:\QFPNTWI\QFPGETSY S=SYS:\TTS$LOG.ERR D=E:\TTS$LOG.ERR

LOAD F:\QFPNTWI\QFPGETSY S=SYS:\SYSTEM\SYS$LOG.ERR D=E:\SYS$LOG.ERR

LOAD F:\QFPNTWI\QFPGETSY S=SYS:\SYSTEM\QFPADOWN.NCF D=E:\QFPADOWN.SYS



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