The only messages i get are:
ch-0d10: Interface disc. or Sel. reset (remote)
ch-0d11: Interface disc. or Sel. reset (remote)
and
ch-0c20: System reset (remote)
ch-0c21: System reset (remote)
In each Lpar I get:
ctc0 Link encap:Serial Line IP
inet addr:192.168.192.141 P-t-P:192.168.192.140
Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MTU:32760 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:16 dropped:16 overruns:0 carrier:16
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
ctc0 Link encap:Serial Line IP
inet addr:192.168.192.140 P-t-P:192.168.192.141
Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MTU:32760 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:16 dropped:16 overruns:0 carrier:16
collisions:0 txqueuelen:100
RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)
I've done several tests
- with and without chandev=noauto parameter
- with same unitadd for c20-c21 and d10-d11
- with ctc0,0xd11,0xd10 or ctc0,0xd10,0xd11
Gerard
-----Message d'origine-----
De�: Linux on 390 Port [mailto:[EMAIL PROTECTED]] De la part de
Peter E. Abresch Jr. - at Pepco
Envoy�: mercredi 15 mai 2002 15:16
��: [EMAIL PROTECTED]
Objet�: RE : ESCON CTC between two LPAR LINUX (SLES 2.4.7)
In my exuberance to provide assistance, I missed the unit address. I
have
not seen it define like that before but cannot think of any reason that
it
should not work since it is the unit address that must match. Does your
CTC show up when you enter IFCONFIG? Any other error messages? There is
not much to go on.
Peter
Monteleone <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port <[EMAIL PROTECTED]>
05/15/2002 08:34 AM
Please respond to Linux on 390 Port
To: [EMAIL PROTECTED]
cc:
Subject: RE : ESCON CTC between two LPAR LINUX (SLES
2.4.7)
Hello Peter,
I don't understand your answer,
D10 (unitadd=01) chpid(99 CNC) is the read device and point to c20
(unitadd=00) chpid(98 CTC)
D11 (unitadd=00) chpid(99 CNC) is the write device and point to c21
(unitadd=01) chpid(98 CTC)
I believed that the crossing was done thru the unitadd parameter, wasn't
it?
Where do you see my mistake?
I've got no problem between z/OS and Linux where the read or write
option is controlled with the TCPIP parameter (0 = read, 1 = write).
Have you got a sample?
Thanks in advance.
-----Message d'origine-----
De�: Linux on 390 Port [mailto:[EMAIL PROTECTED]] De la part de
Peter E. Abresch Jr. - at Pepco
Envoy�: mercredi 15 mai 2002 14:03
��: [EMAIL PROTECTED]
Objet�: Re: ESCON CTC between two LPAR LINUX (SLES 2.4.7)
I have CTCs working fine between a z/OS system and Linux. What I see
that
is most glaring is that you have the read channel connected to a read
channel and a write channel connected to a write channel. Try reversing
the UCB address on one of your CTC definitions. The read channel must
connect to a write channel and a write channel must connect to a read
channel.
I also assume that everything else is configured correctly in the
rc.config. Try the ifconfig command to check the status. Let me know how
it goes. Good luck.
Peter
Monteleone <[EMAIL PROTECTED]>
Sent by: Linux on 390 Port <[EMAIL PROTECTED]>
05/15/2002 03:49 AM
Please respond to Linux on 390 Port
To: [EMAIL PROTECTED]
cc:
Subject: ESCON CTC between two LPAR LINUX (SLES 2.4.7)
I'm going to be crazy with this connection, Can you explain me what's
wrong with my definition please ?
I would like to establish a session between SYST & DEVS
RESOURCE PARTITION=((SYST,1),(DEVS,2),(PROD,3))
CHPID PATH=(98),SHARED,PARTITION=(SYST,DEVS,PROD),TYPE=CTC
CHPID PATH=(99),SHARED,PARTITION=(SYST,DEVS,PROD),TYPE=CNC
CNTLUNIT CUNUMBR=0C10,PATH=(98),UNITADD=((00,002)),CUADD=1, *
UNIT=SCTC
CNTLUNIT CUNUMBR=0C20,PATH=(98),UNITADD=((00,002)),CUADD=2, *
UNIT=SCTC
CNTLUNIT CUNUMBR=0C30,PATH=(98),UNITADD=((00,002)),CUADD=3, *
UNIT=SCTC
CNTLUNIT CUNUMBR=0D10,PATH=(99),UNITADD=((00,002)),CUADD=1, *
UNIT=SCTC
CNTLUNIT CUNUMBR=0D20,PATH=(99),UNITADD=((00,002)),CUADD=2, *
UNIT=SCTC
CNTLUNIT CUNUMBR=0D30,PATH=(99),UNITADD=((00,002)),CUADD=3, *
UNIT=SCTC
IODEVICE ADDRESS=(C10,002),UNITADD=00,CUNUMBR=(0C10),STADET=Y,*
PARTITION=(DEVS,PROD),UNIT=SCTC
IODEVICE ADDRESS=(C20,002),UNITADD=00,CUNUMBR=(0C20),STADET=Y,*
PARTITION=(SYST,PROD),UNIT=SCTC
IODEVICE ADDRESS=(C30,002),UNITADD=00,CUNUMBR=(0C30),STADET=Y,*
PARTITION=(SYST,DEVS),UNIT=SCTC
IODEVICE ADDRESS=(D10,001),UNITADD=01,CUNUMBR=(0D10),STADET=Y,*
PARTITION=(DEVS,PROD),UNIT=SCTC
IODEVICE ADDRESS=(D11,001),UNITADD=00,CUNUMBR=(0D10),STADET=Y,*
PARTITION=(DEVS,PROD),UNIT=SCTC
IODEVICE ADDRESS=(D20,001),UNITADD=01,CUNUMBR=(0D20),STADET=Y,*
PARTITION=(SYST,PROD),UNIT=SCTC
IODEVICE ADDRESS=(D21,001),UNITADD=00,CUNUMBR=(0D20),STADET=Y,*
PARTITION=(SYST,PROD),UNIT=SCTC
IODEVICE ADDRESS=(D30,001),UNITADD=01,CUNUMBR=(0D30),STADET=Y,*
PARTITION=(SYST,DEVS),UNIT=SCTC
IODEVICE ADDRESS=(D31,001),UNITADD=00,CUNUMBR=(0D30),STADET=Y,*
PARTITION=(SYST,DEVS),UNIT=SCTC
DEVS
/etc/zipl.conf: dasd=.., chandev=noauto
/etc/chandev.conf ctc0,0xd10,0xd11
SYST
/etc/zipl.conf dasd=.., chandev=noauto
/etc/chandev.conf ctc0,0xc20,0xc21
After reboot, I get on each system
CTC driver successfully initialised with read and write devices
"waiting for connection on ctc0"
.
.
.
.
failed
.
.
Any idea ?
Thanks in advance.
Gerard MONTELEONE
Ingenieur Systeme & Reseau
* 04.95.23.68.09 / 06.87.72.70.32
S.I.T.E.C zi du Vazzio
20090 AJACCIO Cedex
