gt;
>
> Original Message-
> From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On
> Behalf Of John McKown
> Sent: Monday, April 07, 2014 8:03 AM
> To: IBM-MAIN@LISTSERV.UA.EDU
> Subject: [IBM-MAIN] OT: How would you like _this_ as your "z/OS h
On Tue, 8 Apr 2014 20:27:25 +, Ken Porowski wrote:
>How large would the QR code have to be to replace a stand alone dump?
A kernel oops isn't (usually) a dump, but as John mentioned closer to an
indicative dump plus relevant syslog. Getting a dump is quiet an exercise -
reading it more so.
On Tue, Apr 8, 2014 at 3:27 PM, Ken Porowski wrote:
> How large would the QR code have to be to replace a stand alone dump?
>
Yeah. I guess the HMC would need to have a 60" screen with a 4K (UltraHD)
resolution. Of course, any QR code from z/OS would likely only encode
"relevant" data. Kind of l
sent from or received at this email address.
Original Message-
From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf
Of John McKown
Sent: Monday, April 07, 2014 8:03 AM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: [IBM-MAIN] OT: How would you like _this_ as your "
On Mon, 7 Apr 2014 07:03:25 -0500, John McKown wrote:
>The Linux developers are considering using QR codes to encode Kernel OOPS
>(hard wait) information. Snap a picture of it on the old cell phone, then
>decode it. It could encode a URL and debug data so that the user could open
>a bug report usi
The Linux developers are considering using QR codes to encode Kernel OOPS
(hard wait) information. Snap a picture of it on the old cell phone, then
decode it. It could encode a URL and debug data so that the user could open
a bug report using it. In our case, such a thing would need to come up on
t
