** Last updated 15 April 1998 ** 

This file contains content for both II09535 (Part 1) and 
II10264 (Part 2) V3R2 Informational APARs. 

This informational APAR contains updated information regarding:     

   - Integration Services for FSIOP (5763SA2)
   - OS/400 Integration for Novell NetWare (5763SA3)
   - NetWare Enhanced Integration (5763SS1 - Option 25)

The Integrating AS/400 with Novell NetWare home page can be found by selecting the Software and Client/Server links from the AS/400 home page:

     http://www.as400.ibm.com/

Select the "Service and Support" category to access this, and related, Informational APARs on the World Wide Web.

NOTE: If your *BASE or *NETWARE NWSD is failing with the      following error messages, then a set of PTFs which upgrade the level of OS/2 Warp used on the FSIOP may help solve the problem.  All of these PTFs are included in cum tape C6191320.
        MSGCPI573F with error code x'E1000005'
        MSGCPI7E60 with which points to SRC65066224
If you are experiencing this problem, please load and apply the following set of PTFs.  They are very large and most likely not available via ECS.
      5763SA2 PTFs: SF30536, SF30537, SF30538, SF30539
      SF30540, SF30541, SF30542, SF30543, SF30544, SF30545
These PTFs should not be loaded if using NLV
      2962, 2986, 2987 or 2989.



Current PTFs for the FSIOP base and NetWare support:

PTF information is no longer retained in Info APARs. See the Service and Support page (as4nwss.htm) and select the Code Updates link.

Korean, Traditional Chinese and Simplified Chinese

These language versions of IntranetWare (NetWare 4.11) are not supported on the Integrated PC Server.

NetWare patches and fixes

There are NetWare 4.1 OS patches and updated Novell NetWare
Loadable Modules (NLMs) that are shipped along with Integration Services for FSIOP (5763SA2).  Refer to OS/400 Integration for Novell NetWare (SC41-3124) for more information on which patches have been included.  Hereafter, it will be the customer's responsibility to obtain any other NetWare patches or updates that are necessary.

Updates (newer versions of NLMs) from Novell usually go on the SYS volume.  To ensure new updates are accessed, change the 'search add 1 e: ' statement in the AUTOEXEC.NCF file to 'search add e: ', causing SYS: to be searched before E:.

Patches (NLMs loaded from STARTUP.NCF that fix the NetWare
kernel SERVER.EXE) from Novell need to go to the E: drive since this is the NetWare boot drive on the FSIOP.

Pentium Integrated PC Server

The new pentium Integrated PC Server is now available on V3R2 with feature code 1978. If you create a new server after this level of V3R2 is
installed, you do not need to do anything special to enable the pentium Integrated PC Server.

If you had an existing server on your AS/400, you need to do the following to upgrade ==EACH== server after you install the new pentium Integrated PC Server card for that server.  The server can be of type *BASE or *NETWARE. 
1) The resource number has changed.  Submit the command:
    WRKHDWRSC TYPE(*CMN)
    The pentium Integrated PC Server will have a resource type of 6616.  Record the resource name (CC04 for example).
 2) Issue the command:
    CHGNWSD NWSD(server) RSRCNAME(resource-name)
    where 'server' is the NWSD you are changing and 'resource-name' is    the new resource from step 1.
 3) For *NETWARE servers, do the following:
  a) Vary on the *NETWARE NWSD using the VRYCFG command
     or the WRKNWSCFG CFGTYPE(*NWS) command with option 1.
     Wait for the server to be active as shown on the WRKNWSSTS SVRTYPE(*NETWARE) panel.
  b) For NetWare 4.10 do the following steps.  Do not do this for a NetWare 4.11 server!!
    i) Submit the following command:
       SBMNWSCMD CMD('F: QFPNTWI NW410 SYSTEM QLANDR7')
                 SERVER(server-name)
                 SVRTYPE(*NETWARE) CMDTYPE(*NETWARE)
    ii) Vary off and back on the *NETWARE NWSD.  The NWSD
       is updated with new NLMs for the SYSTEM directory
       (TOKENTSM, ETHERTSM, MSM and NBI).
  c) Update the AUTOEXEC.NCF file on the SYS: volume  by adding the following lines after the
     LOAD F: QFPNTWI QFPPUTSY... lines.  Note that the lines
     should not be split when updating the AUTOEXEC.NCF file.
       LOAD F: QFPNTWI QFPPUTSY S=F: QFPNTWI IBMTRPO.LAN
           D=SYS:SYSTEM IBMTRPO.LAN
       LOAD F: QFPNTWI QFPPUTSY S=F: QFPNTWI IBMEANWS.LAN
           D=SYS:SYSTEM IBMEANWS.LAN

IntranetWare (NetWare 4.11)

To install NetWare 4.11 on the AS/400, you need PTFs:
   5763SA2 SF37536
   5763SA2 SF32061
   5763SA2 SF37481  (Only necessary for Japanese NetWare)
   5763SS1 SF34422
These PTFs are backward compatible and will also support
NetWare 4.10.


IntranetWare contains NetWare 4.11.

