** Last updated 15 April 1998 ** 

This file contains content for both II09667 (Part 1) and II10265 (Part 2) V3R7 Informational APARs. 

This informational APAR contains information information regarding:

   - Integration Services for FSIOP (5716SA2)
   - OS/400 Integration for Novell NetWare (5716SA3)
   - NetWare Enhanced Integration (5716SS1 - 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.

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.

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.

Novell NetWare OS Updates for Enhanced NetWare Integration:

The following NetWare OS (4.10 and 3.12) update packages from Novell contain fixes required for the Enhanced NetWare Integration NLM. Obtain the latest revision level for your NetWare release.  In addition to these packages, IBM strongly recommends that your servers be upgraded to the latest patch and NLM file update level.

Update file   Description
-----------   ----------------------------------------------
LIBUPn        CLIB and DSAPI updates
STRTLn        STREAMS, TLI, SPXS, and IPXS NLM updates

Pentium Integrated PC Server

The new pentium Integrated PC Server is now available with V3R7 with a production date of 2/28/97 or later, or cumulative PTF package C7029370 or later applied on V3R7. If you create a new server after this level of V3R7 is installed or you have an AS/400 Advanced Model 150,
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(*LCLNTW)
    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 if they are not already there.  Note that the lines should not be split when updating 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

To remove the old 6506 entries from the WRKHDWRSC panel with the status of 'Not detected', you can do the following:
  1) Issue the command:  STRSST

  2) Choose option 1 to Start a Service tool, option 7 for Hardware Service manager and then option 2 for Logical hardware resources. Select option 1 for System bus resource

  3) You should see all IOP resources on this screen. Move the
     cursor to the old 6506 entry which now shows up as
     'Not detected' or 'Unknown'.

  4) Type option '4' against the old 6506 entry to remove the
     entry from system hardware resources. Press enter.
  5) Confirm the remove request on the confirmation screen.
  6) The old '6506' resource entry should now be removed. Exit
     from the service tools.

Korean, Traditional Chinese and Simplified Chinese

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

IntranetWare (NetWare 4.11)
 

To install NetWare 4.11 on the AS/400, you need PTFs:
   5716SA2 SF34308
   5716SA2 SF37273  (Only necessary for Japanese NetWare)
   5716SA3 SF39033
These PTFs are backward compatable 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 INSNTWSVR command and install NetWare 4.11.  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 on your AS/400, you can upgrade to NetWare 4.11, but all NetWare servers on the AS/400 need to 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: volumn 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 thatstorage space part of the SUS: 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 your NWSDs on your AS/400.Use the command       WRKCFGSTS *NWS to bring up a list,
    and take option 2 to vary off the server.

 4. Delete license program 5716SA2.
    Type 'GO LICPGM' and take option 12.

 5. Reinstall license programs 5716SA2.
    Type 'GO LICPGM' and take option 11.

 6. Apply all 5716-SA2 PTFs including SF34308.
    Ensure you also have 5716-SA3 SF37249 PTF as well.

 7. Install the NetWare 4.11 CDROM image on your system:
    INSNTWSVR NWSD(*CPYONLY) NTWSRCDIR('/QOPT/NW411')
    where '/QOPT/NW411' is the NetWare 4.11 CDROM
    in the AS/400 CDROM drive.

 8. Vary on your NetWare servers (WRKCFGSTS option 1).

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.

NetWare tape support for OS/400 - additional information

If you are using a 1/2" cartridge AS/400 tape drive (3590,
3570) with the NetWare tape support for OS/400, do NOT load
the tape immediately before you ALLOCATE or DEALLOCATE the
drive from the NetWare console (RCONSOLE).

The error message you receive when you attempt the AS400TP
ALLOCATE x or AS400TP DEALLOCATE x operation is:

QFPANW.NLM:021-AS/400 tape device 'x' NOT allocated, lost
connection with OS/2 device driver VT400.SYS.

This will cause the tape drive to hang and it will not be useable from NetWare or AS/400.  To recover the tape drive you must vary off the NetWare server where the ALLOCATE or DEALLOCATE was issued.

To assure that this condition does not occur, follow these steps to ALLOCATE the drive:

1) Vary on the tape drive from OS/400
2) Vary off the tape drive from OS/400
3) DO NOT load the tape drive with a tape
4) ALLOCATE the drive from NetWare
5) Now load the tape in the tape drive

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
  2850 - 1.5MB adjustment for the card.
  6616 - No adjustment made for the card.
With PTF 5716SS1 SF38870, the following adjustments are made for the 6506, 6616 and 2850 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.

Other Tips, Techniques and Restrictions

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 FSIOPand 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 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.

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 recovery, you can use OS/400 command (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 Integrating AS/400 with Novell NetWare (SC41-4124) for details on saving and restore storage spaces.

*SPECIAL NOTE* Due to a problem with the tool, please interpret
all vertical bars ("|") as backslashes in directory names.