NWSAA 4 to AS400 configuration options

(Last modified: 24Jan2001)

This document (10059960) is provided subject to the disclaimer at the end of this document.

goal

fact

This document addresses 3 different configuration options relating to NWSAA ver 4.00.20 and connections to AS400s. A single Peer Link configuration, Multiple Control Points for greater than 253 connections, and connections to multiple AS400 systems are all covered. The manuals cover most of these configurations but not all in the same place and many times present overlapping and conflicting information. These configurations worked in my particular scenario and likely will work in most others.
This document assumes that you know your way around the NWSAA configuration utility and are at least somewhat familiar with NetWare.

goal

Creating a Primary single Control Point connection.

fact

This configuration is used for creating a primary connection to a single AS400 with only one control point.

The preferred configuration on the AS400 is to have AUTO CREATE turned on. If this is not possible for some reason, then all configuration parameters will have to be defined manually on the AS400. You will need to consult the AS400 and NWSAA documentation on how to accomplish this.

1) Configure the Node. Select Node and click create. On the Basic Screen enter the Network name (generally APPN) and a CPname and alias (ex: CPNAME4). Define the Node type as an End Node. The Advanced and Encryption screens can generally be left at defaults. Click OK.
2) Define a Data Link adapter. Select Data Link Adapter and click create. Select the adapter type and click ok. Enter the adapter name. The adapter name needs to match the name defined in NetWare when the board driver was loaded using the NAME= parameter (ex: SAATOKEN). Define the local SAP as 04. The adapter number can generally be left at the default as well as the Performance and Reactivation screens. Click OK.
3) Define a Peer Link to the AS400. Select Peer Links and click create. Select the adapter type and click OK. The Peer link name needs to match the CPname defined in step 1 (CPNAME4). For the Port name select the adapter defined in step 2. Enter the address of the AS400 in the remote node address field. This address can be determined by using the DSPLIND command on the AS400. Select 04 for the Remote SAP. In the Adjacent Node Parameters screen the Adjacent CPname fields should be blank and the CP type should be set to Learn. The Advanced, Performance and Reactivation screens can generally be left at defaults. Click OK.
4) Next configure an AS400 system. Select AS400 Systems and click create. Enter the Network name (generally APPN) and the default AS400 system and alias name (ACC400). On the Advanced screen the Network Name and CPname should be blank. Click OK. This will also create a Partner LU 6.2 to match.
5) Define any parameters needed for the Commexec and click Finish to save the configuration file. (Note: some problems have been encountered with AS400PCS not loading if IPX is turned off)
6) Commexec will read the IWSAA.INI file to determine what configuration file to load. Be sure this file is updated correctly. If changes are made to the SAAUP.NCF file to load a different configuration file, Commexec will still load the file specified in the INI file. If no INI file is found, Commexec will load with default parameters and generate a message to that effect on the console screen.

goal

NWSAA 4.0 to AS400 ' Multiple Control Points and greater than 253 connections:

fact

This configuration is used to create multiple Control Points to the same AS400 for the purpose of supporting more than 253 connections. It can also be used to separate out devices from different locations for easier management on the AS400, load balancing on the controllers, or any other reason you might want to group your devices.

Before attempting to establish multiple connections to the same AS400 via multiple control points, first establish the primary connection and test it. This will significantly reduce your troubleshooting later, if any is needed.

Whenever making changes to the configuration file, it is recommended that you work with a second copy in event that you need to return to a baseline configuration. Be sure to edit the SAAUP.NCF or IWSAA.INI file to reflect the name of the new configuration file.

In order for the NWSAA server to use a second controller on the same token-ring or Ethernet connection, an additional alias and SAP (service access point) must be defined on the AS400. Additional alias's can be defined on the AS400 using the WRKCFGL command on the AS400. If *APPNLCL is not created, create it. When creating an alias, you must also define the default name as the first entry. For instance, if the default system name is ACC400, then you would create an entry for ACC400 and another entry for ACCGW1 (if this is the alias name you choose). When creating additional SAPs, keep in mind this will require varying off the controller. This will likely have to be performed after hours in most production environments. Consult your AS400 documentation on how to configure additional SAPs.
It is also worth considering creating any additional SAPs you might need in the future. The default SAP is 04. Additional SAPs are incremented by 4, i.e. the next SAP would be 08, then 0C, etc.

Note: This is the configuration that worked in the particular environment I installed the gateway to. It is possible that configuration differences on the AS400 or the gateway could alter these instructions.

