Re: SYSASCII Console for Linux images

[Peter Oberparleiter]

On 03.03.2021 16:36, Alan Altmark wrote:
> On Wednesday, 03/03/2021 at 02:25 GMT, Peter Oberparleiter
>  wrote:
>> 3. Use the ASCII Console as Linux console
>>
>> - add "console=ttyS1" to kernel parameters in /etc/zipl.conf
>> (mind the upper-case S)
>> - run zipl + reboot
>>
>> During boot you should see all Linux console output on the ASCII
>> Console.
>
> Is there a way to tell Linux, "Use the ascii console unless there isn't
> one, in which case use the 3215 console instead."?

You can tell Linux to print console output to both ASCII and 3215
consoles by repeating the console= statement for ttyS0 (3215) and ttyS1
(ASCII). You can also configure Linux to provide a login prompt that
works independently on both consoles.

The one thing that's not possible with the current implementation is to
control the Linux init process from both consoles. This is typically
necessary if there's an error during early boot - like a root file
system corruption - that requires manual intervention to resolve.

The input device that is connected to the init process is determined
once during kernel initialization depending on the order of console=
statements (the last one will be used for input) and it cannot be
changed without a reboot.


Regards,
  Peter Oberparleiter

--
Peter Oberparleiter
Linux on Z Development - IBM Germany

--
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

Re: SYSASCII Console for Linux images

[Dave Jones]

This is a good idea, imho. Right now, as I understand things, the main
driver of the z architecture growth is Linux based workloads, so the
more we ("we" == IBM) can make the z platform behave like the other
platforms, the easier it will be for IBM to sell z boxes into
distributed-oriented sites. Robert's pints "a" and "b" address this
explicitly, and it's just another step in the evolution of the
mainframe.

Maybe we could try to hold a BoF about this topic at the upcoming VM
Workshop? Robert, are you planning on attending?
Take care.
DJ

---
DAVID JONES | MANAGING DIRECTOR FOR ZSYSTEMS SERVICES | z/VM, Linux, and
Cloud
703.237.7370 (Office) | 281.578.7544 (CELL)

INFORMATION TECHNOLOGY COMPANY

On 03.02.2021 3:25 PM, Robert J Brenneman wrote:

I thought it would be cool if the hardware platform could emulate a set
of
Keyboard/Video/Mouse devices via pretend PCI devices presented into the
LPAR that hook into like a VNC / RemoteDesktop / SPICE software service
that runs on the SE or HMC.

If you virtualize it like pretend PCI devices ( similar to what KVM
does
internally for guests ) then Linux doesn't need any new drivers if you
emulate things that the kernel already knows how to talk to: Cirrus
Logic
VGA card, USB Keyboard & Mouse , possibly USB  CDROM too and you can
pass
through an ISO mount from your remote desktop client.

This would do a bunch of things:
a)  Installation now works like on every other Linux platform : remote
into
the LPAR / Guest using the same tools as every other platform ( VNC ,
SPICE, RemoteDesktop )  and you don't have to muck about with creating
a
custom parmfile at all - if we can remote media mount a .iso through
the
client to present as a USB attached DVD then it appears as local
install
media and you don't need a working IP stack for the installer anymore.
b)  Fixing broken systems now works like every other Linux platform :
remote into the VNC / SPICE / RemoteDesktop link and fix the network
using
whatever suits your fancy. Full on X11 GUI if you really want to - go
for
it.
c) Hypervisor agnostic : since its basically fake PCI devices you
generate
as many as needed per LPAR and either use them directly from the LPAR
or
attach them to a specific guest. You would have to have some kind of
mapping of "PCI device group 1 is VNC desktop :1 " , and you would have
to
manage that from the HMC similar to what we do with OSA ICC profiles -
but
thats a solvable problem.

