Re: Problem with iucvconn under SLES 11 SP2

[Will, Chris]

Reverting to login-3.41-0.2.13.s390x.rpm resolved the issue.

-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Mark Post
Sent: Wednesday, July 10, 2013 11:20 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Problem with iucvconn under SLES 11 SP2

>>> On 7/10/2013 at 10:35 AM, "Will, Chris"  wrote: 
> This was an earlier thread.  Not sure is it was ever resolved but we 
> have run into the same issue with the later versions of login ad util-linux.

This is being worked on via Bugzilla # 824458 - iucvconn disconnects after 
entering a username.  There was a change to the behavior of the login command 
due to a prior bug (# 778842) which affected the hvc_iucv driver.  A patch has 
been submitted by IBM to the Linux Kernel Mailing List for comments so 
hopefully a fix will become available before too long.

In the meantime, during my testing of the problem, I determined that when the 
initial disconnect happens (when the userid is entered), the login process is 
still running, waiting for the response to the password prompt (which the user 
doesn't see because of the disconnect).  When you reconnect, if you type in the 
password (which will not be displayed) and hit enter, you'll be logged in.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit http://wiki.linuxvm.org/


The information contained in this communication is highly confidential and is 
intended solely for the use of the individual(s) to whom this communication is 
directed. If you are not the intended recipient, you are hereby notified that 
any viewing, copying, disclosure or distribution of this information is 
prohibited. Please notify the sender, by electronic mail or telephone, of any 
unintended receipt and delete the original message without making any copies.
 
 Blue Cross Blue Shield of Michigan and Blue Care Network of Michigan are 
nonprofit corporations and independent licensees of the Blue Cross and Blue 
Shield Association.

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Where does Linux store path information for dasd devices?

[Rick Troth]

> Seems like it should be the default
> I mean, except in very very specific cases,
> should the virtual machine EVER care about the hardware details?

Yeah ... David makes an excellent point.
Seems like a virtualization violation, in the pure sense.
Have always found it odd that guests can "see" certain aspects about
the real I/O subsystem.

I would have liked to see this CHPIDVIRTUALIZATION option years ago.

-- R; <><



On Wed, Jul 10, 2013 at 9:58 AM, David Boyes  wrote:
>> -Original Message-
>> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
>> Bruce Hayden
>> This is also why OPTION CHPIDVIRTUALIZATION ONE (and also the
>> GLOBALOPTS
>> statement) was invented, so that relocating guests don't see the real paths
>> or care if the paths on the LPAR they move to change.  [snip] and also
>> "This option should be specified only when the guest is going to be
>> relocated. In addition to virtualizing the CHPID numbers, CHPIDV ONE results
>> in DASD path group ID virtualization."
>> I'm not sure why it is suggested that this option is only used for relocating
>> guests.  It seems that it would have been useful to you if your Linux guests
>> had this option in effect before you started changing the paths!
>
> Seems like it should be the default I mean, except in very very specific 
> cases, should the virtual machine EVER care about the hardware details?
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
> http://www.marist.edu/htbin/wlvindex?LINUX-390
> --
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/



--
-- R;   <><

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Problem with iucvconn under SLES 11 SP2

[Mark Post]

>>> On 7/10/2013 at 10:35 AM, "Will, Chris"  wrote: 
> This was an earlier thread.  Not sure is it was ever resolved but we have run 
> into the same issue with the later versions of login ad util-linux.

This is being worked on via Bugzilla # 824458 - iucvconn disconnects after 
entering a username.  There was a change to the behavior of the login command 
due to a prior bug (# 778842) which affected the hvc_iucv driver.  A patch has 
been submitted by IBM to the Linux Kernel Mailing List for comments so 
hopefully a fix will become available before too long.

In the meantime, during my testing of the problem, I determined that when the 
initial disconnect happens (when the userid is entered), the login process is 
still running, waiting for the response to the password prompt (which the user 
doesn't see because of the disconnect).  When you reconnect, if you type in the 
password (which will not be displayed) and hit enter, you'll be logged in.


Mark Post

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Problem with iucvconn under SLES 11 SP2

[Will, Chris]

This was an earlier thread.  Not sure is it was ever resolved but we have run 
into the same issue with the later versions of login ad util-linux.

slxosdev2:~ # rpm -qa | grep kernel
kernel-firmware-20110923-0.19.21.10
kernel-source-3.0.80-0.7.1
kernel-default-3.0.80-0.7.1
kernel-default-man-3.0.80-0.7.1
kernel-default-base-3.0.80-0.7.1
kernel-default-devel-3.0.80-0.7.1
linux-kernel-headers-2.6.32-1.4.13
nfs-kernel-server-1.2.3-18.29.1
slxosdev2:~ # rpm -qa | grep login
login-3.41-0.4.2
slxosdev2:~ # rpm -qa | grep util-linux
util-linux-2.19.1-6.33.47.1
util-linux-lang-2.19.1-6.33.47.1

We had it working under sles 11 sp2 but earlier versions of the above software. 
 Here is part of the previous post.


Starting the iucvconn connection is working. After pressing Enter to get

the login prompt, the guest is prompting for the userid. When I press now

Enter, instead of prompting for the password, iucvconn disconnects from the

guest and I am again in the command line.



When I call iucvconn again, then there comes the message Login incorrect

and the guest is prompting for userid. In this case now, the password is

asked and the session works as designed.



So the problem is that the first login fails due to a disconnect of the

connection. It was working previous with SLES 11 SP1. So it seems that

either is iucvconn has a sort of bug or the associated driver.



Here is a sample hardcopy what is not working:



Starting at user admin1 and want to connect to tstsys1:



# iucvconn tstsys1 lnxhvc0  <--- pressing ENTER starts the connection,

  <--- need to press ENTER

again to get the login prompt



Welcome to SUSE Linux Enterprise Server 11 SP2  (s390x) - Kernel

3.0.58-0.6.6-default (hvc0).





tstsys1 login: root   <--- Entering root and press ENTER



ybi@admin1 [~/perl] # <-- Instead of asking for the password the

connection is disconnected and I am again at the command prompt of admin1.





# iucvconn tstsys1 lnxhvc0  <--- Repeat the connection request and

pressing ENTER re-starts the connection,

  <--- need to press ENTER

again to get the login prompt

Login incorrect



tstsys1 login: root   <--- Entering root and press ENTER

Password:  <-- Now prompted for the password



Last login: Mon Mar  4 10:29:48 CET 2013 on hvc0

Directory: /root

Mon Mar  4 10:45:29 CET 2013



root@stp1tsta [~]





--

Best regards



Florian Bilek



--

For LINUX-390 subscribe / signoff / archive access instructions,

send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit

http://www.marist.edu/htbin/wlvindex?LINUX-390

--

For more information on Linux on System z, visit

http://wiki.linuxvm.org/

  *   Previous 
message
  *   View by 
thread
  *   View by 
date
  *   Next 
message

  *   Problem with iucvconn under SLES 11 SP2 Florian Bilek
·

 *   Re: Problem with iucvconn under SLES 11 
SP2 Hendrik 
Brueckner
o

*   Re: Problem with iucvconn under SLES 11 
SP2 Florian 
Bilek
§

   *   Re: Problem with iucvconn under SLES 11 
SP2 Hendrik 
Brueckner
§

  *   Re: Problem with iucvconn under SLES 
11... 
Florian Bilek
§

 *   Re: Problem with iucvconn under 
SL... 
Florian Bilek
§

*   Re: Problem with iucvconn 
unde... 
Florian Bilek
§

   *   Re: Problem with iucvconn 
... Hendrik 
Brueckner
   *   Re: Problem with iucvconn 
... Florian 
Bilek
   *   Re: Problem with iucvconn 
... Hendrik 
Brueckner
   *   Re: Problem with iucvconn 
... Hendrik 
Brueckner

Reply via email to
[The Mail Archive]

  *   The Mail Archive home
  *   linux-390 - all 
messages

Re: Where does Linux store path information for dasd devices?

[David Boyes]

> -Original Message-
> From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of
> Bruce Hayden
> This is also why OPTION CHPIDVIRTUALIZATION ONE (and also the
> GLOBALOPTS
> statement) was invented, so that relocating guests don't see the real paths
> or care if the paths on the LPAR they move to change.  [snip] and also
> "This option should be specified only when the guest is going to be
> relocated. In addition to virtualizing the CHPID numbers, CHPIDV ONE results
> in DASD path group ID virtualization."
> I'm not sure why it is suggested that this option is only used for relocating
> guests.  It seems that it would have been useful to you if your Linux guests
> had this option in effect before you started changing the paths!

Seems like it should be the default I mean, except in very very specific 
cases, should the virtual machine EVER care about the hardware details?

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: IBM to acquire CSL International

[Jean-Francois Jiguet]

Isabelle,

Si tu n'as pas eu l'info ... Tu m'avais posé la question sur ce produit il 
y a quelques mois. Maintenant il fait parti du portefeuille IBM


Jean Francois JIGUET
Linux for zSeries and VM support
GTS/TSS
IBM Certified 
email: jjig...@fr.ibm.com



From:   Marcy Cortes 
To: LINUX-390@vm.marist.edu, 
Date:   07/09/2013 06:01 PM
Subject:IBM to acquire CSL International
Sent by:Linux on 390 Port 



Cross posted to IBMVM and Linux-390

IBM Press Release today:  
http://www-03.ibm.com/press/us/en/pressrelease/41442.wss

Marcy

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or 
visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/




Sauf indication contraire ci-dessus:/ Unless stated otherwise above:
Compagnie IBM France
Siège Social : 17 avenue de l'Europe, 92275 Bois-Colombes Cedex
RCS Nanterre 552 118 465
Forme Sociale : S.A.S.
Capital Social : 639.291.962.10 ?
SIREN/SIRET : 552 118 465 03644 - Code NAF 6202A 

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Sad new from Raleigh

[Henry Schaffer]

And the circumstances were tragic - hit and run driver who had lost his
drivers license.

http://www.thedurhamnews.com/2013/07/10/3020241/durham-mourns-cyclist-killed-in.html

--henry schaffer


On Wed, Jul 10, 2013 at 12:22 AM, Chip Davis  wrote:

> Red Hat employee Seth Vidal, 36, was biking near his home in Durham
> around 9 p.m. Monday when he was hit from behind by a hit-and-run
> driver.  He was pronounced dead at Duke University Hospital.
>
> Vidal worked for Red Hat as the lead developer of "Yum", an automated
> system updater used around the world.
>
> -Chip-
>
> --**--**--
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> http://www.marist.edu/htbin/**wlvindex?LINUX-390
> --**--**--
> For more information on Linux on System z, visit
> http://wiki.linuxvm.org/
>

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/

Re: Where does Linux store path information for dasd devices?

[Klaus Bergmann]

It is strange. Rick types "lscss" and expects zLinux to give him the right
information. He gets

Device   Subchan.  DevType CU Type Use  PIM PAM POM  CHPIDs
--
0.0.01B0 0.0.000A  3390/0C 3990/E9 yes  FF  FF  FF   444BA0B1 A1B06F4D

which is wrong. zLinux says "Yes, it is wrong, but nobody informed me and I
didn't care to inform myself."

Now Rich goes ahead and types "chchp -v 0 b1" which triggers zLinux to
inform itself and then, after "lscss", returns the right answer:

Device   Subchan.  DevType CU Type Use  PIM PAM POM  CHPIDs
--
0.0.01B0 0.0.000A  3390/0C 3990/E9 yes  FF  E4  FF   444BA0B1 A1B06F4D

It is a rare case of humans having to instruct the computer how to deliver
the right answer and not the computer doing it by itself in the first
place.

I have been in the first row of that movie a long time ago and have given
up. Couldn't convince anybody to correct this. All the best, Rick, hope
your Service Request has more luck.

Klaus

--
For LINUX-390 subscribe / signoff / archive access instructions,
send email to lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/