After the PTFs are installed, if you do not have any NetWare servers on the AS/400, use the installation process as documented in Chapter 2 of the OS/400 Integration for Novell NetWare (SC41-3124-01) book.  You cannot have both NetWare 4.10 and NetWare 4.11 on the AS/400 system at the same time.

If you already have NetWare 4.10 servers, you can upgrade to NetWare 4.11, but all NetWare servers on the AS/400 need be upgraded to NetWare 4.11 at the same time. The process to upgrade all of your NetWare 4.10 servers on your AS/400 to NetWare 4.11 is:


1. Before attempting to upgrade any server, verify that  each server has at least 70 megabytes available on the SYS: volume.  If you do not have that much space, the SYS: volume might fill up during the upgrade process.


Please create another NWS storage space and link it to your server.  Then use the INSTALL.NLM to make that storage space part of the SYS: volume.


2. On each NetWare 4.10 server on your AS/400,
 a) Map a drive on your PC to your NetWare 4.10 server
     and remove read attribute on INSTALL & NWSNUT NLM.
     for example:   MAP V:=servername SYS:
                    V:
                    CD SYSTEM
                    attrib -r INSTALL.NLM
                    attrib -r NWSNUT.NLM
  b) Copy the INSTALL.NLM and NWSNUT.NLM from the
     NetWare 4.11 CD to the SYS volume of your server:
       COPY E: PRODUCTS NW411 _ 411 SYSPRE INSTALL.NLM V:
       COPY E: PRODUCTS NW411 _ 411 SYSPRE NWSNUT.NLM  V:
      where E: is the remote CDROM drive and V: the SYS vol.
  c) Bring up RCONSOLE, UNLOAD NWSNUT and reload it using
       LOAD SYS: SYSTEM NWSNUT
  d) Using RCONSOLE, LOAD SYS: SYSTEM INSTALL, Copy Files
     option and copy the following from the NetWare 4.11 CD
     by specifying a remote path to your NetWare 4.11 CD:
       E: PRODUCTS NW411 INSTALL IBM OS2 XXX ENGLISH
     where E: is the remote drive and language is ENGLISH.
     'File "E: NWOS2.EXE" cannot be opened' error will
     occur.  Ignore this error and press Enter.
     Select 'Continue copy next file'.

 3. Vary off all NWSDs on your AS/400 using
    the command WRKCFGSTS *NWS and take option 2.

 4. Delete license program 5763SA2. Type 'GO LICPGM' and take option 12.
 
 5. Reinstall license programs 5763SA2.
    Type 'GO LICPGM' and take option 11.

 6. Apply all 5763-SA2 PTFs including SF31997 & SF32061.
    Ensure you also have PTF 5763-SS1 SF34422 installed.

 7. Install a temporary server using the INSNTWSVR command, and use that temporary server to do the workstation install as documented in Chapter 2 of the OS/400  Integration for Novell NetWare (SC41-3124-01) book.

 8. Vary off the temporary server and optionally delete the objects associated with it.  See the INSNTWSVR help text for the objects created for a NetWare server.

 9. Vary on the NWSDs that were upgraded to NetWare 4.11
    using the WRKCFGSTS *NWS option 1.
    After the NetWare 4.11 server is varied on, you will
    need to load NetWare 4.11 licenses on it.

To have the abend.log created when a NetWare 4.11 server abends, the following SET parameter needs to be added to the STARTUP.NCF file.
  SET DEVELOPER OPTION=OFF

One problem known about NetWare 4.11 on the AS/400 is not being able to dump the NetWare dump disk.  You can do the following as documented in the NetWare publication:
CALL QSYS/QFPDMPSS PARM(nwsdname *LINKNW)
but no dump file is created for the NetWare dump.

Machine storage pool size


When an Integrated PC Server is installed on your system, some memory is used in the machine storage pool (pool 1) for functions used on the Integrated PC Server.

The system value QFPRADJ indicates if automatic adjustment of the machine pool size should be made.  When the QFPRADJ value is non-zero, some adjustments are made for the Integrated PC Server, but you may need to make a manual adjustment by setting the QFPRADJ value to zero. More information about adjusting pool sizes is in the
WorK Management Guide, Performance Tuning chapter.

The automatic adjustments made for the Integrated PC Server are:
  6506 - 2.7MB adjustment for a 1 port card
         4.2MB adjustment for a 2 port card
  6616 - No adjustment made for the card.
With PTF 5763SS1 SF38883, the following adjustments
are made for the 6506 and 6616 cards:
  3.6MB adjustment for a 1 port card
  5.4MB adjustment for a 2 port card

The following server types use the indicated pool storage:
  *BASE servers (including Notes and FlowMark) use
        2.7MB plus 1.5MB per port.
  *NETWARE servers use 2.0MB plus 1.5MB per port.

Workstation Install Tips and Techniques

Ensure that you have not already done a Workstation Install for the language version (LANVER) specified on the INSNTWSVR command.  Only 1 Workstation install is required per language.  The server storage space where the NetWare files are stored is shared between all *NETWARE NWSDs of that language.

