Paul, Are these ESCON channels, or CTCs? It makes a difference. Call them by the right name. You can turn off auto detection for CTC/ESCON devices by using a kernel parameter in your parmfile: ctc=noauto
To specify your CTCs, use the chandev kernel parameter: chandev=ctc0,0xreadchan,0xwritechan,0,3 The trailing "3" specifies the protocol to use. According to the "Device Drivers and Installation Commands (March 4,2002)" manual (http://www10.software.ibm.com/developerworks/opensource/linux390/docu/lzsdd 08.pdf): 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. Since you're talking to a z/OS system, that would mean you should use "3." Hope this helps. Mark Post -----Original Message----- From: Paul Trammell [mailto:[EMAIL PROTECTED]] Sent: Wednesday, April 10, 2002 10:22 PM To: [EMAIL PROTECTED] Subject: CTCs and CHANDEV parameter Like Larry, my definitions worked with the Marist 2.2 version. I have ESCON CTCs in LPAR mode connecting to a z/OS 1.2 system on the other end. Installing RH72, I am muddling through the postings on this issue trying to figure out why I can't use those same devices as before with the new system. I have tried specifying chandev=ctc0,addr1,addr2 to no avail, but noticed a 'noauto' in the CHANDEV=noauto;lcs0,0x6a0a,0x6a0b example from the earlier post (it seems CHANDEV=escon0,addr1,addr2 is not valid?). Is there something similar to 'noauto' for ctc0? Has anyone actually defined escon0 successfully, so that you can ifconfig escon0? I am IPLing from tape, have the parms all on one line. Thanks for any/all help! Paul
