ch-0.0.0e21 (TX in ch_action_txretry): Busy Problem

View: New views

2 Messages — Rating Filter: Alert me

ch-0.0.0e21 (TX in ch_action_txretry): Busy Problem

by Kayhan :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

While attempting to install SuSE SLES9 /S390 with CTC connection under
zVM in Hercules, I have got the following message:

ch-0.0.0e21 (TX in ch_action_txretry): Busy Ð

How can I solve this problem?

Regards,

Kayhan Tanrýverir

CTC channels are 0E20 :read and 0E21:write

The CTC device statement(s) from my Hercules configuration file:

0E20-0E21 CTCI -n 00-15-B7-FF-3F-61 192.168.10.85 0.0.0.0

The TCP/IP configuration statements for VM operating system my running
under Hercules:

DEVICE DEVÞ0E20 CTC E20LINK ETH0 CTC 0 DEVÞ0E20 MTU
1500... HOME192.168.10.85 255.255.255.0 ETH0... GATEWAY192.168.10.1
255.255.255.0 = ETH0 1500 ...DEFAULTNET 192.168.10.1 ETH0
1500 ...START DEVÞ0E20

When I login to Linux machine I have got the correct messages:

CTCA 0E20 DEFINED CTCA 0E21 DEFINED
CTCA 0E21 COUPLED BY LINUX43 0E20 CTCA 0E20 COUPLED TO LINUX43
0E21 CTCA 0E20 COUPLED BY LINUX43 0E21 CTCA 0E21 COUPLED TO
LINUX43 0E20

IP address of LINUX43 is : 192.168.10.85

Default gateway is : 192.168.10.1

It is successfully ping 192.168.10.1 from 192.168.10.85

DTCPARMS member is below:
**************************************************************** *
SYSTEM DTCPARMS created by DTCIPWIZ EXEC on 31 Oct 2009 *
Configuration program run by MAINT at 19:26:38
****************************************************************
nick.TCPIP :type.server
:class.stack
:attach.0E20-0E21

****** SLES9 Installation Messages *******

ctc0: read: ch-0.0.0e20, write: ch-0.0.0e21, proto: 3

ctc0 detected.

ctc0 is available, continuing with network setup.

Please enter your full host name, e.g. 'linux.example.com'
(linux.example.com):

linux.vm

Please enter your IP address, e.g. '192.168.0.1' (192.168.0.1):
192.168.10.86

Please enter the IP address of your peer, e.g. '192.168.0.254'
(192.168.0.254):

192.168.10.1

Please enter the IP address of the DNS server or 'none' for no DNS
(none): none

Please enter the MTU (Maximum Transfer Unit),

leave blank for default: (1500): 1500

Trying to ping my IP address:

PING 192.168.10.86 (192.168.10.86) 56(84) bytes of data.

64 bytes from 192.168.10.86: icmp_seq=1 ttl=64 time=0.789 ms

64 bytes from 192.168.10.86: icmp_seq=2 ttl=64 time=1.09 ms

64 bytes from 192.168.10.86: icmp_seq=3 ttl=64 time=1.38 ms

--- 192.168.10.86 ping statistics ---

3 packets transmitted, 3 received, 0% packet loss, time 2062ms

rtt min/avg/max/mdev = 0.789/1.088/1.384/0.245 ms

Trying to ping the IP address of the peer:

PING 192.168.10.1 (192.168.10.1) 56(84) bytes of data.

ch-0.0.0e21 (TX in ch_action_txretry): Busy Ð

--- 192.168.10.1 ping statistics ---

10 packets transmitted, 0 received, 100% packet loss, time 9147ms

Warning: The peer address 192.168.10.1 did not ping.

Statistics from ctc0:

rx_dropped: 1

rx_length_errors: 1

[Non-text portions of this message have been removed]

Re: ch-0.0.0e21 (TX in ch_action_txretry): Busy Problem

by jsganino-2 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Kayhan,

It sounds like you are trying to read from your write side, and write to your read side. In a CTC connection, there are two channels, in your case, E20 and E21, to provide a read path and a write path for the network traffic. By convention, TCPIP reads from the lower address and writes to the upper address. This results pretty quickly in both ends reading from the E20 CTC and writing to the E21 CTC. My first thought to fix this paralleled yours - switch the connections somewhere:

> CTCA 0E21 COUPLED BY LINUX43 0E20
> CTCA 0E20 COUPLED TO LINUX43 0E21

It didn't work for me, either. But, I found (with some help from the folks here) that there is a 0/1 switch in the PROFILE TCPIP device definitions for a CTC

