![]() |
Chapter 15. Configuring Enhanced Integration for NetWare To configure Enhanced Integration for NetWare you need to do several things. This topic lists what you must do, then explains how to accomplish each task. Once you complete the following configuration tasks, you are ready to manage your network.
AS/400 uses the IPX protocol to communicate with the NetWare servers on your network. Therefore, you need to activate this protocol on AS/400.
You need to install the latest Novell NetWare patches before you install the Enhanced Integration for NetWare NLM.
These NLMs allow your NetWare servers to communicate with the Enhanced Integration for NetWare support on AS/400.
Enhanced Integration for NetWare provides the support to be able to enroll AS/400 users on the NetWare network. To use this function, you must create a QNETWARE user object with ADMIN authority in each NDS tree and SUPERVISOR authority on each NetWare 3.12 server on which you want to enroll users. See "QNETWARE User Profile" for more information about the QNETWARE user objects. See also step 6.
This allows you to automate much of the administration tasks, by allowing AS/400 to store passwords. See "Step 5--Change the QRETSVRSEC System Value (Optional)" for details about QRETSVRSEC.
You can create authentication entries for each user so that the Enhanced Integration for NetWare support automatically starts authenticated connections as needed to the appropriate server in the network. If you do not create an authentication entry, you must manually start the connection before using the most of the administration and file system functions. For details about authentication entries, see Chapter 16. "NetWare Authentication Entries and Connections".
This IPL can be done at any time that is convenient for you after you install the Enhanced Integration for NetWare product. The IPL activates the QNetWare file system in the AS/400 Integrated file system.
By ensuring that the QNetWare file system is mounted, you ensure that you have access to the file system and that AS/400 can connect to the NetWare servers. Use DSPMSG QSYSOPR after the IPL and look for the message CPCA08C that says /QNetWare file system mounted.Once the QNetWare file system is mounted and IPX is active, the Enhanced Integration for NetWare support is available.
Network server attributes allows you to set AS/400 system defaults for commands to simplify administration tasks.
If you plan to have manage NetWare user profiles and passwords from AS/400, you need to enroll the users. Step 1--Activate IPX for Enhanced Integration for NetWare You need to configure IPX when you run Enhanced Integration for NetWare. This topic explains how to set up IPX. This topic explains how to configure AS/400 business computing systems for IPX support. If you are unfamiliar with OS/400 IPX support, consider getting the Internetwork Packet Exchange (IPX) Support book for reference. That book contains more detailed information about configuring and managing IPX connections. If your adapter is an Integrated PC Server, you run IPX over token ring or Ethernet LANs. If your adapter is not an Integrated PC Server, you can run IPX over X.25 or frame relay, in addition to the token ring or Ethernet. IPX support requires an IPX description and an IPX circuit. Once these are configured, you can start IPX (STRIPX). You need an IPX description for the system to start IPX. IBM supplies two descriptions, QDCIPX1 and QDCIPX2. You can use one of these to start IPX (using the STRIPX command) or create your own IPX description. Note:
You need at least one IPX circuit to communicate on the network. An IPX circuit is a logical representation of a path for IPX communication. Circuits are not physical objects. Each circuit is associated with a line description. The line description describes the physical connection from the AS/400 to the network. The circuit defines the logical path from the internal IPX layer to the line. You can configure up to 255 circuits on one system. For a LAN, the circuit defines the path or point of attachment from the IPX protocol layer to the IPX network. For a WAN, it defines the path from the IPX protocol layer to a remote IPX node or system. To use AS/400 as an IPX router, see the Internetwork Packet Exchange (IPX) Support book. Several possibilities exist.
Figure 15-1 shows an AS/400 system with an Integrated PC Server ((1)). You do not need to configure IPX to the LAN ((2)) because AS/400 did that for you when you completed "Step 3--Run the Install NetWare Server (INSNTWSVR) Command". Figure 15-1. IPX and OS/400 Integration for Novell NetWare
Figure 15-2 shows IPX ((2)) running over the Integrated PC Server ((1)). You must enable IPX for Enhanced Integration for NetWare. Note:
To run Enhanced Integration for NetWare ((3)) over the Integrated PC Server, you can use one of the IPX descriptions already on AS/400, and the circuit that was created when you configured OS/400 Integration for Novell NetWare is used by IPX ("Step 3--Run the Install NetWare Server (INSNTWSVR) Command"). That circuit directs your IPX traffic out over the line attached to the adapter, which in this case is your Integrated PC Server. It is recommended that you have another adapter and that you add an IPX circuit for that adapter to handle the IPX traffic when you need to vary off the NetWare server that is on the Integrated PC Server. Figure 15-2. IPX with both OS/400 Integration for Novell NetWare and Enhanced Integration for NetWare
In the case shown in Figure 15-3, where the adapter ((1)) is not an Integrated PC Server, you must either use a supplied IPX description or create one. You must also add an IPX circuit (ADDIPXCCT) to direct your IPX traffic over the adapter ((2)). You can use token ring, Ethernet, X.25, or frame relay adapters. This topic steps through configuring an AS/400 system in the sample network shown in Figure 15-10. Your user profile must have *IOSYSCFG special authority to configure IPX support. Note:
To determine if IPX is already configured on your AS/400 system, do the following. If you know you need to configure IPX, go to "Configuration Checklist". To determine if IPX is configured on AS/400
Use a user ID that has at least *IOSYSCFG authority.
+--------------------------------------------------------------------------------+ | CFGIPX Configure IPX | | SYSTEM: SYSAS400 | | Select one of the following: | | | | Configure IPX | | 1. Configure IPX circuits | | 2. Work with IPX descriptions | | 3. Work with IPX status | | | | Configure AnyNet/400 over IPX | | 10. Work with IP over IPX interfaces | | 11. Work with IP over IPX routes | | 12. Work with IP over IPX addresses | | | | 20. Work with SNA over IPX locations | | | | | | | | | | Selection or command | | ===> 1 | | | | F3=Exit F4=Prompt F9=Retrieve F12=Cancel | | | +--------------------------------------------------------------------------------+ +--------------------------------------------------------------------------------+ | Configure IPX Circuits | | System: SYSAS400 | | Select one of the following: | | | | 1. Work with IPX circuits | | 2. Work with IPX circuit routes | | 3. Work with IPX circuit services | | | | | | | | | | | | | | | | | | | | | | | | | | Selection or command | | ===> 1 | | | | F3=Exit F4=Prompt F9=Retrieve F12=Cancel | +--------------------------------------------------------------------------------+
If an active circuit exists, as shown in Figure 15-6, you can use one for Enhanced Integration for NetWare. AS/400 uses only one circuit for each attached line description. +--------------------------------------------------------------------------------+ | Work with IPX Circuits | | System: SYSAS400 | | Type options, press Enter. | | 1=Add 2=Change 4=Remove 5=Display 7=Display associated services | | 8=Display associated routes 9=Start 10=End | | | | Circuit Line Line Circuit | | Opt Name Description Type Status | | | | APVNW01 ETHLINE *ELAN *FSIOP | | PUBS P3ETHLINE *ELAN Active | | TRN_LINE TRNLINE01 *TRLAN Inactive | | TRN_SAP TRNLINE *TRLAN Active | | | | | | | | | | | | | | Bottom | | F3=Exit F5=Refresh F6=Print list F12=Cancel F17=Top F18=Bottom | | | +--------------------------------------------------------------------------------+
Figure 15-7 shows the Work with IPX Status panel. +--------------------------------------------------------------------------------+ | Work with IPX Status | | System: SYSAS400 | | Select one of the following: | | | | 1. Work with IPX circuit status | | 2. Display IPX route information | | 3. Display IPX service information | | 4. Work with IPX/SPX connection status | | 5. Display active IPX description | | | | | | | | | | | | | | | | | | | | | | Selection or command | | ===> | | | | F3=Exit F4=Prompt F9=Retrieve F12=Cancel | +--------------------------------------------------------------------------------+
Figure 15-8 shows active IPX links. If your system is ready to run IPX, then this panel shows connections in a Listen state. +--------------------------------------------------------------------------------+ | Work with IPX/SPX Connection Status | | System: SYSAS400 | | Type options, press Enter. | | 4=End 5=Display details | | | | Remote Remote Remote Local | | Opt Network Node Address Socket Socket Idle Time State | | ___ * * * 2298 002:34:44 Listen | | ___ * * * 7ED6 002:34:55 Listen | | ___ * * * 7ED7 002:34:46 Listen | | ___ * * * 7ED8 002:34:53 Listen | | ___ * * * 7ED9 002:34:47 Listen | | ___ * * * 7EDA 002:34:52 Listen | | ___ * * * 7EDB 002:34:50 Listen | | ___ * * * 7EDC 002:34:49 Listen | | ___ * * * 8795 682:28:01 Listen | | ___ * * * 8796 682:28:02 *IPX | +--------------------------------------------------------------------------------+
When IPX is active, you can view all the active servers on your network that have the Enhanced Integration for NetWare NLMs installed and activated.
+--------------------------------------------------------------------------------+ | Display SPX Connection Status | | System: SYSAS400 | | Connection information: | | Remote IPX network number . . . . . . . . . : * | | Remote node address . . . . . . . . . . . . : * | | Remote socket . . . . . . . . . . . . . . . : * | | | | Local IPX network number . . . . . . . . . . : 00000001 (1) | | | | Local node address . . . . . . . . . . . . . : 000000000001 | | Local socket . . . . . . . . . . . . . . . . : 2298 | | Local connection ID . . . . . . . . . . . . : 65535 | | Remote connection ID . . . . . . . . . . . . : 65535 | | SPX socket type . . . . . . . . . . . . . . : *STREAM | | Associated user profile . . . . . . . . . . : QUSER | | | | Connection state information: | | State . . . . . . . . . . . . . . . . . . . : Listen | | Connection open type . . . . . . . . . . . . : Passive | | | +--------------------------------------------------------------------------------+Configuration Checklist To configure the IPX support, you need to do each of the steps that follow. The steps are summarized in this topic. If you ran the STRIPX command before you created the circuit, you can activate the circuit you just created with one of the following commands:
Note:
Table 15-1. Supported Input/Output Adapters
|
Create your own IPX description to control the IPX internal network number and other IPX values. To create an IPX description, see "Step 1a--Create an IPX Description". To use one of the IBM-supplied IPX descriptions, choose either QDCIPX1 or QDCIPX2.
See "Step 1b--Configure a Line Description".
See "Step 1c--Add an IPX Circuit" Notes:
The following example shows you how to configure a AS/400 system to run the IPX protocol over an Ethernet line. To run IPX over a token ring line, simply create or use a token ring line instead of an Ethernet one. For more information and more examples, see the Internetwork Packet Exchange (IPX) Support book. Figure 15-10. Sample IPX Network. The PCs are running Windows95, NetWare Requester**, and Client Access for Windows 95/NT. Step 1a--Create an IPX Description Each AS/400 must have its own IPX description that defines global system default values for IPX. One IPX description is defined for the OS/400 IPX support on each AS/400. Note: You can define multiple IPX descriptions for IPX support on the system at any given time. You would want to have multiple IPX descriptions when you are using native IPX support and an Integrated PC Server or multiple Integrated PC Servers.To create an IPX description:
+--------------------------------------------------------------------------------+ | CFGIPX Configure IPX | | SYSTEM: SYSAS400 | | Select one of the following: | | | | Configure IPX | | 1. Configure IPX circuits | | 2. Work with IPX descriptions | | 3. Work with IPX status | | | | Configure AnyNet/400 over IPX | | 10. Work with IP over IPX interfaces | | 11. Work with IP over IPX routes | | 12. Work with IP over IPX addresses | | | | 20. Work with SNA over IPX locations | | | | | | | | | | Selection or command | | ===> | | | | F3=Exit F4=Prompt F9=Retrieve F12=Cancel | | | +--------------------------------------------------------------------------------+
AS/400 displays the Work with IPX Descriptions menu (see Figure 15-12).
Or enter the Create IPX Description (CRTIPXD) command on a AS/400 command line and press F4. +--------------------------------------------------------------------------------+ | Work with IPX Descriptions | | System: SYSAS400 | | | | | | Type options, press Enter. | | 1=Create 2=Change 3=Copy 4=Delete 5=Display 6=Print | | 7=Rename 9=Retrieve source | | | | Opt IPX Desc Text | | 1 | | | +--------------------------------------------------------------------------------+
Figure 15-13. Create IPX Description Command
Prompt Example (1 of 2)
+--------------------------------------------------------------------------------+ | Create IPX Description (CRTIPXD) | | | | Type choices, press enter. | | | | IPX description . . . . . . . . systema(1) NAME | | IPX internal network number . . 00000001(2) 00000001-FFFFFFFE, *RANDOM | | IPX routing protocol . . . . . . *NLSP *NLSP, *RIP | | IPX router name . . . . . . . . *NONE | | | | | | IPX maximum datagram size . . . 1500 (3) 576-65535 | | Text 'description' . . . . . . . IPX Description for SYSTEMA | | | | | +--------------------------------------------------------------------------------+
Continue at "Step 1b--Configure a Line Description".
Use the name of your AS/400 system for the IPX description name.
The internal network number is a hexadecimal number, ranging from 00000001 through FFFFFFFE. Choose a number, or specify *RANDOM, and AS/400 will generate a number for itself. The internal network number must be a unique number on the network. Therefore, if you use *RANDOM, there is a small chance to generate a duplicate number. There is no default. For the IPX internal network number in this example, 00000001 is used.
If you do have routers, read on. To be very safe, you can choose the lower value, 576. All routers support at least this maximum datagram size. This value is important because there is no end-to-end negotiation of maximum datagram size, and there may be intermediate hops in a route to the destination system that have a smaller maximum datagram size than the directly attached links to the AS/400 system. You must determine the maximum packet size that is allowed between the AS/400 system and the destination system and set this value in the IPX description accordingly. Make this value as large as possible for performance reasons. If an IPX router between the AS/400 system and the destination system cannot support receiving packets that are the maximum datagram size, it discards the packet. All routers must support 576 byte datagrams. Tip:
The Add IPX Circuit (ADDIPXCCT) command has a default maximum datagram parameter that you must consider when setting the IPX maximum datagram parameter for an IPX description. If the IPX maximum datagram value of the IPX description is larger than the default maximum datagram value of the IPX circuit on a circuit chosen for the IPX connection, then sending the packet over this circuit may fail. Also, the IPX maximum datagram size of the IPX description is used with the maximum datagram size parameter in the SSAP definition of the line description associated with the circuit to determine the actual maximum IPX packet size that is sent on a physical line.
Note: Changes to an IPX description take effect when: For the network example, AS/400 has one Ethernet line description. You can use a line description that is already configured if the line meets the requirements for your network. If your network uses token ring, you must use CRTLINTRN instead of CRTLINETH. To configure a line description:
If you do not know the name, type WRKHDWRSC *CMNThe resource name consists of the IOA resource name and the port number on the IOA. Figure 15-14 shows the IOAs that could be available for IPX support on AS/400. See Table 15-1 for the IOAs that IPX supports. Figure 15-14. Work with Communication Resources
Display Example
+--------------------------------------------------------------------------------+ | Work with Communication Resources | | | | System: SYSAS400 | | | |Type options, press Enter. | | | | 2=Edit 4=Remove 5=Work with configuration descriptions | | | | | |Opt Resource Type Text | | CMB01 2615 Combined function IOP | | LIN01 6152 Comm Adapter | | LIN011 6152 V.24 Port | | CMB02 2617 Combined function IOP | | LIN02 2617 LAN Adapter | | LIN012 2617 Ethernet Port | | LIN18 605A Comm Adapter | | CC08 2666 Comm Processor | | LIN15 2616 Comm Adapter | | LIN151 2666 Comm Port | | LIN20 605A Comm Adapter | | | | | +--------------------------------------------------------------------------------+
The Create Line Description (Ethernet) (CRTLINETH) command prompt display is shown. See Figure 15-15. Certain values have special meaning for IPX support.
Figure 15-15. Create Line Description (Ethernet)
Command Prompt Example
+--------------------------------------------------------------------------------+ | Create Line Desc (Ethernet) (CRTLINETH) | | | | Type choices, press Enter. | | | | Line description . . . . . . . . > AETHLINE (1) Name | | Resource name . . . . . . . . . > LINE012 (2) Name, *NWID, *NWSD | | Online at IPL . . . . . . . . . *YES *YES, *NO | | Vary on wait . . . . . . . . . . *NOWAIT *NOWAIT, 15-180 (1 second) | | Local adapter address . . . . . *ADPT 020000000000-7EFFFFFFFFFF.. | | Exchange identifier . . . . . . *SYSGEN 05600000-056FFFFF, *SYSGEN | | Ethernet standard . . . . . . . *ALL (3) *ETHV2, *IEEE8023, *ALL | | SSAP list: | | Source service access point . *SYSGEN(4) 02-FE, *SYSGEN | | SSAP maximum frame . . . . . . *MAXFRAME, 265-1496, 265... | | SSAP type . . . . . . . . . . *CALC, *NONSNA, *SNA, *HPR | | + for more values | | Text 'description' . . . . . . . *BLANK | | | | | | | | | | Bottom | | F3=Exit F4=Prompt F5=Refresh F10=Additional parameters F12=Cancel | | F13=How to use this display F24=More keys | | | +--------------------------------------------------------------------------------+
The default value, *SYSGEN, automatically defines source service access points: 04, 12, AA, or C8. There is no need to explicitly define SSAPs in the line description unless the line description is to be shared with other protocols. If the line description is to be shared with other protocols, define the SSAPs required by the other protocols. Tip:
The X'AA' SSAP is unique because it can be shared by multiple communications protocols at the same time; therefore the X'AA' SSAP value can be explicitly defined on the line description without causing a conflict (for example, TCP/IP uses the X'AA' SSAP value). Figure 15-16 shows the Ethernet line description for SYSTEMA. Figure 15-16. Sample Ethernet Line Description
for System A
+--------------------------------------------------------------------------------+ | Display Line Description SYSTEMA | | 02/23/96 13:46:15 | | Line description . . . . . . . . . : AETHLINE | | Option . . . . . . . . . . . . . . : *BASIC | | Category of line . . . . . . . . . : *ELAN | | | | Resource name . . . . . . . . . . : LIN012 | | Online at IPL . . . . . . . . . . : *YES | | Vary on wait . . . . . . . . . . . : *NOWAIT | | Local adapter address . . . . . . : *ADAPT | | Exchange identifier . . . . . . . : 056A0036 | | Ethernet standard . . . . . . . . : *ALL | | Maximum controllers . . . . . . . : 40 | | Error threshold level . . . . . . : *OFF | | Text . . . . . . . . . . . . . . . : 'Line description for System A' | | | +--------------------------------------------------------------------------------+Step 1c--Add an IPX Circuit To add a circuit for the sample network:
+--------------------------------------------------------------------------------+ | Configure IPX Circuits | | SYSTEM: SYSAS400 | | Select one of the following: | | | | 1. Work with IPX circuits | | 2. Work with IPX circuit routes | | 3. Work with IPX circuit services | | | | | | | | | | | | | | | | | | | | | | | | | | Selection or command | | ===> 1 | | | | F3=Exit F4=Prompt F9=Retrieve F12=Cancel | | | +--------------------------------------------------------------------------------+
Tip:
However, you can define up to 4 circuits if your LAN uses multiple frame types for IPX packets. The line type determines the number of SSAPs that can be used for IPX packets. Since you can define one circuit for each SSAP, this also determines the number of circuits that can be defined for a particular line description. Only 2 circuits can be defined for token-ring and Ethernet Version 2 (ETHV2) type line descriptions. For more information about circuits, see the Internetwork Packet Exchange (IPX) Support book.
The Work with IPX Circuits display is shown in Figure 15-18. +--------------------------------------------------------------------------------+ | Work with IPX Circuits | | System: SYSAS400 | | Type options, press Enter. | | 1=Add 2=Change 4=Remove 5=Display 7=Display associated services | | 8=Display associated routes 9=Start 10=End | | | | Circuit Line Line | | Circuit | | Opt Name Description Type | | Status | | | | | +--------------------------------------------------------------------------------+
Use defaults for values that are not highlighted. For explanations of the values that are not highlighted, see either the online help text or the Internetwork Packet Exchange (IPX) Support book. +--------------------------------------------------------------------------------+ | Add IPX Circuit (ADDIPXCCT) | | | |Type choices, press Enter. | | | |Circuit name . . . . . . . . . . > CCT1A (1) | |Line description . . . . . . . . > AETHLINE (2) Name | |IPX network number . . . . . . . 2FFFFFFF (3) 00000001-FFFFFFFD | |Frame type . . . . . . . . . . . *SSAP *SSAP, *SNAP, *ETHV2, *ETHNTW | |Enable for NLSP . . . . . . . . *YES *YES, *NO | |MAC channel for NLSP . . . . . . *BROADCAST *BROADCAST, *MULTICAST | |Router priority for NLSP . . . . 44 0-127 | |Cost override for NLSP . . . . . *CALC 1-63, *CALC | | | +--------------------------------------------------------------------------------+ The important prompts in an IPX circuit for an Ethernet line description are as follows:
The line description name in the sample network is AETHLINE. To find the names of the currently defined line descriptions, use the Work with Line Descriptions (WRKLIND) command. Note: The line description must be created prior to adding the circuit.
To find that number, look at the circuit descriptions on other AS/400 systems in the network, or look on your Novell NetWare server. The number should be the same on all systems in the network. For the sample network, the Ethernet portion of the network has an external IPX network number of 2FFFFFFF. This value must match for all IPX nodes in an IPX network. Only circuits within a local area network (LAN) need an external network number. To activate your IPX circuit:
STRIPX IPXD(SYSTEMA)
The Work with IPX Circuits display is shown in Figure 15-18. Step 2--Install the Novell NetWare Patches on the Servers The latest Novell NetWare patches must be installed on each server in the NDS tree and on each NetWare 3.12 server that you will manage from AS/400. NetWare Patches Novell makes these patches available on its home page on the world wide web. At the time this book was published, the following was the procedure for getting Novell NetWare patches from the web:
A page with lists of Novell patches should appear. The links on the Novell home page may change in the future. If they do change and you cannot find these patches, contact Novell for assistance. NetWare-J Patches IBM provides these patches on the world wide web. At the time this book was published, the following was the procedure for getting Novell NetWare patches from the web:
A page with lists of Novell patches should appear. Step 3--Install the Enhanced Integration for NetWare NLM on the Servers The Enhanced Integration for NetWare NLM must be installed on each server in the NDS tree and on each NetWare 3.12 server that you will manage from AS/400. There is a different Enhanced Integration for NetWare NLM for each version of NetWare. The Enhanced Integration for NetWare installation diskette for NetWare 4.1 may include: Label: QFPNTWE41x. Contents: AS4NW41x.NLM - Enhanced Integration NLM AS4NW.IPS - Install Script file for NetWare 4.1 CLIB.NLM - NetWare 4.1 C Runtime Library DSAPI.NLM - NetWare Directory Services API Library VOLLIB.NLM - NetWare 4.1 Volume Library Utility PARTAPI.NLM - NetWare 4.1 Media Manager Partition Lib NWPSRV.NLM - NetWare 4.1 Print Services LibraryTwenty-two language files named AS4NW.MR0 are in the directory: NLS\numberwhere number is the NetWare language number. Enhanced Integration for NetWare has a message file for 14 unique NetWare languages. See Table D-1 for a list of the languages and for a list of the 14 languages for which a message file exists. The Enhanced Integration for NetWare 4.1 NLM installs all languages files. The NLM uses the language file that corresponds to the current Language of the server. Enhanced Integration for NetWare installation diskette for NetWare 3.12 Label: QFPNTWE312 Contents: AS4NW312.NLM - Enhanced Integration NLM AS4NW.NLM - Install NLM for NetWare 3.12 servers VOLLIB.NLM - NetWare Volume Library Utility NWPSRV3X.NLM - NetWare 3.12 Print Services LibraryThe Enhanced Integration for NetWare 3.12 NLM installs the same 22 language files named AS4NW.MR0 as does the Enhanced Integration for NetWare 4.10 NLM. The AS4NW.NLM installation NLM prompts for the desired language. This is the only language file installed with the Enhanced Integration for NetWare 3.12 NLM. IBM provides these NLMs to ensure you have a complete set. You can also obtain the current versions of most of these NLMs from Novell. The exceptions are as4nw410 and as4nw312, which are part of Enhanced Integration for NetWare. If you do not have the diskette, you can create diskettes from the files in the QDLS folder (QFPNTWE) on AS/400 using Client Access. For instructions, see "Creating Installation Diskettes". LOAD Command for the Enhanced Integration for NetWare NLM The LOAD command provides options that allow you to tailor your environment. LOAD AS4NW410 and LOAD AS4NW312 Command The LOAD AS4NW410 and LOAD AS4NW312 console commands load the NetWare 4.1 and NetWare 3.12 versions, respectively, of the Enhanced Integration for NetWare NetWare Loadable Module (NLM). This NLM is required to use Enhanced Integration for NetWare functions on a NetWare server. Note: This is a NetWare console command.
If this parameter is not specified, only connections that have no open files associated with them will be closed when the specified CNNIDLTIME value has passed. LOAD SYS:/AS4NW/AS4NW312 /MAXCNN=10This command loads the NetWare 3.12 version of the Enhanced Integration for NetWare NLM. The full path to the NLM is specified. The maximum number of connections allowed is 10. Since CLSALLIDL is not specified, only connections with no open files will be closed by idle connection processing. To load the NLM on a NetWare 4.1 server: LOAD AS4NW410 /CLSALLIDLThis command loads the NetWare 4.1 version of the Enhanced Integration for NetWare NLM. The server path environment variable was changed to include the directory SYS:/AS4NW. The maximum number of connections allowed is the default value of 50. All idle connections, regardless of whether or not there are open files associated with them, will be closed by idle connection processing. Loading the Enhanced Integration for NetWare NLM To install the as4nw312.nlm on the NetWare 3.12 servers:
LOAD A:\AS4NW
See Table D-1 for a list of languages that have message libraries. LOAD SYS:AS4NW\AS4NW312
LOAD INSTALL >A:\If you are installing on NetWareJ 4.10 servers the path is A:\NLS\9, not just A:\.
A menu appears that indicates which file groups to install.
Return to the RCONSOLE display (press ESC or Alt-F3) and load the NLM to be active. LOAD SYS:AS4NW\AS4NW410
For example, if you use AUTOSTR.NCF as the batch file for all of your NetWare servers, add the following statement to the end of the batch file: load sys:as4nw\as4nwnnn (nnn = 410 or 312)Then save the file and exit. If you do not add this statement, you must manually load the NLM each time you bring up the server. The NLM is loaded after you DOWN and restart the server. If the server is on an Integrated PC Server, use the VRYCFG command to down the server. To load the NLM immediately, enter the following at the server command prompt: load sys:as4nw\as4nwnnn
Note:
Step 4--Create a QNETWARE User on NetWare Servers (Optional) To enroll AS/400 users on NetWare, you need a QNETWARE user and on all
NDS trees and NetWare 3.12 servers that are to be managed from AS/400.
A QNETWARE user is created on AS/400 when Enhanced Integration for NetWare
is installed on your system. If you do not want to enroll AS/400 users,
skip this step. If you do want to enroll AS/400 users, see Chapter
21. "Managing User Enrollment" for more information.
Step 5--Change the QRETSVRSEC System Value (Optional) Changing the QRETSVRSEC from its default of 0 to the value 1 can make
system management more efficient. There are security implications, however.
See "Step 1--Set Up Your
NetWare Servers for User Enrollment" for detailed information.
Step 6--Set Up Authentication Entries (Optional) To automate connections to the appropriate servers in your network, you need authentication entries for each AS/400 user that will be using the Enhanced Integration for NetWare support.
Power down AS/400, then re-IPL. Use the PWRDWNSYS command and specify *YES for the RESTART parameter. This activates the QNetWare file system that is used by Enhanced Integration for NetWare. To verify that the QNetWare file system is mounted, wait until the IPL completes. Then enter: DSPMSG QSYSOPRLook for the message CPCA08C that says: /QNetWare file system mountedNote: This IPL can be done any time after the licensed program for Enhanced Integration for NetWare is installed. The step is placed here only for those who want to complete the configuration steps before running the PWRDWNSYS command. Step 8--Verify Communications to the NLMs To verify that AS/400 can communicate with the Enhanced Integration for NetWare NLMs on the NetWare servers
The service type is *NTWENHINTG. Figure 15-20 shows active servers on two different networks. +--------------------------------------------------------------------------------+ | | | | | Display IPX Service Information | | System: SYSAS400 | | Type options, press Enter. | | 5=Display details | | | | Service Service Remote Hops to Service | | Opt name Type Network Service Source | | SERVERA *NTWENHINTG 480B0001 1 *SAP | | SERVERB *NTWENHINTG D4800051 2 *SAP | +--------------------------------------------------------------------------------+ Step 9--Define Network Server Attributes (Optional) The Change Network Server Attributes (CHGNWSA) command changes AS/400 attributes that allow you to change certain defaults on a system-wide basis. The attributes are originally set for users of the IBM LAN Server for OS/400 product. If you are running only NetWare servers, you may want to change the settings as shown in Figure 15-21. You can set many of these attributes on an individual user profile basis using the CHGNWSUSRA command. Many network server commands such as DSPNWSUSR and WRKNWSSTS can specify that information from the network server attributes should be used by specifying *NWSA for a given parameter. Network server attributes are saved by the Save System (SAVSYS) command. Network server attributes are restored to the system when the operating system is installed. +--------------------------------------------------------------------------------+ | Change NWS Attributes (CHGNWSA) | | | | Type choices, press Enter. | | | | Prompt control . . . . . . . . . PMTCTL > *NETWARE (1) | | Default server type . . . . . . DFTSVRTYPE > *NETWARE (2) | | NDS tree . . . . . . . . . . . . NDSTREE 'CT_TREE' (3) | | | | NDS context . . . . . . . . . . NDSCTX 'ROCH.IBM' (4) | | | | NDS tree list: NDSTREELST | | NDS tree . . . . . . . . . . . *NONE (5) | | | | User object context . . . . . | | | | Default server . . . . . . . . | | | | Profile object . . . . . . . . | | | | + for more values | | More.. | | F3=Exit F4=Prompt F5=Refresh F12=Cancel F13=How to use this display | | F24=More keys | | | +--------------------------------------------------------------------------------+ +--------------------------------------------------------------------------------+ | Change NWS Attributes (CHGNWSA) | | | | Type choices, press Enter. | | | | NetWare 3.12 server list . . . . NTW3SVRLST *NONE (5) | | | | + for more values | | | | | | | +--------------------------------------------------------------------------------+In the example represented by Figure 15-21, the AS/400 defaults are changed to as follows:
|
Step 10--Enroll Users (Optional) You can simplify network user management tasks with user profile propagation,
allow AS/400 users to access NetWare file systems, and send printing to
NetWare-managed printers. If you want to do this, go to Chapter
21. "Managing User Enrollment".
[ Top of Page | Previous Page | Next Page | Table of Contents | Index ] |