Hello Mark, thanks for your help,
I changed ctc0 to escon0 in my chandev.conf without success.
I changed my iodf has recommended.
I tried protocol_no value 0, 1, 3 without success.
When I try protocol_no=2 i get "No such a device" even after create
/dev/ttyZ0.
This is what I get with cat /proc/chandev
chan_type key bitfield
ctc=0x1,escon=0x2,lcs=0x4,osad=0x8,qeth=0x10,claw=0x20
*'s for cu/dev type/models indicate don't cares
cautious_auto_detect: on
persist = 0x00
use_devno_names: off
Channels enabled for detection
chan cu cu dev dev max checksum use hw auto
recovery
type type model type model port_no. received stats
type
========================================================================
======
0x20 0x3088 0x61 * * 0 no no
not_operational,no_path,revalidate,device_gone
0x08 0x3088 0x62 * * 0 no no
not_operational,no_path,revalidate,device_gone
0x10 0x1731 0x05 0x1732 0x05 0 no no
not_operational,no_path,revalidate,device_gone
0x10 0x1731 0x01 0x1732 0x01 0 no no
not_operational,no_path,revalidate,device_gone
0x04 0x3088 0x60 * * 1 no no
not_operational,no_path,revalidate,device_gone
0x06 0x3088 0x1f * * 15 no no
not_operational,no_path,revalidate,device_gone
0x05 0x3088 0x08 * * 15 no no
not_operational,no_path,revalidate,device_gone
0x04 0x3088 0x01 * * 15 no no
not_operational,no_path,revalidate,device_gone
Forced devices
chan defif read write data memory port ip hw
host adapter api
type num devno devno devno usage(k) protocol no. chksum stats
name name name
========================================================================
=======================
0x02 0 0x0d10 0x0d11 0x0000 default 3 0 0
0x04 0 0x0602 0x0603 0x0000 default 1 0 0
Registered probe functions
probefunc shutdownfunc msck_notfunc chan devices devices
type found active
===============================================================
0x08810258 0x0880fe50 0x08810064 0x03 1 1
0x08805080 0x08805418 0x08805490 0x04 1 1
Initialised Devices
read write data read write data chan port dev dev
memory read msck write msck data msck
irq irq irq devno devno devno type no. ptr name
usage(k) status status status
========================================================================
=============================================
0x015a 0x015b n/a 0x0602 0x0603 n/a 0x04 1 0x07fbb600 eth0
320 good good not applicable
0x0162 0x0163 n/a 0x0d10 0x0d11 n/a 0x02 0 0x07fbb400 ctc0
n/a good good not applicable
Total device memory usage 320k.
channels detected
chan cu cu dev dev in
chandev
irq devno type type model type model pim chpids use
reg.
========================================================================
=======
0x015a 0x0602 0x04 0x3088 0x60 0x0000 0x00 0x80 0x88ffffffffffffff
yes yes
0x015b 0x0603 0x04 0x3088 0x60 0x0000 0x00 0x80 0x88ffffffffffffff
yes yes
0x015c 0x0c10 0x06 0x3088 0x1f 0x0000 0x00 0x80 0x98ffffffffffffff no
no
0x015d 0x0c11 0x06 0x3088 0x1f 0x0000 0x00 0x80 0x98ffffffffffffff no
no
0x0160 0x0c30 0x06 0x3088 0x1f 0x0000 0x00 0x80 0x98ffffffffffffff no
no
0x0161 0x0c31 0x06 0x3088 0x1f 0x0000 0x00 0x80 0x98ffffffffffffff no
no
0x0162 0x0d10 0x06 0x3088 0x1f 0x0000 0x00 0x80 0x99ffffffffffffff
yes yes
0x0163 0x0d11 0x06 0x3088 0x1f 0x0000 0x00 0x80 0x99ffffffffffffff
yes yes
All seems to be correct, it's like a "route" error ????????????????????
-----Message d'origine-----
De�: Linux on 390 Port [mailto:[EMAIL PROTECTED]] De la part de
Post, Mark K
Envoy�: mercredi 15 mai 2002 19:49
��: [EMAIL PROTECTED]
Objet�: Re: ESCON CTC between two LPAR LINUX (SLES 2.4.7)
Gerard,
There are a couple of things you could take a look at. The "Device
Drivers
and Installation Commands" shows four possible values for the CTC
protocol
to be used:
protocol_no is the protocol number for CTC or ESCON. This can take the
values:
- 0 for compatibility mode (the default; used with non-Linux peers other
than OS/390 and z/OS)
- 1 for extended mode,
- 2 meaning "CTC-based tty" (this is only supported on Linux-Linux
connections),
- 3 for compatibility mode with OS/390 and z/OS.
If I were experimenting, I would probably try protocol 1 first, followed
by
2, then 3.
You may also want to consider specifying escon0 and not ctc0, since you
have
them defined as ESCON devices and not CTC devices. The device _name_
that
gets created is still ctc0 (oddly enough), but using escon0 in my
/etc/chandev.conf causes it to show up as channel type 0x02 instead of
0x01.
Do a "cat /proc/chandev" to see what your system thinks it is. Most
likely
it is going to be 0x01. Also, when I specify the protocol type, I had
to
specify the buffer size as well.
escon0,0x700,0x701,0,1
worked, but
escon0,0x700,0x701,,1
did not.
Just as a plea for "non confusing" system definitions, I would change
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
to
IODEVICE ADDRESS=(D10,002),UNITADD=00,CUNUMBR=(0D10),STADET=Y,*
PARTITION=(DEVS,PROD),UNIT=SCTC
and reverse the read-write channels on the Linux/390 end:
/etc/chandev.conf escon0,0xc21,0xc20
Mark Post
-----Original Message-----
From: Monteleone [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, May 15, 2002 3:49 AM
To: [EMAIL PROTECTED]
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
