problem with vm vtam on tserver

Discussion:

(too old to reply)

Franz Josef Pohlen

2006-02-16 21:59:56 UTC

Hi listers,

I cannot get my ethernet adapter to work. If I activate it it gets a sense
081c0000
IST093I ETH1XCA ACTIVE
IST380I ERROR FOR ID = L0E40000 - REQUEST: ACTLINK, SENSE: 081C0000

The display shows lines never active

IST097I DISPLAY ACCEPTED
IST075I NAME = ETH1XCA, TYPE = XCA MAJOR NODE
IST486I STATUS= ACTIV, DESIRED STATE= ACTIV
IST1021I MEDIUM=CSMA/CD,ADAPNO= 1,CUA=0E40,SNA SAP= 4
IST654I I/O TRACE = OFF, BUFFER TRACE = OFF
IST170I LINES:
IST232I L0E40000, NEVAC
IST232I L0E40001, NEVAC
IST232I L0E40002, NEVAC
IST232I L0E40003, NEVAC
IST232I L0E40004, NEVAC
IST232I L0E40005, NEVAC
IST232I L0E40006, NEVAC
IST232I L0E40007, NEVAC
IST232I L0E40008, NEVAC
IST232I L0E40009, NEVAC
IST232I L0E4000A, NEVAC
IST232I L0E4000B, NEVAC
IST232I L0E4000C, NEVAC
IST232I L0E4000D, NEVAC

