On 24.07.20 00:40, Davis, Larry (National VM Capability) wrote:
> I found this statement in the Linux-390 archives from Rick Troth and was 
> wondering if any one has used this interface or if there are more details on 
> using it
> 
> *Linux sees an ASCII "system console"*
> 
> This is where I had to do a little digging. They don't let me on the HMC
> so I have never gotten access to the SYSASCII interface. Sounds like a
> great idea. IBM realizes that some mainframe operating systems are
> better served with a byte-at-a-time interface. (Call it "ASCII", but the
> significant feature is not the character set. Character sets are so 1980.)

Yes, thats why KVM uses this type as the default console for its guests. Here
we have one virtual "ascii" console per guest that we then expose in a tty or 
pty.

> 
> z/VM can attach a SYSASCII to a Linux guest. Linux can then use the
> SYSASCII console interface and a non-mainframe Linux person would be
> perfectly comfortable.

Here it is different. You can attach the one "real" one to one guest. And 
the guest must see this console during boot if I remember correctly. 
Not sure if this will work with hotplug as the system console are initialized
very early. This will be especially hard as both consoles have the ttyS1 
_console_ name (the tty name of the ascii console is sclptty0). Maybe we 
should think about changing the console name as well to sclptty0.....but
then this would break  existing setups that do use the console=ttyS1 parameter
in lpar and kvm.

 
> 
> We need a way to give our Linux admins real terminal access to an ASCII 
> terminal for Boot Messages and to fix issues that prevent Network access.
> 
> The Linux Admins do use an HMC access method for the AIX systems they support 
> and want to use the same thing for z/VM Linux servers
> 
> 
>   1.  Is this possible if the HMC has access to the z/VM LPAR
>   2.  Are there specific Steps to activate the SYSASCII console when attached 
> to Linux
>      *   Even if I attach SYSASCII to a Linux server it is not actually active
> 
> q sysascii
> 
> SYSASCII attached to GLTRHEL8 inactive
> 
>      *   How to I get SYSACSII activated
> 
> 
> 
> Larry Davis
> Senior z/VM systems Architect, Enterprise Services
> T +1.813.394.4240
> DXC Technology dxc.technology<http://www.dxc.technology/>
> 
> 
> DXC Technology Company - Headquarters: 1775 Tysons Boulevard, Tysons, 
> Virginia 22102, USA.
> DXC Technology Company -- This message is transmitted to you by or on behalf 
> of DXC Technology Company or one of its affiliates. It is intended 
> exclusively for the addressee. The substance of this message, along with any 
> attachments, may contain proprietary, confidential or privileged information 
> or information that is otherwise legally exempt from disclosure. Any 
> unauthorized review, use, disclosure or distribution is prohibited. If you 
> are not the intended recipient of this message, you are not authorized to 
> read, print, retain, copy or disseminate any part of this message. If you 
> have received this message in error, please destroy and delete all copies and 
> notify the sender by return e-mail. Regardless of content, this e-mail shall 
> not operate to bind DXC Technology Company or any of its affiliates to any 
> order or other contract unless pursuant to explicit written agreement or 
> government initiative expressly permitting the use of e-mail for such 
> purpose. --.
> 
> ----------------------------------------------------------------------
> For LINUX-390 subscribe / signoff / archive access instructions,
> send email to lists...@vm.marist.edu 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 lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
http://www2.marist.edu/htbin/wlvindex?LINUX-390

Reply via email to