Tim, I know my posts tend to be rather long, particularly so when I need to guess many possibilities from sparse input.
However, if you read them fully you'll see that on both my responses to this query I managed to find an excuse to mention Enterprise Extender. We all await clarifications from Thomas. Meantime perhaps someone can quote chapter and verse regarding the level of AS/400 operating system which begins support for Enterprise Extender since I believe I have seen mention of such support only relatively recently. Never mind - it's a challenge - and I came up with the following from ( http://www-1.ibm.com/support/docview.wss?uid=nas1ed75fbb6841d9f718625710a004963a3&rs=110 ) <quote> Configuring EE (Enterprise Extender) between Two IBM System iT Systems Technote This is a sample configuration for EE (Enterprise Extender) between two IBM System i5T systems at R540 or above. SYSTEM A and SYSTEM B Step 1: Ensure "Allow HPR Transport Tower Support" (ALWHPRTWR) is enabled in Network Attributes. a To view the parameter: DSPNETA b To change the value: CHGNETA ALWHPRTWR(*YES) Step 2: Display the Network Attributes ( DSPNETA ) of each system and gather the following information. a Local Network ID (LCLNETID) b Local Control Point Name (LCLCPNAME) Step 3: Get the IP addresses for each system. Use CFGTCP, Option 1 to view the local interfaces and select the IP addresses you wish to use for this connection. Step 4: Create the APPC controller ( CRTCTLAPPC ). SYSTEM A SYSTEM B Local IP Interface Address = 1.1.1.1 Local IP Interface Address = 1.1.1.2 Local Network ID = APPN Local Network ID = APPN Local Control Point Name = SYSTEMA Local Control Point Name = SYSTEMB CRTCTLAPPC CRTCTLAPPC LINKTYPE = *HPRIP LINKTYPE = *HPRIP RMTINTNETA = 1.1.1.2 RMTINTNETA = 1.1.1.1 LCLINTNETA = 1.1.1.1 LCLINTNETA = 1.1.1.2 RMTNETID = APPN RMTNETID = APPN RMTCPNAME = SYSTEMB RMTCPNAME = SYSTEMA Note: At the time of this writing, a value must be specified in the LCLINTNETA other than *SYS. A virtual APPN controller is created called QAPENDxxxx, and this is where the APPC device is attached. The original APPC controller that is created above will be at a Varied On state and that is normal. Step 5: The configuration object QAPENDxxxx controller status of ACTIVE APPC device status of ACTIVE Original APPC controller status of VARIED ON. Caution: When using Enterprise Extender across a network that traverses firewalls, ensure UDP ports 12000-12004 are open to successfully establish a connection. </quote> ... and it even includes your warning! Chris Mason ----- Original Message ----- From: "Tim Hare" <[EMAIL PROTECTED]> Newsgroups: bit.listserv.ibm-main To: <[email protected]> Sent: Thursday, 20 April, 2006 9:24 PM Subject: Re: Need Help defining an AS400 with an IP address to the mainframe > I think everyone so far is overlooking a possibility: that this new > AS/400 is configured to support Enterprise Extender. In that case, the IP > address is sufficient to connect to it, as long as you have EE running in > your Communication Server. You will also need to make sure that UDP ports > 12000-12004 (yes those are five digit numbers) are open in any firewalls > between the AS/400 and your box. > > Tim Hare > Senior Systems Programmer > Florida Department of Transportation > (850) 414-4209 ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO Search the archives at http://bama.ua.edu/archives/ibm-main.html