For Ethernet ODI configurations it is important that the STARTNET.BAT file is left in it's default format before you start the Workstation install.  If you change that file the installation utility may not be able to find configuration information, causing incorrect updates to the configuration files (NET.CFG, PROTOCOL.INI, and STARTNET.BAT ) which will cause connection problems (phase 2 will stop).  If you did
change your STARTNET.BAT file, ensure that the LSL and IPXODI statements have the .COM extension and the ODI driver statement does not use LOADHIGH.

If you are using PC DOS version 6.1 or 6.3 there is a problem when you connect to the FSIOP after you reboot the PC between phase 1 and phase 2.  Files (including QFP2.DAT) are not being downloaded to the PC.  The QFP.LOG file (history log) will have the following statement at the bottom: c: >xcopy z: qfpntwi wsinstal *.* c: qfptmp. Correct the problem by putting a copy of XCOPY.EXE from the DOS subdirectory into the root directory of the c: drive (i.e. copy c: dos xcopy.exe c: ).  Then reboot the PC.

If the NetWare Integration TSR hangs (NETINSTL.EXE) when you reboot between phase 1 and phase 2, ensure that no other PC on the LAN is attempting a Workstation Install at the same time.  There is a problem with the way the NETINSTL.EXE handles multiple NetBIOS addresses.

Other Tips, Techniques and Restrictions

OS/400 Integration Products for NetWare are not supported on V3R6.

Networking Extensions, 5733-SA1 is incorporated into V3R2 and is not a prerequisite product for installing NetWare.

New versions of products Integration Services for FSIOP, 5763-SA2, and OS/400 Integration for Novell NetWare, 5763-SA3, exists for V3R2.  The V3R1 versions, which had product IDs starting with 5733, can NOT be used.  You may slip install the new products over the old products.

Before installing Integration Services for FSIOP, 5763-SA2, you must ensure that all *NETWARE and *BASE type network server descriptions are in a varied off state.

A minimum of 32MB of memory is required to run Novell NetWare 4.1 on the FSIOP.  A 1 or 2 port FSIOP card can be used.  Notes:
1) If you want to run NetWare for SAA on the FSIOP and
   connect to the same AS/400, you must use a 2 port FSIOP
   or a separate token-ring or Ethernet card.

2) If you want NetWare TCP/IP to communicate with OS/400 TCP/IP on the same AS/400, you must use a 2 port FSIOP or  a separate token-ring or Ethernet card.

If you are experiencing Ethernet communication failures with AS/400, the problem may be caused by the Multiport Transport/ Hub not conforming to Ethernet Standards (ISO/IEC 8802.3).  Refer to the informational APARs II08464 and II08473 for more information.

OS/400 Verify TCP/IP Connection (PING) may fail if an internet address is specified that corresponds to a line associated with a *NETWARE network server description (NWSD).

The OS/400 Change TCP/IP Attributes option to enable datagram forwarding does not apply to lines associated with a *NETWARE network server description (NWSD).  TCP/IP packets entering the AS/400 via a line associated with a *NETWARE network server description (NWSD) will not be forwarded to other TCP/IP interfaces by OS/400.

In order to complete Novell product certification testing, TOKENTSM.NLM version 2.61 was required.  It is recommended
that you obtain TOKENTSM.NLM version 2.61 or higher from
Novell.

If you decide to configure and use AS/400 local IPX support, you must first install a Novell NetWare 4.1 license before AS/400 local IPX support can be activated.  After installing the license, you must start or restart IPX support using the STRIPX command to activate the local IPX connection.

If you decide to configure the NetWare server to support protocols other than IPX (such as TCP/IP), you must use the NetWare INETCFG utility.  Note that when using the INETCFG utility, you may see a red warning message displayed indicating that a configuration file may be corrupted.  You can ignore this message since this file was updated by an
AS/400 program without using the INETCFG utility.  Refer to page 4-12 in publication SC41-3124 for additional hints concerning using the INETCFG utility.

When doing WRKNWSSTS option 5 (display details), you will notice the version will always show 4.10, even if NetWare 4.11 version is installed.  This will be corrected in V3R7.

Backing up your NetWare data files and NDS is recommended.
The following are some recommendations concerning backing and recovering your data when using OS/400 Integration for Novell NetWare.

- When using the OS/400 RST command to restore an entire storage space, a temporary copy of the storage space is made before replacing the original storage space.  For example, restoring a 1GB storage space requires 1GB of available DASD for use by the RST command.

- To perform incremental backup of data, use of a NetWare backup utility, such as SBACKUP, to backup data to a tape device attached to a PC based server is required. Incremental backup of data to AS/400 media is not currently supported by OS/400 Integration for Novell NetWare.

- To perform backup of entire volumes of data for disaster recover, you can use OS/400 commands (SAV) to backup storage spaces.  In this situation, it is recommended that user data not be stored in SYS: but instead stored in a separate volume in a separate storage space.  Separate storage spaces allow recover of user data volumes without changes to NDS which is stored on SYS:  If NDS needs to be recovered, and there is not a replica of NDS in the network to recover
from, NDS can be recovered by restoring SYS:.  Refer to the OS/400 Integration for Novell NetWare manual (SC41-3124) for details on saving and restore storage spaces.