AS/400 TCP/IP 494 configuration

Issue:
What configuration is required on the AS/400 for the Perle 494E to operate.

Solution:

Configuring the AS/400 for Anynet support can be done in five simple steps.
This document will assume the AS/400 has an Ethernet line configured and the TCP/IP interface created with an assigned TCP/IP Address.

STEP 1
Change the Network Attribute To Allow Anynet Support
To check the network attribute Allow Anynet Support is set to *YES ,enter command DSPNETA ,option is located on the third screen.
If set to *NO, enter command CHGNETA ,find the parameter, Allow Anynet Support and change.

Note :The network attributes contain information which is required to complete the controller network configuration


Local network ID . . . . . . . . .: APPN (default net ID,or changed name)
Default local location . . .. . .. : PERLE170 (your system name or serial number)


STEP 2
Create the Anynet Appc Controller with the link type of *ANYNW
There are two methods of configuring controllers.
Method 1 . Creating Multiple Anynet Appc controllers to support each remote location.
Method 2 . Creating a Single Anynet Appc controller to support anywhere from 1 to 254 Remote controllers.
Method two is recommended when there are multiple remote locations.
When multiple Anynet Appc controllers are created, Appc Devices for each remote location may not autoconfig under the correct controller description. When installing a new location if all other Anynet Appc Controllers with the exception of the description for the site being created were varied off, this will allow the new location to auto config under the correct Anynet Appc controller.
Using the single Anynet Appc Controller removes any possibilities of the Appc device being auto created under the wrong Appc Controller description.

To create the Appc controller description enters command CRTCTLAPPC .

        Create Ctl Desc (APPC) (CRTCTLAPPC)

    Type choices, press Enter.

 Controller description . . . . . >      ANYNETAPPC               Name
 Link type . . . . . . . . . . . >           *ANYNW                         *ANYNW,
 Online at IPL . . . . . . . . .             *YES                               *YES, *NO
 Remote network identifier . . .       *NETATR                       Name, *NETATR,
 Remote control point . . . . . .          ANYNTCTL                   Name,
 APPN/HPR capable . . . . . . . .         *YES                        *YES, *NO

Fig 1
STEP 3
Add entries to the Appn Remote List.
To communicate using Appc over TCP/IP support .the AS/400 requires a configuration list entry for each 494 TCP/IP controller The TCP/IP communication uses the information in the Appn remote location list to determine which controller description to use when activating NWS session.
To update the APPNRMT configuration list, use command.
CHGCFGL *APPNRMT (See table below)
If there is no configuration list, use command
WRKCFGL (use option 1 to create a list.
The configuration List :QAPPNRMT
The configuration list type :*APPNRMT (You can add entries for each controller as listed in table.

                         Display Configuration List                                                          PERLE
                                                                                                         03/03/03 10:20:44
       Configuration list . . . . . . . . : QAPPNRMT
      Configuration list type . . . . . : *APPNRMT
      Text . . . . . . . . . . . . . . . :

  -------------------APPN Remote Locations--------------------
                         Remote                               Remote             Control
 Remote              Network          Local            Control             Point                   Secure
 Location            ID                    Location       Point                 Net ID                  Loc
 
 C494E01           *NETATR        *NETATR       ANYNTCTL       *NETATR             *NO
 C494E02          *NETATR         *NETATR        ANYNTCTL      *NETATR             *NO
 __________      *NETATR        *NETATR        _________         *NETATR             *NO



 F3=Exit  F11=Display session information      F12=Cancel      F17=Position to

Fig 2
When adding items to the list only the Remote location and Remote Control Point have to be added the AS/400 will automatically update all other fields.

STEP 4
Map 494 LU Name to an Internet Address
The AS/400 TCP/IP host table provides the mapping between the SNA remote location and remote network ID of the 494 TCP/IP controller and a remote internet address.
To add to or change. Enter the command CFGTCP then option 10 add an entry for each controller card which has an IP address.
Note:
If the controller has multiple twinax cards, each card is assigned a unique IP address and a unique LU and CP name.
Add an entry for each configured controller card in the 494 controller. (see fig.3)


                   Work with TCP/IP Host Table Entries
                                                                            System: PERLE
    Type options, press Enter.
  1=Add      2=Change      4=Remove     5=Display     7=Rename

                Internet                Host
Opt          Address                Name

__        ___________
__          101.102.100.30        C494E01.APPN.SNA.IBM.COM
__         101.102.100.31         C494E02.APPN.SNA.IBM.COM
__          127.0.0.1                LOOPBACK  LOCALHOST


F3=Exit   F5=Refresh    F6=Print    list F12=Cancel F17=Position to

Fig. 3


The IP address entered must match the remote IP address of the 494 controller.
The host name entered must be in the form of rmtlocname.appn.sna.ibm.com , where:

rmtlocname - is the RMTLOCNAME entered in the RWS controller.
APPN - is the remote network ID of the 494e TCP/IP controller.
sna.ibm.com - is the SNA domain suffix.

the SNA domain suffix is IBM supplied and is needed for Any Net communications in SNA networks.

For additional information on the AS/400 TCP/IP configuration ,please view the complete document link.


Article ID:
332
Published:
5/2/2003 5:43:33 PM
Last Modified:
5/2/2003 6:15:21 PM
Issue Type:
Configuration