I agree, for regular access users should use ssh to login to a guest. So
you don't need all that many devices. The HVC is controlled by the
kernel parameters at boot. But the iucv connections also can use a
service that's started during init (or systemd). In there you can define
any amount you might want. The latter does require a correct boot as
it's just a service that gets started. But you can (manually) start
another iucv service when needed.
Regards, Berry.
Op 03-12-2025 om 04:37 schreef Cohen, Sam:
Philip,
I second Rick's mention of IUCV and a central terminal server for
consideration. I've set it up and it is very easy, especially if you have
SLES. It's easy to get working with my Ubuntu, RH and SLES guests. However
(you knew there would be one), I use this as a backdoor for admins, not for
general users (since I'm not sure how many IUCV connections and associated
terminals (/dev/hvc) I really want to manage for each Linux guest. How many
simultaneous connections do you realistically need for this group of people
(irrespective of the number people that could login)?
Thanks,
Sam
-----Original Message-----
From: Linux on 390 Port <[email protected]> On Behalf Of Rick Troth
Sent: Tuesday, December 2, 2025 21:20
To: [email protected]
Subject: Re: Console access for s390x linux
There are some "terminal server" options. I have never used such, but I HAVE
used, and been very pleased with 'iucvconn', which is standard with mainframe Linux.
You can set-up a central Linux guest to act as a "jump server" such that your
SAs connect to that (e.g., using SSH from their laptops) and then use 'iucvconn' to work
on the various other guests. The other guests can run a daemon to handle incoming
traffic. BUT you can also get the kernel to talk the same protocol, no daemon needed.
Now ... this does not help the SAs manage pre-IPL guests. The guest can be in a really
bad state, but at least needs the kernel. (Stuff like "single user" mode.)
IBM cooked up a clean and simple protocol, layered on IUCV (which is secure and
robust).
You can even cobble-up a listener to run on CMS. Not saying I've ever done such
a thing. If I had, would I admit it? *:-)*
-- R; <><
On 12/2/25 10:08 PM, Philip Tully wrote:
Cross-posted to VM and linux lists
My team is looking for a solution to provide non-3270 console access to linux
guests running under zVM.
We need to provide console access to groups of SA's, taking over support.
We will of course need to ensure it meets our compliance requirements, so any
suggestions would be appreciated.
Regards
Phil Tully
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions, send
email [email protected] with the message: INFO LINUX-390 or
visit
http://www2/.
marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-390&data=05%7C02%7CSam.Cohen%40L
RS.COM%7C7d674b08750d4be6d24008de321aff71%7C62af9ccc42164ae2a1d306614c
59c315%7C0%7C0%7C639003288760118299%7CUnknown%7CTWFpbGZsb3d8eyJFbXB0eU
1hcGkiOnRydWUsIlYiOiIwLjAuMDAwMCIsIlAiOiJXaW4zMiIsIkFOIjoiTWFpbCIsIldU
IjoyfQ%3D%3D%7C0%7C%7C%7C&sdata=wV4DySQu5icDoaLYeuGlVg8HEgTmOoW0coRmBQ
lixhQ%3D&reserved=0
--
-- R; <><
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions, send email to
[email protected] with the message: INFO LINUX-390 or visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390
----------------------------------------------------------------------
For LINUX-390 subscribe / signoff / archive access instructions,
send email to [email protected] with the message: INFO LINUX-390 or visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390
