Troubleshooting
Problem
This document contains a list of things to consider when configuring AnyNet bewteen IBM OS/400 or IBM i5/OS and VTAM
Resolving The Problem
|
Important Note: Starting in i 7.1, AnyNet (a method used to run SNA communications traffic over IP) is no longer supported. Users of AnyNet are encouraged to migrate to Enterprise Extender as a replacement. For information about migrating to Enterprise Extenders from AnyNet, see the Migrating from AnyNet to Enterprise Extender topic in the IBM i Information Center. |
It is possible to configure AnyNet between IBM OS/400 or i5/OS and MVS/VTAM. Possible uses include APPC/APPN-only connection to applications such as CICS or other transaction type applications.
Note: AnyNet is configurable for APPC controllers only. There is no AnyNet support for HOST controller descriptions.
To configure AnyNet between the OS/400 or i5/OS system and MVS, the following host software is required:
| V4R2 of ACF/VTAM for MVS/ESA Program # 5695-117 | |
| V2R2.1 of IBM TCP/IP for MVS/ESA Program # 5735-HAL | |
| V3R1 of IBM TCP/IP for MVS/ESA Program #5655-HAL | |
| Version 3 Release 1 or higher of the OS/400 or i5/OS Operating System Program # 57xx- SS1 | 5763-SS1 (R310 or R320) 5716-SS1 (R360 or R370) 5769-SS1 (R410 or higher) |
Configuration Matching Parameters:
OS/400 or i5/OS VTAM MVS/ESA
| DSPNETA Local network ID USIBM Local control point name AS400 Default local location AS400 Default mode BLANK | VBUILD TYPE=TCP, (required) CONTIMER=30, DNSUFX= IBM.COM, (required) EXTIMER=3, IATIMER=120, PORT=397, (required) TCB=10, TCPIPJOB=T1ATCP MVSGNSIP GROUP ISTATUS=ACTIVE Groupname MVSLSNIP LINE ISTATUS=ACTIVE Linename MVSPSNIP PU ISTATUS=ACTIVE PUNAME |
| TCPIP Configuration INTERNET ADDRESS 9.5.xxx.xx | VTAM TCP/IP Host Table INTERNET ADDRESS 9.5.yyy.yy |
| Controller Description CTLD ANYNETCTL (3) CATEGORY APPC LINKTYPE *ANYNW ONLINE *YES RMTNETID USIBM (1) RMTCPNAME ANYNETCP (2) | |
| Device Description DEVD ANYDEV CATEGORY APPC RMTLOCNAME ANYNETMVS (4) ONLINE *YES LCLLOCNAME ANYAS400 (5) RMTNETID USIBM (1) CTL ANYNETCTL (3) | VBUILD TYPE=CDRSC (1) NETWORK NETID=USIBM (5) ANYAS400 CDRSC ALSLIST=RAIPSNIP, ALSREQ=YES |
| REMOTE CONFIGUARION LIST REMOTE LOCATION ANYNETMVS (4) REMTOE NETWORK ID USIBM (1) LOCAL LOCATION ANYAS400 (5) REMOTE CONTROL POINT ANYNETCP (2) CONTROL POINT NETID USIBM (1) | |
| Host Table Entry 9.5.yyy.yy ANYNETMVS.USIBM.SNA.IBM.COM (4) | TCP/IP Host Table for AnyNet/MVS (5) HOST: 9.5.xxx.xx: ANYAS400.USIBM.SNA.IBM.COM |
| Notes: 1. VTAM on the mainframe must have a VBUILD TYPE=TCP. 2. When using APPC over TCP/IP, VTAM sees any remote LUs as independent LUs which are defined as CDRCSs. 3. The name label of the CDRSC definition statement must be the remote ILU name (Local Location Name in the OS/400 or i5/OS remote Configuration List). 4. ALSREQ=YES to use the Predefined list. |
To activate the AnyNet connection to MVS/VTAM, do the following:
On OS/400 or i5/OS On MVS/VTAM
| 1. Make sure that the Network Attribute for Allow AnyNet is set to *YES (ALWANYNET *Yes) 2. Vary on the AnyNet® Controller. 3. Verify that job QAPPCTCP is active in subsystem QSYSWRK 4. Verify that NETSTAT, Option 3 shows 2 ports named APPCove, one in UDP and one in LISTEN. | 1.Verify that the group,line and PU defined on the VBUILD TYPE=TCP are Active. 2.Verify that the CDRCSs must have a status of ACTIV (D NET,ID=ANYAS400) |
Once the above steps are complete, AnyNet should working between OS/400 or i5/OS and MVS/VTAM.
[{"Type":"MASTER","Line of Business":{"code":"LOB57","label":"Power"},"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SWG60","label":"IBM i"},"Platform":[{"code":"PF012","label":"IBM i"}],"Version":"6.1.0"}]
Historical Number
16311114
Was this topic helpful?
Document Information
Modified date:
18 December 2019
UID
nas8N1018028