This is the xca majornode
*
*
ETH1P PORT ADAPNO=1, <=== TKR-ADAPTERNUMMER *
CUADDR=E40, <=== SIEHE IOCP *
MEDIUM=CSMACD, <=== F"R ETHERNET *
SAPADDR=04, *
TIMER=60
*
* AUTOGEN=(ANZAHL PU'S,BEGINN LUNAME,BEGINN PUNAME)
* MAX ANZAHL PU'S=254
ETH1G GROUP ANSWER=ON, *
AUTOGEN=(50,L,Q), *
CALL=INOUT, *
DIAL=YES, *
DYNPU=YES, *
DYNPUPFX=CN, *
ISTATUS=ACTIVE
*
These are the relevant tserver's flex-es config statements (Flex-es v7)

channel(0) local # channel 0 a local channel

cu devad(0xE40,1) path(0) resource(cuSNAa) # xca For sna

cuSNAa: cu osasna # zVM Virtual CTC to local 3172 on Eth SNA
interface local(1)
options 'adapternumber=1'
device(00) osasna /dev/net1 # Ethernet Adapter
end cuSNAa

This is the ifconfig -a output to document that the adapters are not used by
unixware

lo0: flags=4049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet 127.0.0.1 netmask ff000000
inet/perf: recv size: 4096; send size: 8192; full-size frames: 1
inet/options: rfc1323
net0: flags=4043<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.50 netmask ffffff00 broadcast 192.168.0.255
inet/perf: recv size: 24576; send size: 24576; full-size frames: 1
inet/options: rfc1323
ether 00:09:6b:b0:5f:ca

My tcpip connection on /dev/net2 is working well.

The ethernet adapter is a dual port intel pro/100 as you can order with the
tserver. On the apar database I had already found an apar VM61479 which
pointed to the same error message but it did not help. There is no error
message on the flex console when activating the device. I have also tested
with cu type xcasna. It got the same result.

Can anybody give me an idea what I still can do to get the sna connection
working.

Mit freundlichen Grüßen / best regards

Franz Josef Pohlen

Stephen Frazier

2006-02-16 22:57:45 UTC

Permalink

Enter the CLI command "display devstate e40" to flexes.

Post by Franz Josef Pohlen
Hi listers,
I cannot get my ethernet adapter to work. If I activate it it gets a sense
081c0000
IST093I ETH1XCA ACTIVE
IST380I ERROR FOR ID = L0E40000 - REQUEST: ACTLINK, SENSE: 081C0000
These are the relevant tserver's flex-es config statements (Flex-es v7)
channel(0) local # channel 0 a local channel
cu devad(0xE40,1) path(0) resource(cuSNAa) # xca For sna
cuSNAa: cu osasna # zVM Virtual CTC to local 3172 on Eth SNA
interface local(1)
options 'adapternumber=1'
device(00) osasna /dev/net1 # Ethernet Adapter
end cuSNAa
This is the ifconfig -a output to document that the adapters are not used by
unixware
lo0: flags=4049<UP,LOOPBACK,RUNNING,MULTICAST> mtu 16384
inet 127.0.0.1 netmask ff000000
inet/perf: recv size: 4096; send size: 8192; full-size frames: 1
inet/options: rfc1323
net0: flags=4043<UP,BROADCAST,RUNNING,MULTICAST> mtu 1500
inet 192.168.0.50 netmask ffffff00 broadcast 192.168.0.255
inet/perf: recv size: 24576; send size: 24576; full-size frames: 1
inet/options: rfc1323
ether 00:09:6b:b0:5f:ca
My tcpip connection on /dev/net2 is working well.
The ethernet adapter is a dual port intel pro/100 as you can order with the
tserver. On the apar database I had already found an apar VM61479 which
pointed to the same error message but it did not help. There is no error
message on the flex console when activating the device. I have also tested
with cu type xcasna. It got the same result.
Can anybody give me an idea what I still can do to get the sna connection
working.
Mit freundlichen Grüßen / best regards
Franz Josef Pohlen

--
Stephen Frazier
Information Technology Unit
Oklahoma Department of Corrections
3400 Martin Luther King
Oklahoma City, Ok, 73111-4298
Tel.: (405) 425-2549
Fax: (405) 425-2554
Pager: (405) 690-1828
email: stevef%doc.state.ok.us

Pohlen (Mailinglist)

2006-02-17 17:28:50 UTC

Permalink

Hi Stephen,

the response to display devstate e40 is before and after activating the
ETH1XCA majornode the same: "Filename: /dev/net1 State: OPEN". There comes
no error messages on the flexes console.

Franz Josef
----- Original Message -----
From: "Stephen Frazier" <***@doc.state.ok.us>
To: <VMESA-***@LISTSERV.UARK.EDU>
Sent: Thursday, February 16, 2006 11:57 PM
Subject: Re: [VMESA-L] problem with vm vtam on tserver

Post by Stephen Frazier
Enter the CLI command "display devstate e40" to flexes.

Stephen Frazier

2006-02-17 18:07:51 UTC

Permalink

That is good. If the state had not been open then we would have found the
problem. VTAM is telling you that there is nothing on the other end of the cable
to talk to. Or nothing that it recognizes. What is out there and is it
configured correctly to talk to VTAM?

Post by Pohlen (Mailinglist)
Hi Stephen,
the response to display devstate e40 is before and after activating the
ETH1XCA majornode the same: "Filename: /dev/net1 State: OPEN". There comes
no error messages on the flexes console.
Franz Josef

Pohlen (Mailinglist)

2006-02-17 23:27:17 UTC

Permalink

There is nothing who wants to talk to VTAM at the moment. VTAM has to wait
for incoming connections e.g. from a 3270 emulation. But if the lines are
not active, there cannot be a connection established. It is the same as a
real OSA. The receiver in the error message description is the adapter
itself which does not respond. The XCA is only the door through which others
can connect to VTAM, but the door must be open i.e. the lines of the XCA
definition must be active first.

regards

Franz Josef Pohlen

----- Original Message -----
From: "Stephen Frazier" <***@doc.state.ok.us>
To: <VMESA-***@LISTSERV.UARK.EDU>
Sent: Friday, February 17, 2006 7:07 PM
Subject: Re: [VMESA-L] problem with vm vtam on tserver

Post by Stephen Frazier
That is good. If the state had not been open then we would have found the
problem. VTAM is telling you that there is nothing on the other end of the cable
to talk to. Or nothing that it recognizes. What is out there and is it
configured correctly to talk to VTAM?