1) A Node should already have been created for the primary connection. Ensure that this is defined as an End Node and the Network Name matches your network. Generally this would be APPN.
2) Create a second Data Link Adapter. The first should have been created when you setup the primary connection and should have been configured to use SAP 04. The second adapter needs to be configured to use the same hardware adapter, but a different SAP. If you defined a second SAP of 08 on the AS400, use 08. Select Data Link Adapter and click Create. Select the same adapter type that was used for the first data link adapter and click OK. The Adapter Name needs to be the same name as that used for the first data link adapter and can be selected from the pull down list. The adapter number should also be the same as the first adapter. If you left this at the default it will be 0. Set the local SAP to the next SAP that was defined on the AS400, usually 08. The Performance and Reactivation screens can generally be left at the defaults. Click OK.
3) A peer link for the primary connection should have been created during initial configuration. Be sure to configure it to use the primary (04) data link and set the remote SAP to 04. On the Adjacent Node Parameters screen, the adjacent CPNAME should be blank and the CP type should be Learn. On the Advanced screen, turn on Activate Link at Start and turn off APPN support (unchecked). Click OK.
4) Next you will need to create a system entry for both the default system (if not already done) and the alias that was created on the AS400. These must match exactly the names defined on the AS400 and are case sensitive. Select AS400 Syste.ms on the configuration menu and click create. Enter the Network Name (generally APPN) and the default system name (ACC400 as referenced earlier) in both the system name and system alias fields on the Basic screen. The Network Name and CP name need to be blank on the Advanced screen. Click OK. Select AS400 Systems again and click create to build the second (alias) system. Enter the Network Name as before. For the System name and System alias, enter the alias name defined on the AS400 exactly as it was entered. In the above example we used ACCGW1 as the alias. On the Advanced screen enter the same information for the Network name and CP name as on the basic screen. Click OK. This will also create a Partner LU 6.2 to match.

5) Next you will need to configure a Host link. This will be the link for the Alias name, not the primary connection. The primary connection is using the Peer Link defined earlier. Select Host Link and click create. Select the Data Link Adapter Type and click Ok. For the Host Link name enter the name of the alias defined on the AS400 (ACCGW1). For the Port Name select the second Data Link adapter defined in step 2. Define the Remote node address to match the AS400 and select the Remote SAP that matches the SAP on the second Data Link adapter (08). On the Adjacent Node Parameters screen enter the adjacent CP name. Following the example, this would be APPN.ACCGW1. The Adjacent CP type should be Back-Level LEN. On the Advanced screen, turn on (check) Activate Link at start, turn off APPN support and enter the Local CP name override (ACCGW1). Click OK. This will return you to the Configure Host Links screen, Click OK.
6) Save this configuration file and load it on the SAA gateway. Any clients that you want to access the system through the second control point need to be pointed to the alias name in place of the default system name previously used.

goal

Creating connections to additional AS400 systems.

fact

This configuration is used to create primary connections to additional AS400s from a single NWSAA gateway. It is assumed that the primary connection to the primary AS400 has already been created and tested.

1) These steps assume that the primary connection to the primary AS400 has been created and tested successfully.
2) Select AS400 Systems and click create. Enter the Network name (generally APPN) and the default AS400 system and alias name (MKTG400). On the Advanced screen the Network Name and CPname should be blank. Click OK. This will also create a Partner LU 6.2 to match.
3) Define a Peer Link to the second AS400. Select Peer Links and click create. Select the adapter type and click OK. The Peer link name needs to match the System name defined in step 2 (MKTG400). For the Port name select the primary adapter (generally the 04 adapter). Enter the address of the AS400 in the remote node address field. This address can be determined by using the DSPLIND command on the appropriate AS400. Select 04 for the Remote SAP. In the Adjacent Node Parameters screen the Adjacent CPname fields should be blank and the CP type should be set to Learn. The remaining screens can generally be left at their defaults. Click OK.
4) Save this configuration file and load it on the SAA gateway.
5) Any clients that you want to access the additional AS400 system through the gateway need to be pointed to the appropriate system name in place of the default system name previously used.

document

Document Title:	NWSAA 4 to AS400 configuration options
Document ID:	10059960
Solution ID:	NOVL38340
Creation Date:	24Jan2001
Modified Date:	24Jan2001
Novell Product Class:	connectivity products

disclaimer

The Origin of this information may be internal or external to Novell. Novell makes all reasonable efforts to verify this information. However, the information provided in this document is for your information only. Novell makes no explicit or implied claims to the validity of this information.
Any trademarks referenced in this document are the property of their respective owners. Consult your product manuals for complete trademark information.