I am seeing the following error when attempting to connect to RDzUT via RDz:

Failed to connect to the daemon on 192.168.1.2 using port 4035 with an unexpected exception

Details:

java.net.SocketTimeoutException: Read timed out java.net.SocketTimeoutException: Read timed out at java.net.SocketInputStream.read(Unknown Source) at java.net.SocketInputStream.read(Unknown Source) at java.io.DataInputStream.readByte(Unknown Source) at com.ibm.etools.zseries.util.DStoreWithSSHConnectorService.readString(Unknown Source) at com.ibm.etools.zseries.util.DStoreWithSSHConnectorService.launchServer(Unknown Source) at com.ibm.etools.zseries.util.DStoreWithSSHConnectorService.launchServer(Unknown Source) at org.eclipse.rse.connectorservice.dstore.DStoreConnectorService.connectWithDaemon(Unknown Source) at org.eclipse.rse.connectorservice.dstore.DStoreConnectorService.internalConnect(Unknown Source) at org.eclipse.rse.core.subsystems.AbstractConnectorService$1.run(Unknown Source) at org.eclipse.rse.core.subsystems.AbstractConnectorService$SafeRunner.run(Unknown Source) at org.eclipse.rse.core.subsystems.AbstractConnectorService.connect(Unknown Source) at org.eclipse.rse.core.subsystems.SubSystem.connect(Unknown Source) at com.ibm.ftt.rse.mvs.client.subsystems.MVSFileSubSystem.connect(Unknown Source) at org.eclipse.rse.internal.ui.view.SystemViewLabelAndContentProvider$1.run(Unknown Source) at org.eclipse.core.internal.jobs.Worker.run(Unknown Source)

Also, I notice the following error message repeat in the MVS console every time I attempt to connect with RDz:

11.50.00 STC00048  +FEK210I 5026089 canceled owing to duplicate logon 11.51.14 STC00040  +FEK210I 6456986 canceled owing to duplicate logon

I'm fairly certain at this point that it is not a network or service configuration issue, as the all the IVP processes return success.
Also, I can ping, telnet, ftp, and x3270 connect through the TAP tunnel from my host linux to z/OS.

Could it be that my host machine hardware is just not up to snuff when it comes to processing the connection? The read timeout seems to indicate this...

Thank you for your assistance.
-Vance

This looks like a network issue. Can you ping to/from the UT box from another machine using the 192.168.1.2 address? The TAP interface doesn't intersect with the regular OSA address above so you need to make sure the OSA address works as well.

RDzJohn

John,

I will not be able to confirm until later this afternoon, but I can say with almost 100% certainty that there is no network connectivity beyond the TAP/TUN interface. We are implementing Scenario #2, and only expecting to be able to connect via RDz from the host Linux, nothing beyond that. The 3270 terminal inside RDz connects without any problems.

Thanks,
Vance

If this is the case then you cannot use the 192 address for anything. Start the RSED servers with the 10. address of your TAP interface and you should be able to connect from Linux.

RDzJohn

I should have indicated our configuration beforehand. The TAP interface is 192.168.1.1 (linux) and 192.168.1.2 (zOS). This afternoon I'll post all of my configurations if you like.

We use the 192.168.1.2 address to FTP the SMPE files across and also to connect to ISPF after IPL. Do we need to add any ports to the member inside in TCPPARMS where all the others are defined?

