This is a replicated copy of AS/400's NetWare Integration Adds TCP/IP Support. It is provided for completeness and avoid "broken" link.
AS/400 Starter Kit
CL Style Guide
Cobol Style Guide
RPG Style Guide
NEWS & ANALYSIS
BOOKS & EDUCATION
AS/400's NetWare Integration Adds TCP/IP Support
AS/400 sites that also run NetWare are getting some additional help with network administration from IBM. With V4R3, IBM released a new version of its OS/400 Enhanced Integration for Novell NetWare licensed program that adds several key enhancements. Chief among them are support for NetWare 5.0, which allows native IP as well as Novell's proprietary IPX protocol, and the ability to support a network including an AS/400 and servers running different versions of NetWare. Let's look at the latest version of the Enhanced NetWare Integration product and its configuration and administration.
What's New in Enhanced Integration?
V4R3's Enhanced NetWare Integration includes the support for IPX-based NetWare servers (pre-5.0 versions) found in earlier versions of the Enhanced Integration product. (For more information about V3R7's Enhanced NetWare Integration, see "AS/400 and NetWare: Better Together Since V3R7," March 1998.) And V4R3 Enhanced NetWare Integration lets an AS/400 share resources with NetWare 5.0 servers as well as NetWare 3.12 IPX bindery servers, NetWare 4.x IPX Novell Directory Services (NDS) servers, and NetWare 4.x servers with the NetWare/IP gateway (which lets a NetWare IPX server connect to a network via TCP/IP).
To obtain OS/400 Enhanced Integration for Novell NetWare (product number 5769-SS1), you order it from IBM as a separate licensed program, feature 2246. Enhanced Integration provides a variety of NetWare services for AS/400 operators. The product lets AS/400 users access NetWare file systems and share NetWare-managed printers and provides features that simplify network administration, such as user profile propagation.
The new features in Enhanced NetWare Integration bring these benefits to administrators and end users:
・Network administration is simplified because user profiles and passwords are created on the AS/400 and propagated to other NetWare servers on the network, regardless of which network protocol is used.
・An administrator can manage NetWare user connections and disk volumes from one location - the AS/400.
・The NetWare authentication entry stores all the necessary user IDs and passwords for logging in to NetWare servers, so users can sign on to NetWare servers without having to manually enter their passwords. (For more information about authentication, see "AS/400 and NetWare: Better Together Since V3R7.")
・AS/400 users can access data in NetWare 3.12 servers and NDS-based NetWare 4.x and NetWare 5.0 servers via the AS/400 integrated file system (IFS).
・AS/400 users can share NetWare TCP/IP or IPX network printers. Print files are sent from an AS/400 output queue to a printer queue managed by a NetWare server.
The V4R3 Enhanced NetWare Integration product employs the basic client/server structure of previous releases. The product consists of two logical components: a licensed program that runs on the AS/400 (the client part) and an optional NetWare Loadable Module (NLM) that you can install on NetWare servers in your network to be remotely managed from the AS/400 (the server part). Because the V4R3 enhancements are downward compatible, you can have a network that includes AS/400s and NetWare servers running different versions of Enhanced NetWare Integration.
If you want to connect your AS/400 to NetWare 5.0 or NetWare/IP servers, you must make sure TCP/IP is configured on the AS/400. One way to configure TCP/IP on the AS/400 is to use Operations Navigator (OpNav); refer to OpNav's online help for step-by-step instructions. You can also use the Configure TCP/IP (CFGTCP) command to configure an AS/400 TCP/IP connection. For more information about configuring TCP/IP, see OS/400 TCP/IP Configuration and Reference (SC41-5420). Once TCP/IP is configured, use the PING command on the AS/400 to verify that the AS/400 and NetWare server(s) can communicate (i.e., ping each server on the network).
The next AS/400 configuration task is to use the CHGNWSA (Change Network Server Attributes) command to enter the names of the TCP/IP-based NetWare servers and specify the TCP/IP port for Enhanced NetWare Integration. The CHGNWSA command was added to OS/400 for users of IBM's LAN Server for OS/400 product and was extended for Enhanced NetWare Integration use. In V4R3, CHGNWSA has been extended to accept IP names of NetWare servers.
・Prompt control - with *NETWARE, displays only parameters relevant to NetWare; with *ALL, displays all parameters for all types of network attributes.
・Default server type - set to *NETWARE if most users will use NetWare servers.
・NDS tree - the default NDS tree the AS/400 uses. Specify the tree that your AS/400 users use most often when accessing the network.
・NDS context - this is the complete path name for the NDS context associated with the NDS tree specified above. You define this context here so that other CL commands, such as WRKNTWAUTE (Work With NetWare Authentication Entries), can use a context with *NWSA as parameter. If you don't set an NDS context, the CHGNWSA command uses the default, *ROOT.
・NetWare TCP/IP port - the port that NetWare TCP/IP uses. You can change the default value of the TCP/IP port from 20199 to another value if port 20199 is used for another TCP/IP application on your network. If you change the default port value, you must specify the keyword /TCP=n on the LOAD command when loading the Enhanced NetWare Integration NLM, where n is the new port value specified on the CHGNWSA command (more about the LOAD command and keywords later). You must set values for the NetWare TCP/IP port and NetWare/IP server list parameters to enable AS/400 users to access NetWare servers running TCP/IP.
・NetWare/IP server list - the list of NetWare TCP/IP servers (i.e., the NetWare servers' IP names). Enhanced NetWare Integration uses this list to find out where the TCP/IP NetWare servers are on the network. (This is the only place you need to enter NetWare servers' TCP/IP names.) After identifying the NetWare servers from this list, Enhanced NetWare Integration internally stores information about the servers by their NetWare server names and present and previous TCP/IP and IPX addresses.
・NDS tree list - this list specifies default NDS tree information used by Enhanced NetWare Integration to enroll AS/400 user profiles in the NDS tree. Each entry in the list contains an NDS tree name and a list of default attributes associated with that tree. If there are no entries in the list, Enhanced NetWare Integration will enroll no AS/400 profiles in the network.
・NetWare 3.12 server list - lets you specify a list of default NetWare 3.12 servers for user enrollment.
Configuring TCP/IP NetWare Servers
Your next step is to install the Enhanced NetWare Integration NLM on each server in the network that's managed from the AS/400 (i.e., each server in the NDS tree and each NetWare 3.12 server). Remote management from the AS/400 is an optional feature - you need not use it if you already administer your NetWare servers using native NetWare administration tools. The Enhanced NetWare Integration NLM is shipped with the Enhanced Integration product, but the latest version of the NLM is also available on IBM's Enhanced Integration Web site, http://www.as400.ibm.com/netware. The site provides detailed instructions for installing the NLM.
There are two different Enhanced NetWare Integration NLMs: one for NetWare 3.12 and one for NetWare 4.x and 5.0. When you install an NLM, you must choose the network protocol your servers will use - IPX or TCP/IP.
To install the Enhanced NetWare Integration NLM, you use the standard NetWare console LOAD command to load the appropriate version of the NLM. For NetWare 4.x or NetWare 5.0, use the LOAD command with AS4NW410; for NetWare 3.12, use LOAD with AS4NW312. The following sample command loads the NLM on a NetWare 5.0 server:
LOAD SYS:/AS4NW/AS4NW410 /TCP /MAXCNN=10
The LOAD command is followed by the complete path of the NLM, AS4NW410, which resides in directory SYS:/AS4NW. Following the path are keywords that represent different options. In the above example, the /TCP keyword sets the communications protocol to TCP/IP and the /MAXCNN keyword sets the maximum number of allowed connections to 10. The V4R3 Enhanced NetWare Integration product supports the following LOAD keywords:
・i> /TCP, which specifies the use of TCP/IP rather than IPX. You can specify a port number with /TCP=n, where n is the port number (this is the same value you entered for the CHGNWSA command's NetWare TCP/IP port parameter in Figure 1a).
・i> /MAXCNN, the maximum number of concurrent connections (1 to 100, the default is 50) from AS/400s to a server.
・i> /CLSALLIDL, which closes connections with open files that have been idle for the amount of time specified when the connection was started. NetWare uses a default value of 15 minutes for connections, or you can set this value with the STRNTWCNN (Start NetWare Connection) command's CNNIDLTIME parameter. If this parameter is not specified, the system closes only connections with no associated open files when the specified CNNIDLTIME value has passed.
・i> /SRBUFNUM, the number of buffers (2 to 10, the default is 3) to use in a Save/Restore session.
・i> /SRBUFLEN, the length in bytes of each buffer to use in a Save/Restore session (65536 to 1048576 bytes, or 64 K to 1 MB; the default is 327680 bytes, or 320 K).
Administering NetWare Servers from the AS/400
As in earlier versions of Enhanced NetWare Integration, you use the WRKNWSSTS (Work with Network Server Status) command to administer NetWare servers from the AS/400. Use WRKNWSSTS with *NETWARE for the server type to view the status of only NetWare servers. The default server type value for WRKNWSSTS, *NWSUSRA, tells the AS/400 to use the default server type for the user attributes. You can display these user attributes with the DSPNWSUSRA (Display Network Server User Attributes) command and change them with the CHGCMDDFT (Change Command Default) command. If the default server type for the user attributes is *NWSA, use the CHGNWSA command to change the network server attributes. Defining access at the user attributes (*NWSUSRA) level lets users work with a variety of servers, including LAN Server, NetWare, AIX, or Windows NT servers.
Figure 2 shows the WRKNWSSTS screen. In the Status column, *ACTIVE indicates a server that has either the Enhanced NetWare Integration NLM loaded or an Integrated PC Server (IPCS) with NetWare varied on, and *INACTIVE indicates a server that isn't running one of these NetWare versions. The Location column describes whether the NetWare server is running on an IPCS (*LCL), or running remotely on a PC server (*RMT). (NetWare 5.0 can run only on a PC server.) The Enhanced Functions column indicates whether the Enhanced NetWare Integration NLM is loaded. The Protocol column shows whether a server is using TCP/IP or IPX. To display more detailed information about a NetWare server on your network, enter 5 in the Opt column next to that server's name on the WRKNWSSTS screen. Figure 3 shows the detail screen.
Because the Enhanced NetWare Integration core functions are protocol independent, server management capabilities are retained from previous releases. For example, from the WRKNWSSTS screen, an administrator can
・display users connected to the server
・manually start a connection to the server
・work with connections on the server
・work with volumes on the server
More Help for AS/400-NetWare Sites
The enhancements to the Enhanced NetWare Integration product in V4R3 provide administrative help for sites with networks that include both the AS/400 and NetWare servers. Whether you are upgrading from legacy NetWare servers to NetWare 5.0 or want to centralize management of various NetWare servers, Enhanced NetWare Integration can make it easier to manage your network environment.
Richard Sinn is a staff software engineer at the IBM Santa Teresa Laboratory in San Jose, California. He is also a lecturer at San Jose State University and a freelance writer for magazines and journals. He can be reached at firstname.lastname@example.org or at his Web site, http://www.openloop.com/. is a staff software engineer at the IBM Santa Teresa Laboratory in San Jose, California. He is also a lecturer at San Jose State University and a freelance writer for magazines and journals. He can be reached at email@example.com or at his Web site, http://www.openloop.com/.
You are at an AS400Network.com site.