Nobody else I talked to thought it was cool though... :(


But if youuu guys asked for it as an official Requirement ... maybe
you
guys could make it cool ? ?


...

Just thinkin.

I'm gonna go have dinner now.




On Tue, Mar 2, 2021 at 3:57 PM Dave Jones  wrote:


Thinking about this a little more, I think what would be nice to have
is
something along the lines of the OSA-ICC, which presents locally
attached 3270 device to the O/S, but is reachable via TCP/IP.

We could call it the OSA-ASC and it would present a locally attached
VT220 to either Linux running native in an LPAR or to Linux running as
a
guest of z/VM, also reachable via TCP/IP.

No need to have access to the HMC and it's Integrated ASCII console.

DJ

---
DAVID JONES | MANAGING DIRECTOR FOR ZSYSTEMS SERVICES | z/VM, Linux,
and
Cloud
703.237.7370 (Office) | 281.578.7544 (CELL)

INFORMATION TECHNOLOGY COMPANY

On 03.01.2021 2:00 PM, Mark Post wrote:
> On 3/1/21 3:49 PM, Dave Jones wrote:
>> Have you considered using the IBM Terminal Server for
>> zLinux?
>> The Terminal Server is part of the s390-tools package and
>> permits normal access to other zLinux guests running
>> on the same z/VM system, even if they are not
>> connected to a working TCP/IP network. This permits
>> the use of common Linux tools like vi, Emacs, and
>> nano, to be used even in the event of a network
>> failure.
>
> The caveat being that this only works after the kernel boots up to the
> point where the hvc? console(s) are available. For any problems that
> are
> really early in the boot process, this won't suffice. Once you get past
> that point, things do indeed look a lot more like "normal" to the
> typical Linux system administrator.
>
>
> 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://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




--
Jay Brenneman

--
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

Re: SYSASCII Console for Linux images

[Alan Altmark]

On Wednesday, 03/03/2021 at 02:25 GMT, Peter Oberparleiter 
 wrote:
> 3. Use the ASCII Console as Linux console
>
> - add "console=ttyS1" to kernel parameters in /etc/zipl.conf
> (mind the upper-case S)
> - run zipl + reboot
>
> During boot you should see all Linux console output on the ASCII
> Console.

Is there a way to tell Linux, "Use the ascii console unless there isn't 
one, in which case use the 3215 console instead."?

If things have gone south, I'd kinda like to be able to simply attach the 
ascii console and have Linux start using it right away without the need to 
issue commands (since I can't so anyway because I've lost connectivity). 
And for extra credit: when I'm done, simply detaching the console and 
having Linux go back to the 3215.

Alan Altmark

Senior Managing z/VM and Linux Consultant
IBM Systems Lab Services
IBM Z Delivery Practice
ibm.com/systems/services/labservices
office: 607.429.3323
mobile; 607.321.7556
alan_altm...@us.ibm.com
IBM Endicott


--
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

Re: SYSASCII Console for Linux images

[Peter Oberparleiter]

On 01.03.2021 21:26, Davis, Larry (National VM Capability) wrote:
> What are people doing when the local Linux people are wanting ASCII Consoles 
> available for  performing reboots or problem resolution
>
> I know I can attach the SYSASCII (HMC ASCII vt220 console) to a Linux image
>
> Does the Linux image need to include "ttys1" in the /etc/zipl.conf file for 
> RHEL 7.5 and above?
> console=ttyS1 console=ttyS0

You can specify "console=ttyS1" as additional kernel parameter if you
want to have console output written to the ASCII Console, and also to
use that console as input device for early boot problems (e.g. dracut
rescue shell).

> We tested attaching it to a Running Linux but the device never really worked 
> when attached, we probably missed something
>
> Any Suggestions on using this properly?

I just tried this on an RHEL 7.5 z/VM guest and everything seemed to
work without problems.

Some things to try out (requires root privileges):

1. Attach ASCII console to guest from within Linux guest

$ vmcp att sysascii to '*'


2. To check the connection to the ASCII console: open the "Integrated
HMC ASCII Console" task for the z/VM LPAR. Then issue in Linux:

$ echo test > /dev/ttysclp0

The result should be "test" being displayed on the ASCII Console.


3. Use the ASCII Console as Linux console

- add "console=ttyS1" to kernel parameters in /etc/zipl.conf
  (mind the upper-case S)
- run zipl + reboot

During boot you should see all Linux console output on the ASCII
Console. You can also check this connection using the following command:

$ echo test > /dev/console

The "test" message should again be displayed on the ASCII Console.


4. Enable login from the ASCII Console

$ systemctl start serial-getty@ttysclp0.service

When this command completes, there should be a login prompt shown on the
ASCII Console.

You can also check the status of this systemctl unit using:

$ systemctl status serial-getty@ttysclp0.service


Regards,
  Peter Oberparleiter

--
Peter Oberparleiter
Linux on Z Development - IBM Germany

--
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

Re: SYSASCII Console for Linux images

[Christian Borntraeger]

On 02.03.21 21:56, Dave Jones wrote:

Thinking about this a little more, I think what would be nice to have is
something along the lines of the OSA-ICC, which presents locally
attached 3270 device to the O/S, but is reachable via TCP/IP.

We could call it the OSA-ASC and it would present a locally attached
VT220 to either Linux running native in an LPAR or to Linux running as a
guest of z/VM, also reachable via TCP/IP.


This is basically the KVM model. We do provide virtual VT220 to the guest and
pass that along to local processes or network processes like virt-manager.

Not sure how hard that would be for z/VM as the model of operation is somewhat
tied to the 3270 console.


No need to have access to the HMC and it's Integrated ASCII console.


--
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

Re: SYSASCII Console for Linux images

[Paul Gilmartin]

On 2021-03-02, at 17:48:48, Jim Elliott wrote:
> 
> There was a product called the Yale IUP and later product version the 7171
> Device Attachment Control Unit which "converted" ASCII displays (like the
> IBM 3101) into 3270 protocol devices.
>  
> Later there was the 3174 Controller
> with the Asynchronous Emulator Adapter (AEA) which is what I think you are
> referring to, and it also emulated 3278 on ASCII.
> 
It went both ways.  According to:

http://bitsavers.trailing-edge.com/pdf/ibm/3174/ZZ25-8524-0_3174_Asynchronous_Emulation_Adapter_Feature_Nov87.pdf

 IBM Internal Use Only
Introduction
Terminology
The 3174 Asynchronous Emulation Adapter (ABA) feature and Release 3 micro- code 
provide the customer with increased connectivity by allowing the customer to:

• Use an ASCII device to communicate with an ASCII host

• Use an ASCII device to communicate with an IBM host

• Use a 3270 device to communicate with an ASCII host
^

• Use a 3270 CUT device in MLT (Multiple Logical Terminal) mode to have 
multiple sessions with ASCII and IBM hosts.

I once tried the configuration I highlighted.  Not very useful
to me since I had a real ASCII device on my desk.  But the
emulation was surprisingly faithful.

-- gil

--
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

Re: SYSASCII Console for Linux images

[Jim Elliott]

There was a product called the Yale IUP and later product version the 7171
Device Attachment Control Unit which "converted" ASCII displays (like the
IBM 3101) into 3270 protocol devices. Later there was the 3174 Controller
with the Asynchronous Emulator Adapter (AEA) which is what I think you are
referring to, and it also emulated 3278 on ASCII.

Jim Elliott
Senior IT Consultant - GlassHouse Systems Inc.


On Tue, Mar 2, 2021 at 3:22 PM Paul Gilmartin  wrote:

> On 2021-03-02, at 11:18:25, Fred Shaheen wrote:
> >
> >
> > The ASCII controller was the 7171, developed by Dr. Wehrle's team in the
> > Glendale Lab in the 1980's.
> >
> I believe that was a successor and embedded the "Yale ASCII" which
> was based on an IBM Series 1 minicomputer.  Those provided the
> hardware base for IND$FILE and Columbia Kermit, which switched
> modes with a valid but improbable sequence of 3278 control
> bytes.
>
> I believe the 3174 AEA was different.  But it may have embedded
> 7171 firmware.
>
> > My car pool buddy at the time, Tom Murphy Jr. (the other Tom Murphy for
> > those of you in VM) was the lead
> > developer on that box.
>
>
> > From: Paul Gilmartin
> > Date: 03/02/2021 12:07 PM
> >
> > On 2021-03-02, at 09:38:54, Dave Jones wrote:
> >>
> >> I wonder how hard it would be for z/VM to emulate, or virtualize, a
> >> VT220 type terminal?
> >>
> > In days of yore, there was a hardware solution.  The 3174(?)
> > Asynchronous Emulation Adapter.  I don't remember the configuration
> > I tried, but it made an (independent vendor) 3278 behave remarkably
> > like a VT-220.
>
> -- gil
>
> --
> 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

Re: SYSASCII Console for Linux images

[Paul Gilmartin]

On 2021-03-02, at 11:18:25, Fred Shaheen wrote:
>
>
> The ASCII controller was the 7171, developed by Dr. Wehrle's team in the
> Glendale Lab in the 1980's.
>
I believe that was a successor and embedded the "Yale ASCII" which
was based on an IBM Series 1 minicomputer.  Those provided the
hardware base for IND$FILE and Columbia Kermit, which switched
modes with a valid but improbable sequence of 3278 control
bytes.

I believe the 3174 AEA was different.  But it may have embedded
7171 firmware.

> My car pool buddy at the time, Tom Murphy Jr. (the other Tom Murphy for
> those of you in VM) was the lead
> developer on that box.


> From: Paul Gilmartin
> Date: 03/02/2021 12:07 PM
>
> On 2021-03-02, at 09:38:54, Dave Jones wrote:
>>
>> I wonder how hard it would be for z/VM to emulate, or virtualize, a
>> VT220 type terminal?
>>
> In days of yore, there was a hardware solution.  The 3174(?)
> Asynchronous Emulation Adapter.  I don't remember the configuration
> I tried, but it made an (independent vendor) 3278 behave remarkably
> like a VT-220.

-- gil

--
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

Re: SYSASCII Console for Linux images

[Robert J Brenneman]

I thought it would be cool if the hardware platform could emulate a set of
Keyboard/Video/Mouse devices via pretend PCI devices presented into the
LPAR that hook into like a VNC / RemoteDesktop / SPICE software service
that runs on the SE or HMC.

If you virtualize it like pretend PCI devices ( similar to what KVM does
internally for guests ) then Linux doesn't need any new drivers if you
emulate things that the kernel already knows how to talk to: Cirrus Logic
VGA card, USB Keyboard & Mouse , possibly USB  CDROM too and you can pass
through an ISO mount from your remote desktop client.

This would do a bunch of things:
a)  Installation now works like on every other Linux platform : remote into
the LPAR / Guest using the same tools as every other platform ( VNC ,
SPICE, RemoteDesktop )  and you don't have to muck about with creating a
custom parmfile at all - if we can remote media mount a .iso through the
client to present as a USB attached DVD then it appears as local install
media and you don't need a working IP stack for the installer anymore.
b)  Fixing broken systems now works like every other Linux platform :
remote into the VNC / SPICE / RemoteDesktop link and fix the network using
whatever suits your fancy. Full on X11 GUI if you really want to - go for
it.
c) Hypervisor agnostic : since its basically fake PCI devices you generate
as many as needed per LPAR and either use them directly from the LPAR or
attach them to a specific guest. You would have to have some kind of
mapping of "PCI device group 1 is VNC desktop :1 " , and you would have to
manage that from the HMC similar to what we do with OSA ICC profiles - but
thats a solvable problem.

