![]() |
** 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)
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
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
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
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,
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.
To remove the old 6506 entries from the WRKHDWRSC panel with the status
of 'Not detected', you can do the following:
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
4) Type option '4' against the old 6506 entry to remove the
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:
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:
3. Vary off all your NWSDs on your AS/400.Use the command
WRKCFGSTS *NWS to bring up a list,
4. Delete license program 5716SA2.
5. Reinstall license programs 5716SA2.
6. Apply all 5716-SA2 PTFs including SF34308.
7. Install the NetWare 4.11 CDROM image on your system:
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.
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:
NetWare tape support for OS/400 - additional information If you are using a 1/2" cartridge AS/400 tape drive (3590,
The error message you receive when you attempt the AS400TP
QFPANW.NLM:021-AS/400 tape device 'x' NOT allocated, lost
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
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
The automatic adjustments made for the Integrated PC Server are:
The following server types use the indicated pool storage:
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
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
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
*SPECIAL NOTE* Due to a problem with the tool, please interpret
|