John, thanks again for the help. Following is our configuration (what I perceive to be relevant anyways, please let me know if there's anything else I should list):

Device Map:

... [manager]          # define network adapter (OSA) for communication with host linux name awsosa 22 --path=A0 --pathtype=OSD --tunnel_intf=y --tunnel_ip=192.168.1.1 --tunnel_mask=255.255.255.0 device 400 osa osa device 401 osa osa device 402 osa osa ...

After IPL, from Linux:

$ /sbin/ifconfig ... tap0      Link encap:Ethernet  HWaddr 2A:EE:57:CB:37:B8 inet addr:192.168.1.1  Bcast:192.168.1.255  Mask:255.255.255.0 inet6 addr: fe80::28ee:57ff:fecb:37b8/64 Scope:Link UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1 RX packets:6 errors:0 dropped:0 overruns:0 frame:0 TX packets:34 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:500 RX bytes:360 (360.0 b)  TX bytes:6101 (5.9 Kb) ...

$ ping 192.168.1.2 PING 192.168.1.2 (192.168.1.2) 56(84) bytes of data. 64 bytes from 192.168.1.2: icmp_req=1 ttl=64 time=37.1 ms 64 bytes from 192.168.1.2: icmp_req=2 ttl=64 time=28.9 ms 64 bytes from 192.168.1.2: icmp_req=3 ttl=64 time=3.89 ms

USER.TCPPARMS(PROFILE):

000100 ARPAGE 5 ; 000200 DATASETPREFIX TCPIP ; 000300 AUTOLOG 5 ; 000400     FTPD JOBNAME FTPD1   ; FTP Server 000500     PORTMAP ; Portmap Server 000600 ENDAUTOLOG ; 000700 PORT ; 000800      7 UDP MISCSERV            ; Miscellaneous Server 000900      7 TCP MISCSERV            ; 001000      9 UDP MISCSERV            ; 001100      9 TCP MISCSERV            ; 001200     19 UDP MISCSERV            ; 001300     19 TCP MISCSERV            ; 001400     20 TCP OMVS      NOAUTOLOG ; FTP Server 001500     21 TCP OMVS                ; FTP Server 001600     23 TCP TN3270              ; Telnet Server 001700     25 TCP SMTP                ; SMTP Server 001800     53 TCP NAMESRV             ; Domain Name Server 001900     53 UDP NAMESRV             ; Domain Name Server 002000     69 UDP OMVS                ; OE TFTP SERVER 002100     80 TCP OMVS                ; OE WEB SERVER 002200    111 TCP PORTMAP             ; Portmap Server 002300    111 UDP PORTMAP             ; Portmap Server 002400    135 UDP LLBD                ; NCS Location Broker 002500    161 UDP OSNMPD              ; SNMP Agent 002600    162 UDP SNMPQE              ; SNMP Query Engine 002700    433 TCP OMVS                ; OE WEB Server 002800    443 TCP OMVS                ; Secure Server 002900    512 TCP RXSERVE             ; Remote Execution Server 003000    513 UDP OMVS                ; OE RLOGIN SERVER 003100    514 UDP OMVS                ; OE syslog server 003200    514 TCP RXSERVE             ; Remote Execution Server 003300    515 TCP LPSERVE             ; LPD Server 003400    520 UDP OROUTED             ; RouteD Server 003500    580 UDP NCPROUT             ; NCPROUTE Server 003600    750 TCP MVSKERB             ; Kerberos 003700    750 UDP MVSKERB             ; Kerberos 003800    751 TCP ADM@SRV             ; Kerberos Admin Server 003900    751 UDP ADM@SRV             ; Kerberos Admin Server 004000 ;  1021 TCP OMVS                ; OE FTP SERVER 004100    1023 TCP OMVS                ; OE TELNET SERVER 004200    1023 UDP OMVS                ; OE TELNET SERVER 004300    1024 TCP OMVS                ; OE SERVICES 004400    1415 TCP CSQ1CHIN            ; CSQ1 MQ TCP Listener 004500    3000 TCP CICSTCP             ; CICS Socket 004600    32200 TCP BBN7ACRS             ; Daemon IP port 004700    32201 TCP BBN7ACRS NODELAYACKS ; Daemon SSL port 004800    32202 TCP BBNS001            ; SOAP JMX Connector port 004900    32203 TCP BBNS001            ; ORB port 005000    32204 TCP BBNS001 NODELAYACKS ; ORB SSL port 005100    32205 TCP BBNS001             ; Administrative console port 005200    32206 TCP BBNS001 NODELAYACKS ; Administrative console secure port 005300    32207 TCP BBNS001             ; HTTP transport port 005400    32208 TCP BBNS001 NODELAYACKS ; HTTPS transport port 005500    32209 TCP BBNS001             ; Administrative Local Port 005600    32210 TCP BBNS001             ; High availability manager comm port 005700    32211 TCP BBNS001             ; Service Integration port 005800    32212 TCP BBNS001 NODELAYACKS ; Service Integration secure port 005900    32213 TCP BBNS001S            ; Service Integration MQ interoper 006000    32214 TCP BBNS001S NODELAYACKS ; Service Integration MQ inter secure 006100    32215 TCP BBNS001            ; Session Initiation Protocol (SIP) 006200    32216 TCP BBNS001 NODELAYACKS ; Session Init Protocol (SIP) secure 006300    8879 TCP BBODMGR             ; SOAP JMX Connector port 006400    7277 TCP BBODMGR             ; Cell Discovery port 006500    9809 TCP BBODMGR             ; ORB port 006600    9090 TCP BBODMGR             ; HTTP port 006700    9043 TCP BBODMGR             ; HTTPS port 006800    5755 TCP BBODMNC             ; Daemon port 006900    5756 TCP BBODMNC             ; Daemon SSL port 007000 ; WAS Base Node entries 007100   8880 TCP BBOS001             ; SOAP JMX Connector port 007200  ;2809 TCP BBOS001             ; ORB port (COMMENT THIS ONE OUT) 007300   9080 TCP BBOS001             ; HTTP port 007400   9443 TCP BBOS001             ; HTTPS port 007500   5655 TCP BBODMNB             ; Daemon port 007600   5656 TCP BBODMNB             ; Daemon SSL port 007700 ; WAS ND Node entries 007800   8879 TCP BBODMGR             ; SOAP JMX Connector port 007900   7277 TCP BBODMGR             ; Cell Discovery port 008000   9809 TCP BBODMGR             ; ORB port 008100   9090 TCP BBODMGR             ; HTTP port 008200   9043 TCP BBODMGR             ; HTTPS port 008300   5755 TCP BBODMNC             ; Daemon port 008400   5756 TCP BBODMNC             ; Daemon SSL port 008500 ; WAS Federation entries 008600   8878 TCP BBON001             ; SOAP JMX Connector port 008700   7272 TCP BBON001             ; Node Discovery port 008800   2809 TCP BBON001             ; Node Agent s ORB port 008900   9810 TCP BBOS001             ; Base Server s ORB port 009000 SACONFIG DISABLED ; 009100 ;This device defines the tunnel 009200 DEVICE PORTA  MPCIPA ; 009300 LINK ETH1  IPAQENET PORTA ; 009400 HOME 192.168.1.2 ETH1 ; 009900 BEGINRoutes ; 010000 ;     Destination   SubnetMask    FirstHop       LinkName  Size 010100 ROUTE 192.168.1.0 255.255.255.0       =          ETH1 MTU  1492 ; 010400 ROUTE DEFAULT                    192.168.1.1     ETH1 MTU  1492 ; 010500 ENDRoutes ; 010600 ITRACE OFF ; 010700 IPCONFIG NODATAGRAMFWD ; 010800 UDPCONFIG RESTRICTLOWPORTS ; 010900 TCPCONFIG RESTRICTLOWPORTS ; 011000 START PORTA ;

From TSO:

READY netstat route EZZ2350I MVS TCP/IP NETSTAT CS V1R11       TCPIP Name: TCPIP           18:19:42 EZZ2755I Destination        Gateway         Flags    Refcnt     Interface EZZ2756I -----------        -------         -----    ------     --------- EZZ2757I Default            192.168.1.1     UGS      0000000000 ETH1 EZZ2757I 127.0.0.1/32       0.0.0.0         UH       0000000002 LOOPBACK EZZ2757I 192.168.1.0/24     0.0.0.0         US       0000000000 ETH1 EZZ2757I 192.168.1.2/32     0.0.0.0         UH       0000000000 ETH1 READY netstat home EZZ2350I MVS TCP/IP NETSTAT CS V1R11       TCPIP Name: TCPIP           18:19:47 EZZ2700I Home address list: EZZ2701I Address          Link             Flg EZZ2702I -------          ----             --- EZZ2703I 192.168.1.2      ETH1             P EZZ2703I 127.0.0.1        LOOPBACK READY ping 192.168.1.1 CS V1R11: Pinging host 192.168.1.1 Ping #1 response took 0.019 seconds. READY

From OMVS:

fekfivpd:

IBMUSER:/Z111S/usr/lpp/rdz/bin: >fekfivpd Enter the path to the customized rsed.envvars: /usr/lpp/rdz/etc/rdz executed on ADCD -- Mon Apr 9 13:24:28 CDT 2012 executed by uid=0(START2) gid=0(SYS1) using /usr/lpp/rdz/etc/rdz/rsed.envvars current address space size limit is 1647288320 (1571.0 MB) maximum address space size limit is 2147483647 (2048.0 MB) attempting to connect userid IBMUSER using port 4035 ... Password: SSL is disabled connected 1031 3658196 Success

fekfivpi:

IBMUSER:/Z111S/usr/lpp/rdz/bin: >fekfivpi Enter the path to the customized rsed.envvars: /usr/lpp/rdz/etc/rdz executed on ADCD -- Mon Apr 9 13:26:40 CDT 2012 executed by uid=0(START2) gid=0(SYS1) using /usr/lpp/rdz/etc/rdz/rsed.envvars current address space size limit is 1647288320 (1571.0 MB) maximum address space size limit is 2147483647 (2048.0 MB) ------------------------------------------------------------- /usr/lpp/rdz/etc/rdz/ISPF.conf content: ------------------------------------------------------------- ispllib=ISP.SISPLOAD ispmlib=ISP.SISPMENU isptlib=ISP.SISPTENU ispplib=ISP.SISPPENU ispslib=ISP.SISPSLIB sysproc=ISP.SISPCLIB,RDZUT.SFEKPROC ------------------------------------------------------------- Host install verification for RSE Review IVP log messages from HOST below : ------------------------------------------------------------- Service level 22Feb2011 RSE connection and base TSO/ISPF session initialization check only *** CHECK : ENVIRONMENT VARIABLES - key variables displayed below : Server PATH         = .:/usr/lpp/java/J6.0/bin:/usr/lpp/rdz/bin:/usr/lpp/ispf/bi n:/bin:/usr/sbin STEPLIB = NONE Temporary directory = /tmp _CMDSERV_BASE_HOME  = /usr/lpp/ispf _CMDSERV_CONF_HOME  = /usr/lpp/rdz/etc/rdz _CMDSERV_WORK_HOME  = /usr/lpp/rdz/var/rdz ------------------------------------------------------------- *** CHECK : USS MODULES Checking ISPF Directory : /usr/lpp/ispf Checking modules in /usr/lpp/ispf/bin directory Checking for ISPF configuration file ISPF.conf RC=0 MSG: SUCCESSFUL ------------------------------------------------------------- *** CHECK : TSO/ISPF INITIALIZATION ( TSO/ISPF session will be initialized ) RC=0 MSG: SUCCESSFUL ------------------------------------------------------------- *** CHECK: Shutting down TSO/ISPF IVP session RC=0 MSG: SUCCESSFUL ------------------------------------------------------------- Host installation verification completed successfully -------------------------------------------------------------

fekfivpt:

IBMUSER:/Z111S/usr/lpp/rdz/bin: >fekfivpt Enter the path to the customized rsed.envvars: /usr/lpp/rdz/etc/rdz executed on ADCD -- Mon Apr 9 13:31:05 CDT 2012 executed by uid=0(START2) gid=0(SYS1) using /usr/lpp/rdz/etc/rdz/rsed.envvars current address space size limit is 1647288320 (1571.0 MB) maximum address space size limit is 2147483647 (2048.0 MB) ------------------------------------------------------------- TCP/IP resolver configuration (z/OS UNIX search order): ------------------------------------------------------------- Resolver Trace Initialization Complete -> 2012/04/09 12:31:06.424672 res_init Resolver values: Global Tcp/Ip Dataset  = USER.TCPPARMS(TCPDATA) Default Tcp/Ip Dataset = None Local Tcp/Ip Dataset   = /etc/resolv.conf Translation Table      = TCPIP.STANDARD.TCPXLBIN UserId/JobName         = IBMUSER Caller API             = LE C Sockets Caller Mode            = EBCDIC (G) DataSetPrefix = TCPIP (G) HostName      = RDZUT0 (G) TcpIpJobName  = TCPIP (G) DomainOrigin  = WTCS.WTAMU.EDU (G) NameServer    = 127.0.0.1         EDNS0 Support = Unknown (*) NsPortAddr    = 53            (G) ResolverTimeout    = 10 (G) ResolveVia    = UDP           (G) ResolverUdpRetries = 1 (*) Options NDots = 1 (*) SockNoTestStor (G) AlwaysWto     = NO            (L) MessageCase        = MIXED (*) LookUp        = DNS LOCAL (*) Cache res_init Succeeded res_init Started: 2012/04/09 12:31:06.591375 res_init Ended: 2012/04/09 12:31:06.591481 *************************************************************************** MVS TCP/IP NETSTAT CS V1R11       TCPIP Name: TCPIP           14:31:07 Tcpip started at 18:01:22 on 04/09/2012 with IPv6 disabled ------------------------------------------------------------- host IP address: ------------------------------------------------------------- hostName=RDZUT0 hostAddr=127.0.0.1 bindAddr=127.0.0.1 localAddr=127.0.0.1 Success, addresses match

fekfivpj:

IBMUSER:/Z111S/usr/lpp/rdz/bin: >fekfivpj Enter the path to the customized rsed.envvars: /usr/lpp/rdz/etc/rdz executed on ADCD -- Mon Apr 9 13:34:01 CDT 2012 executed by uid=0(START2) gid=0(SYS1) using /usr/lpp/rdz/etc/rdz/rsed.envvars current address space size limit is 1647288320 (1571.0 MB) maximum address space size limit is 2147483647 (2048.0 MB) testing JES Job Monitor on port 6715... hostName=RDZUT0 hostAddr=192.168.1.2 Waiting for JES Job Monitor response... ACKNOWLEDGE01v03 Success

fekfivpl:

IBMUSER:/Z111S/usr/lpp/rdz/bin: >fekfivpl Enter the path to the customized rsed.envvars: /usr/lpp/rdz/etc/rdz executed on ADCD -- Mon Apr 9 13:34:59 CDT 2012 executed by uid=0(START2) gid=0(SYS1) using /usr/lpp/rdz/etc/rdz/rsed.envvars current address space size limit is 1647288320 (1571.0 MB) maximum address space size limit is 2147483647 (2048.0 MB) testing RSE Lock Daemon on port 4036... hostName=RDZUT0 hostAddr=192.168.1.2 Registering user IBMUSER to Lock Daemon... Waiting for Lock Daemon response... Querying to Lock Daemon... Waiting for Lock Daemon response... IBMUSER Unregistering user IBMUSER from Lock Daemon... Waiting for Lock Daemon response... Querying to Lock Daemon... Waiting for Lock Daemon response... Success

Please provide the output of the linux find_io command. Do you have iptables turned on? If so, have you opened all of the RDz ports?

Please provide the output of TSO HOMETEST, the TCPIP Joblog, and the VTAM joblog.

RDzJohn

John, interesting development after our class met today. Just as an attempt to move forward we switched over to the scenario #4 network configuration. After getting a few lab machines configured, we successfully connected to each others UT instance. Then, someone attempted to connect back through their TAP interface and that worked as well.

Not sure why it would make a difference, maybe you can shed some light on that. Here's the logs you asked for:

find_io:

ibmsys1@ECS142-IS:~> find_io   Interface Name tap0 -> MAC addr 02:a0:a0:a0:a0:a0 Flags = 0 Interface Name tap1 -> MAC addr 02:a1:a1:a1:a1:a1 Flags = 0 Interface Name tap2 -> MAC addr 02:a2:a2:a2:a2:a2 Flags = 0 Interface Name tap3 -> MAC addr 02:a3:a3:a3:a3:a3 Flags = 0 Interface Name eth1 -> MAC addr 00:1e:4f:9e:e2:90 Flags = 0     ====== Start of Chpid Registry Information =====   Total Interfaces Found =    5 Chpid Num  Type  State  Slot Num  Port Num    Card    Interface Name =========  ====  =====  ========  ========  ========  ============== a0       0     808     ff         0      Tun/Tap        tap0 a1       0     808     ff         0      Tun/Tap        tap1 a2       0     808     ff         0      Tun/Tap        tap2 a3       0     808     ff         0      Tun/Tap        tap3 f0       0     808     ff         1       Wired         eth1     ====== End of Chpid Registry Information =====       ====== io_slot.dat file created with registry information==

TSO hometest:

hometest EZA0619I Running IBM MVS TCP/IP CS V1R11 TCP/IP Configuration Tester EZA0621I The FTP configuration parameter file used will be "TCPIP.FTP.DATA". EZA0602I TCP Host Name is: RDZUT0 EZA0605I Using Name Server to Resolve RDZUT0 EZA0611I The following IP addresses correspond to TCP Host Name: RDZUT0 EZA0612I 127.0.0.1 EZA0614I The following IP addresses are the HOME IP addresses defined in PROFIL E .TCPIP: EZA0615I 192.168.1.2 EZA0615I 10.152.106.49 EZA0615I 127.0.0.1 EZA0618I All IP addresses for RDZUT0 are in the HOME list! EZA0622I Hometest was successful - all Tests Passed! READY

As for the joblogs, maybe you can help on that too. Whenever we look at SDSF, the only thing with any output is the system log. It's like sysout=* doesn't exist... or something (sorry, I'm a total noob!)

Some interesting things here. HOMETEST reports that your Home IP address as reported by GetHostId is the loopback address. This is incorrect as it need to return 192.168.1.2. Do you have a nameserver specified on NAMESERVER or NSINTERADDR in your TCPIP.DATA file? Is it reachable and does your host name resolve to RDZUT0? I suspect not. On a standalone system I usually comment out NSINTERADDR and instead use a HOST file. CH 14 of z/OS Communications Server: IP Configuration Guide, SC31-8775-20, describes the Resolver and how to set it up so that it resolves your hostname correctly. Pay particular attention to the search orders for z/OS and Unix configuration files, and the fact that you have to get both setups correct for all things to work properly. If you want to see exactly what the Resolver is doing, the following article details how to turn on Resolver tracing -

http://publibz.boulder.ibm.com/cgi-bin/bookmgr_OS390/BOOKS/F1A1C5A0/3.33.2?SHELF=F1A1BKC0&DT=20100402140156

RDzJohn