> DEVICE DEVÞ0E20 CTC E20LINK ETH0 CTC 0

Try

> DEVICE DEVÞ0E20 CTC E20LINK ETH0 CTC 1

and couple the CTCA's straight (E20 to E20 and E21 to E21) and see what happens.

Good Luck,

Jim

--- In hercules-390@..., "k_tanriverir" <k_tanriverir@...> wrote:

>
>
> While attempting to install SuSE SLES9 /S390 with CTC connection under
> zVM in Hercules, I have got the following message:
>
> ch-0.0.0e21 (TX in ch_action_txretry): Busy Ð
>
>
>
> How can I solve this problem?
>
> Regards,
>
>
>
> Kayhan Tanrýverir
>
>
>
> CTC channels are 0E20 :read and 0E21:write
>
>
>
> The CTC device statement(s) from my Hercules configuration file:
>
>
> 0E20-0E21 CTCI -n 00-15-B7-FF-3F-61 192.168.10.85 0.0.0.0
>
>
> The TCP/IP configuration statements for VM operating system my running
> under Hercules:
>
>
> DEVICE DEVÞ0E20 CTC E20LINK ETH0 CTC 0 DEVÞ0E20 MTU
> 1500... HOME192.168.10.85 255.255.255.0 ETH0... GATEWAY192.168.10.1
> 255.255.255.0 = ETH0 1500 ...DEFAULTNET 192.168.10.1 ETH0
> 1500 ...START DEVÞ0E20
>
>
> When I login to Linux machine I have got the correct messages:
>
>
> CTCA 0E20 DEFINED CTCA 0E21 DEFINED
> CTCA 0E21 COUPLED BY LINUX43 0E20 CTCA 0E20 COUPLED TO LINUX43
> 0E21 CTCA 0E20 COUPLED BY LINUX43 0E21 CTCA 0E21 COUPLED TO
> LINUX43 0E20
>
>
> IP address of LINUX43 is : 192.168.10.85
>
> Default gateway is : 192.168.10.1
>
> It is successfully ping 192.168.10.1 from 192.168.10.85
>
>
>
> DTCPARMS member is below:
> **************************************************************** *
> SYSTEM DTCPARMS created by DTCIPWIZ EXEC on 31 Oct 2009 *
> Configuration program run by MAINT at 19:26:38
> ****************************************************************
> nick.TCPIP :type.server
> :class.stack
> :attach.0E20-0E21
>
>
> ****** SLES9 Installation Messages *******
>
> ctc0: read: ch-0.0.0e20, write: ch-0.0.0e21, proto: 3
>
> ctc0 detected.
>
> ctc0 is available, continuing with network setup.
>
>
>
> Please enter your full host name, e.g. 'linux.example.com'
> (linux.example.com):
>
> linux.vm
>
> Please enter your IP address, e.g. '192.168.0.1' (192.168.0.1):
> 192.168.10.86
>
> Please enter the IP address of your peer, e.g. '192.168.0.254'
> (192.168.0.254):
>
> 192.168.10.1
>
> Please enter the IP address of the DNS server or 'none' for no DNS
> (none): none
>
> Please enter the MTU (Maximum Transfer Unit),
>
> leave blank for default: (1500): 1500
>
>
>
> Trying to ping my IP address:
>
> PING 192.168.10.86 (192.168.10.86) 56(84) bytes of data.
>
> 64 bytes from 192.168.10.86: icmp_seq=1 ttl=64 time=0.789 ms
>
> 64 bytes from 192.168.10.86: icmp_seq=2 ttl=64 time=1.09 ms
>
> 64 bytes from 192.168.10.86: icmp_seq=3 ttl=64 time=1.38 ms
>
>
>
> --- 192.168.10.86 ping statistics ---
>
> 3 packets transmitted, 3 received, 0% packet loss, time 2062ms
>
> rtt min/avg/max/mdev = 0.789/1.088/1.384/0.245 ms
>
> Trying to ping the IP address of the peer:
>
> PING 192.168.10.1 (192.168.10.1) 56(84) bytes of data.
>
> ch-0.0.0e21 (TX in ch_action_txretry): Busy Ð
>
>
>
> --- 192.168.10.1 ping statistics ---
>
> 10 packets transmitted, 0 received, 100% packet loss, time 9147ms
>
>
>
> Warning: The peer address 192.168.10.1 did not ping.
>
> Statistics from ctc0:
>
> rx_dropped: 1
>
> rx_length_errors: 1
>
>
>
>
>
>
>
> [Non-text portions of this message have been removed]
>