Nobody else I talked to thought it was cool though... :(


But if youuu guys asked for it as an official Requirement ... maybe you
guys could make it cool ? ?


...

Just thinkin.

I'm gonna go have dinner now.




On Tue, Mar 2, 2021 at 3:57 PM Dave Jones  wrote:

> Thinking about this a little more, I think what would be nice to have is
> something along the lines of the OSA-ICC, which presents locally
> attached 3270 device to the O/S, but is reachable via TCP/IP.
>
> We could call it the OSA-ASC and it would present a locally attached
> VT220 to either Linux running native in an LPAR or to Linux running as a
> guest of z/VM, also reachable via TCP/IP.
>
> No need to have access to the HMC and it's Integrated ASCII console.
>
> DJ
>
> ---
> DAVID JONES | MANAGING DIRECTOR FOR ZSYSTEMS SERVICES | z/VM, Linux, and
> Cloud
> 703.237.7370 (Office) | 281.578.7544 (CELL)
>
> INFORMATION TECHNOLOGY COMPANY
>
> On 03.01.2021 2:00 PM, Mark Post wrote:
> > On 3/1/21 3:49 PM, Dave Jones wrote:
> >> Have you considered using the IBM Terminal Server for
> >> zLinux?
> >> The Terminal Server is part of the s390-tools package and
> >> permits normal access to other zLinux guests running
> >> on the same z/VM system, even if they are not
> >> connected to a working TCP/IP network. This permits
> >> the use of common Linux tools like vi, Emacs, and
> >> nano, to be used even in the event of a network
> >> failure.
> >
> > The caveat being that this only works after the kernel boots up to the
> > point where the hvc? console(s) are available. For any problems that
> > are
> > really early in the boot process, this won't suffice. Once you get past
> > that point, things do indeed look a lot more like "normal" to the
> > typical Linux system administrator.
> >
> >
> > 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://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
>


--
Jay Brenneman

--
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

Re: SYSASCII Console for Linux images

[Alan Altmark]

On Tuesday, 03/02/2021 at 08:56 GMT, Dave Jones  
wrote:
> Thinking about this a little more, I think what would be nice to have is
> something along the lines of the OSA-ICC, which presents locally
> attached 3270 device to the O/S, but is reachable via TCP/IP.
>
> We could call it the OSA-ASC and it would present a locally attached
> VT220 to either Linux running native in an LPAR or to Linux running as a
> guest of z/VM, also reachable via TCP/IP.
>
> No need to have access to the HMC and it's Integrated ASCII console.

We have (had) something in the system called "native ASCII" support.  It's 
support for ancient Telegraph Adapter Type II (TELE2) devices attached to 
the old 270X and 374X controller, and later emulated in the 9370/9221 
boxes.  Those things used I/O functions like PREPARE.  The "OSA-ASC" could 
simulate one of those.

Blech.  No.  Thanks, but no thanks.

I can envision:
- TN3270E connection to VM
- New SYSASCII command can be issued before LOGON
- CP instructs telnet server to renegotiate to line mode NVT
- Telnet server connect to *CCS as it does for line mode, but with 
"SYSASCII" indicator
- CP prompts for userid and password as usual
- Upon success, CP signals telnet server to stop doing EBCDIC-ASCII 
translation
- CP connects *CCS terminal to virtual SYSASCII console

Alan Altmark

Senior Managing z/VM and Linux Consultant
IBM Systems Lab Services
IBM Z Delivery Practice
ibm.com/systems/services/labservices
office: 607.429.3323
mobile; 607.321.7556
alan_altm...@us.ibm.com
IBM Endicott


--
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

Re: SYSASCII Console for Linux images

[Paul Gilmartin]

On 2021-03-02, at 09:38:54, Dave Jones wrote:
>
> I wonder how hard it would be for z/VM to emulate, or virtualize, a
> VT220 type terminal?
>
In days of yore, there was a hardware solution.  The 3174(?)
Asynchronous Emulation Adapter.  I don't remember the configuration
I tried, but it made an (independent vendor) 3278 behave remarkably
like a VT-220.

-- gil

--
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

Re: SYSASCII Console for Linux images

[Dave Jones]

Thinking about this a little more, I think what would be nice to have is
something along the lines of the OSA-ICC, which presents locally
attached 3270 device to the O/S, but is reachable via TCP/IP.

We could call it the OSA-ASC and it would present a locally attached
VT220 to either Linux running native in an LPAR or to Linux running as a
guest of z/VM, also reachable via TCP/IP.

No need to have access to the HMC and it's Integrated ASCII console.

DJ

---
DAVID JONES | MANAGING DIRECTOR FOR ZSYSTEMS SERVICES | z/VM, Linux, and
Cloud
703.237.7370 (Office) | 281.578.7544 (CELL)

INFORMATION TECHNOLOGY COMPANY

On 03.01.2021 2:00 PM, Mark Post wrote:

On 3/1/21 3:49 PM, Dave Jones wrote:

Have you considered using the IBM Terminal Server for
zLinux?
The Terminal Server is part of the s390-tools package and
permits normal access to other zLinux guests running
on the same z/VM system, even if they are not
connected to a working TCP/IP network. This permits
the use of common Linux tools like vi, Emacs, and
nano, to be used even in the event of a network
failure.


The caveat being that this only works after the kernel boots up to the
point where the hvc? console(s) are available. For any problems that
are
really early in the boot process, this won't suffice. Once you get past
that point, things do indeed look a lot more like "normal" to the
typical Linux system administrator.


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://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

Re: SYSASCII Console for Linux images

[Fred Shaheen]

The ASCII controller was the 7171, developed by Dr. Wehrle's team in the
Glendale Lab in the 1980's.
My car pool buddy at the time, Tom Murphy Jr. (the other Tom Murphy for
those of you in VM) was the lead
developer on that box.



Fred C. Shaheen
Manager, System z Virtualization Development
   
   
   
   Phone: 1-607-429-4372 | Tie-Line: 620-4372   
  IBM
   Mobile: 1-607-237-4628  
   E-mail: shahe...@us.ibm.com  1701 
North St
 
Endicott, NY
   
13760-5553
United 
States
   


'Intention without action is only a dream.  In the end it isn't what we
want to do or plan to do but what we actually do that makes any
difference.'
Mark Sanborn



From:   Paul Gilmartin 
To: LINUX-390@VM.MARIST.EDU
Date:   03/02/2021 12:07 PM
Subject:[EXTERNAL] Re: SYSASCII Console for Linux images
Sent by:Linux on 390 Port 



On 2021-03-02, at 09:38:54, Dave Jones wrote:
>
> I wonder how hard it would be for z/VM to emulate, or virtualize, a
> VT220 type terminal?
>
In days of yore, there was a hardware solution.  The 3174(?)
Asynchronous Emulation Adapter.  I don't remember the configuration
I tried, but it made an (independent vendor) 3278 behave remarkably
like a VT-220.

-- gil

--
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

Re: SYSASCII Console for Linux images

[Davis, Larry (National VM Capability)]

That is what, I thought the SYSASCII device was designed for?


Larry Davis (z/VM Team)

-Original Message-
From: Linux on 390 Port  On Behalf Of Paul Gilmartin
Sent: Tuesday, March 2, 2021 12:06 PM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: SYSASCII Console for Linux images




*** CAUTION ***: This Email failed a DXC authentication security check (SPF or 
DMARC) which indicates it may not have come from a legitimate sender. Please 
use caution when opening any message content such as an attachment or clicking 
a URL. More information on the SPF (Sender Policy Framework) and DMARC 
(Domain-based Authentication, Reporting and Conformance) security checks is 
available on the 
ITConnect<https://csc.service-now.com/sp?id=kb_article_view_kb_id=20f68041dbd108d07dd3cebe3b961915_sso_id=7b5e13254fb5d600a198a4eab110c723>
 site.



On 2021-03-02, at 09:38:54, Dave Jones wrote:
>
> I wonder how hard it would be for z/VM to emulate, or virtualize, a
> VT220 type terminal?
>
In days of yore, there was a hardware solution.  The 3174(?) Asynchronous 
Emulation Adapter.  I don't remember the configuration I tried, but it made an 
(independent vendor) 3278 behave remarkably like a VT-220.

-- gil

--
For LINUX-390 subscribe / signoff / archive access instructions, send email to 
lists...@vm.marist.edu with the message: INFO LINUX-390 or visit
https://clicktime.symantec.com/a/1/kkd5gyzDgMEh5b-4tJCH5drMB4KqXKhWwDWfDpuLu-E=?d=UD6SAj8uaOFFsm_CB14vkwCoZTXPNCJ5wamTvkbyZtMkAX2n4fgPeYTK8h7VOHAvQ4CJbZBhdvGJHSmOR-oA0cuBmYLxkW-7qiw8I2O5N2X5xZrUATrEakm-ixsHMuiPHVqncHPju55j92A-CMPmd-Iv92xYPiyJMbiU8NvAQyscfB9FerVgncS_LfaGZebaqW8AhtIblpJy53Orf4FSO9oEOCC8mjUVAv9n92KuugHIqt6b-LcQ0GjVCSwHWuOU9AnWKGQPAfXwk8ISkHkq8b0ulmKIj0dpubThSWviPWeYiSIQXJcXK6R64C8cuIE8fo-I6fGXH2mkreVbF0DznZsO1oR2TbtZhGpYETU3r6RmIsb6jfGvF20ukj5zweXvG6j7iqi-_EZHRFzxyW-rsI7yyk3ILCG_YmLCGfZwRpQ%3D=http%3A%2F%2Fwww2.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-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

Re: SYSASCII Console for Linux images

[Dave Jones]

I wonder how hard it would be for z/VM to emulate, or virtualize, a
VT220 type terminal?
DJ

---
DAVID JONES | MANAGING DIRECTOR FOR ZSYSTEMS SERVICES | z/VM, Linux, and
Cloud
703.237.7370 (Office) | 281.578.7544 (CELL)

INFORMATION TECHNOLOGY COMPANY

On 03.01.2021 2:00 PM, Mark Post wrote:

On 3/1/21 3:49 PM, Dave Jones wrote:

Have you considered using the IBM Terminal Server for
zLinux?
The Terminal Server is part of the s390-tools package and
permits normal access to other zLinux guests running
on the same z/VM system, even if they are not
connected to a working TCP/IP network. This permits
the use of common Linux tools like vi, Emacs, and
nano, to be used even in the event of a network
failure.


The caveat being that this only works after the kernel boots up to the
point where the hvc? console(s) are available. For any problems that
are
really early in the boot process, this won't suffice. Once you get past
that point, things do indeed look a lot more like "normal" to the
typical Linux system administrator.


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://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

Re: SYSASCII Console for Linux images

[Mark Post]

On 3/1/21 3:49 PM, Dave Jones wrote:
> Have you considered using the IBM Terminal Server for
> zLinux?
> The Terminal Server is part of the s390-tools package and
> permits normal access to other zLinux guests running
> on the same z/VM system, even if they are not
> connected to a working TCP/IP network. This permits
> the use of common Linux tools like vi, Emacs, and
> nano, to be used even in the event of a network
> failure.

The caveat being that this only works after the kernel boots up to the
point where the hvc? console(s) are available. For any problems that are
really early in the boot process, this won't suffice. Once you get past
that point, things do indeed look a lot more like "normal" to the
typical Linux system administrator.


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://www2.marist.edu/htbin/wlvindex?LINUX-390

Re: SYSASCII Console for Linux images

[Davis, Larry (National VM Capability)]

Yes and it works great as long as the user does not do a reboot or the systems 
fails to boot or load the IUCV driver


Larry Davis (z/VM Team)

-Original Message-
From: Dave Jones 
Sent: Monday, March 1, 2021 3:50 PM
To: Linux on 390 Port 
Cc: Davis, Larry (National VM Capability) 
Subject: Re: SYSASCII Console for Linux images

Have you considered using the IBM Terminal Server for zLinux?
The Terminal Server is part of the s390-tools package and permits normal access 
to other zLinux guests running on the same z/VM system, even if they are not 
connected to a working TCP/IP network. This permits the use of common Linux 
tools like vi, Emacs, and nano, to be used even in the event of a network 
failure.

DJ

---
DAVID JONES | MANAGING DIRECTOR FOR ZSYSTEMS SERVICES | z/VM, Linux, and Cloud
703.237.7370 (Office) | 281.578.7544 (CELL)

INFORMATION TECHNOLOGY COMPANY

On 03.01.2021 12:26 PM, Davis, Larry (National VM Capability) wrote:
> What are people doing when the local Linux people are wanting ASCII
> Consoles available for  performing reboots or problem resolution
>
> I know I can attach the SYSASCII (HMC ASCII vt220 console) to a Linux
> image
>
> Does the Linux image need to include "ttys1" in the /etc/zipl.conf
> file for RHEL 7.5 and above?
> console=ttyS1 console=ttyS0
>
> We tested attaching it to a Running Linux but the device never really
> worked when attached, we probably missed something
>
> Any Suggestions on using this properly?
>
>
>
>
> Larry Davis
> Senior z/VM systems Architect, Enterprise Services T +1.813.394.4240
> DXC Technology
> dxc.technology<https://clicktime.symantec.com/3379qj7Uvp8t2fKLT8fF8Xn7
> Vc?u=http%3A%2F%2Fwww.dxc.technology%2F>
>
>
>
> --
> For LINUX-390 subscribe / signoff / archive access instructions, send
> email to lists...@vm.marist.edu with the message: INFO LINUX-390 or
> visit
> https://clicktime.symantec.com/3CnzXXAf9qFkz7AMVv737Yd7Vc?u=http%3A%2F%2Fwww2.marist.edu%2Fhtbin%2Fwlvindex%3FLINUX-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

Re: SYSASCII Console for Linux images

[Dave Jones]

Have you considered using the IBM Terminal Server for
zLinux?
The Terminal Server is part of the s390-tools package and
permits normal access to other zLinux guests running
on the same z/VM system, even if they are not
connected to a working TCP/IP network. This permits
the use of common Linux tools like vi, Emacs, and
nano, to be used even in the event of a network
failure.

DJ

---
DAVID JONES | MANAGING DIRECTOR FOR ZSYSTEMS SERVICES | z/VM, Linux, and
Cloud
703.237.7370 (Office) | 281.578.7544 (CELL)

INFORMATION TECHNOLOGY COMPANY

On 03.01.2021 12:26 PM, Davis, Larry (National VM Capability) wrote:

What are people doing when the local Linux people are wanting ASCII
Consoles available for  performing reboots or problem resolution

I know I can attach the SYSASCII (HMC ASCII vt220 console) to a Linux
image

Does the Linux image need to include "ttys1" in the /etc/zipl.conf
file for RHEL 7.5 and above?
console=ttyS1 console=ttyS0

We tested attaching it to a Running Linux but the device never really
worked when attached, we probably missed something

Any Suggestions on using this properly?




Larry Davis
Senior z/VM systems Architect, Enterprise Services
T +1.813.394.4240
DXC Technology dxc.technology



--
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

SYSASCII Console for Linux images

[Davis, Larry (National VM Capability)]

What are people doing when the local Linux people are wanting ASCII Consoles 
available for  performing reboots or problem resolution

I know I can attach the SYSASCII (HMC ASCII vt220 console) to a Linux image

Does the Linux image need to include "ttys1" in the /etc/zipl.conf file for 
RHEL 7.5 and above?
console=ttyS1 console=ttyS0

We tested attaching it to a Running Linux but the device never really worked 
when attached, we probably missed something

Any Suggestions on using this properly?




Larry Davis
Senior z/VM systems Architect, Enterprise Services
T +1.813.394.4240
DXC Technology dxc.technology



--
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