Steve,

Don't keep looking, your problem is that you _must_ specify a portname.
That has been true for every person that has reported running into that
particular error message.  It's never been clear if Linux/390 can _set_ that
portname (maybe you and your IBM rep can figure that out), but it is _very_
clear that it must match the portname.  If Linux/390 can't set it, use one
of your other operating systems to do so, and then update your Linux/390
parameters to match.  Make sure you specify the portname in all upper case.

Mark Post

-----Original Message-----
From: Steve Gear Schneider Technical Services
[mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 13, 2002 11:27 AM
To: [EMAIL PROTECTED]
Subject: Re: trying to us OSA/E Gig with


hello gerald,

 thanks for your reply.

 yes, the OSA will be shared, but the linux lpar is the only one using it
at this time. on this CEC we do not have a portname defined in vtam at this
time.

still looking

regards,
  steve



                    "Benton,
                    Gerald"               To:     [EMAIL PROTECTED]
                    <Gerald_Benton@       cc:
                    CSX.com>              Fax to:
                    Sent by: Linux        Subject:     Re: FTP and Telnet
not working in
                    on 390 Port            linux 390 lpars
                    <[EMAIL PROTECTED]
                    ARIST.EDU>


                    03/13/2002
                    10:13 AM
                    Please respond
                    to Linux on 390
                    Port






Steve,

Is this OSA/SF shared with other MVS LPARS? If it is you have
to use the same portname you used in your TRLE definitions.

Good luck....

-----Original Message-----
From: Steve Gear Schneider Technical Services
[mailto:[EMAIL PROTECTED]]
Sent: Wednesday, March 13, 2002 11:01 AM
To: [EMAIL PROTECTED]
Subject: Re: FTP and Telnet not working in linux 390 lpars


hello,

   we are trying to install linux s/390 with OSAE gig card and SUSE  server
7. the chpid is online and enabled. when we IPL the initial system we get
the msg,

   qeth  received an IDX terminate on irq 0x485/0x486 with cause code 0x22
- - try another portname
   there were problems in hard setting up the card.

anyone see this before.

thanks,
  steve gear

Reply via email to