Re: What version am I running?

[Mark Pace]

Thank you both.  I knew it was simple, but I just couldn't find it.
Now I need a better memory, because my main FTP server says it's SP2 and I
do NOT remember upgrading it.  :(

Oh well, one less step to get it to SP3.  :)


On Thu, Jul 25, 2013 at 2:43 PM, Mauro Souza  wrote:

> I usually run
> # cat /etc/*release
>
> So wherever it's SuSE, RedHat, Ubuntu, Fedora or almost anything, I can get
> the distro version.
>
> And to get the kernel version:
> # uname -a
>
>
>
>
> Mauro
> http://mauro.limeiratem.com - registered Linux User: 294521
> Scripture is both history, and a love letter from God.
>
>
> 2013/7/25 Pedro Principeza 
>
> > Hi Mark.
> >
> > Run:
> >
> > # cat /etc/SuSE-release
> > # uname -a
> >
> > That'll tell you the version of SuSE and the kernel version + patches.
> >
> > --
> > Pedro Principeza
> >
> >
> >
> > From:   Mark Pace 
> > To: LINUX-390@vm.marist.edu,
> > Date:   25/07/2013 15:30
> > Subject:What version am I running?
> > Sent by:Linux on 390 Port 
> >
> >
> >
> > I know I've read how to do this in the past, but I can not find it
> > anywhere
> > in my archives.
> >
> > How do I determine what version of SLES I am running?
> >
> > --
> > The postings on this site are my own and don’t necessarily represent
> > Mainline’s positions or opinions
> >
> > Mark D Pace
> > Senior Systems Engineer
> > Mainline Information Systems
> >
> > --
> > 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/
>



-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
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: TX-Errs on hipersocket interface.

[Bruce Hayden]

Ron,
See page 11 of this presentation:
http://www.vm.ibm.com/service/vmreqzeh.html
This presentation is found on
http://www.ibm.com/developerworks/linux/linux390/perf/tuning_networking.htmlwhere
there are other good tuning tips.


On Thu, Jul 25, 2013 at 2:42 PM, Ron Foster wrote:

> The receiver is zos.  Anybody here know how to increase the buffers in zos.
>
> Ron
>
> Sent from my iPhone
>
>
>

--
Bruce Hayden
z/VM and Linux on System z ATS
IBM, Endicott, NY

--
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: What version am I running?

[Mauro Souza]

I usually run
# cat /etc/*release

So wherever it's SuSE, RedHat, Ubuntu, Fedora or almost anything, I can get
the distro version.

And to get the kernel version:
# uname -a




Mauro
http://mauro.limeiratem.com - registered Linux User: 294521
Scripture is both history, and a love letter from God.


2013/7/25 Pedro Principeza 

> Hi Mark.
>
> Run:
>
> # cat /etc/SuSE-release
> # uname -a
>
> That'll tell you the version of SuSE and the kernel version + patches.
>
> --
> Pedro Principeza
>
>
>
> From:   Mark Pace 
> To: LINUX-390@vm.marist.edu,
> Date:   25/07/2013 15:30
> Subject:What version am I running?
> Sent by:Linux on 390 Port 
>
>
>
> I know I've read how to do this in the past, but I can not find it
> anywhere
> in my archives.
>
> How do I determine what version of SLES I am running?
>
> --
> The postings on this site are my own and don’t necessarily represent
> Mainline’s positions or opinions
>
> Mark D Pace
> Senior Systems Engineer
> Mainline Information Systems
>
> --
> 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: TX-Errs on hipersocket interface.

[Ron Foster]

The receiver is zos.  Anybody here know how to increase the buffers in zos. 

Ron

Sent from my iPhone

On Jul 25, 2013, at 1:14 PM, "Ursula Braun"  wrote:

> Ron,
> 
> Carsten's first explanation is correct. If you see tx_errors on a
> HiperSockets interface, it usually means transmission of a packet fails
> because the receiver has currently no free receive buffer. You should
> verify first if the receiver has configured the maximum of 128 buffers
> (sysfs attribute buffer_count) for his HiperSockets device. 128 is
> nowadays the default, but older qeth driver versions run with a default
> of 16. If you see the tx_errors even though your receiver runs already
> with the maximum of 128 buffers, you either have to live with the
> autotuning mechanisms of tcp or you take actions to slow down the sender
> or to accelerate the receiver.
> 
> As Alan suggested we can document this in the Device Driver book. The
> other option would be to change the current behavior of the qeth driver
> and increase probably both the tx_dropped and the tx_error counter.
> 
> It is definitely not a problem to report to SuSe folks.
> 
> Kind regards, Ursula Braun, Linux on System z development, IBM Germany
> 
> On Thu, 2013-07-25 at 13:18 +, Ron Foster wrote:
>> Carsten,
>> 
>> Do you know where I would start looking for causes of the transmit errors on 
>> Hipersockets?
>> 
>> The error is occurring on SLES11 SP2 systems.  We are not having it on our 
>> SLES10 SP4 systems.
>> 
>> Do I need to open a problem with the SuSe folks?
>> 
>> Thanks,
>> 
>> Ron Foster
>> 
>> Baldor Electric Company
>> 
>> 5711 R S Boreham Jr Street
>> 
>> Fort Smith, AR 72901
>> 
>> Phone:479-648-5865
>> 
>> Fax:479-646-5440
>> 
>> Email: ron.fos...@baldor.abb.com
>> 
>> IM Address:rfos...@baldor.com
>> 
>> www.baldor.com
>> 
>> 
>> 
>> 
>> From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of Carsten Otte 
>> [co...@de.ibm.com]
>> Sent: Thursday, July 25, 2013 7:53 AM
>> To: LINUX-390@VM.MARIST.EDU
>> Subject: Re: TX-Errs on hipersocket interface.
>> 
>> Alan wrote:
>>> Carsten, this is information that really needs to be in the Device Driver
>>> book, as it differs from the traditional interpretation of TX/RX counters.
>> Ah, you're right - that would be accouned as dropped, not TX error. Forget
>> about my
>> reply then, time to look at other causes for that TX error. Sorry for the
>> noise.
>> 
>> with kind regards
>> Carsten Otte
>> System z firmware development / Boeblingen lab
>> ---
>> Every revolution was first a thought in one man's mind;
>> and when the same thought occurs to another man, it is the key to that era.
>> 
>> - Ralph Waldo Emerson, Essays: First Series, 1841
>> 
>> --
>> 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/
> 
> --
> 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: What version am I running?

[Pedro Principeza]

Hi Mark.

Run:

# cat /etc/SuSE-release
# uname -a

That'll tell you the version of SuSE and the kernel version + patches.

--
Pedro Principeza



From:   Mark Pace 
To: LINUX-390@vm.marist.edu, 
Date:   25/07/2013 15:30
Subject:What version am I running?
Sent by:Linux on 390 Port 



I know I've read how to do this in the past, but I can not find it 
anywhere
in my archives.

How do I determine what version of SLES I am running?

-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

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

What version am I running?

[Mark Pace]

I know I've read how to do this in the past, but I can not find it anywhere
in my archives.

How do I determine what version of SLES I am running?

-- 
The postings on this site are my own and don’t necessarily represent
Mainline’s positions or opinions

Mark D Pace
Senior Systems Engineer
Mainline Information Systems

--
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: TX-Errs on hipersocket interface.

[Veencamp, Jonathon D.]

Question:  Why would SLES 11 see hipersocket retransmits and window adjustments 
and not SLES 10?  Is the device driver either more forgiving or efficient on 
SLES 10?

I'm just curious.  I may be in the same situation soon.

Regards
Jon Veencamp
Federated Insurance

-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Ursula 
Braun
Sent: Thursday, July 25, 2013 9:54 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: TX-Errs on hipersocket interface.

Ron,

Carsten's first explanation is correct. If you see tx_errors on a
HiperSockets interface, it usually means transmission of a packet fails
because the receiver has currently no free receive buffer. You should
verify first if the receiver has configured the maximum of 128 buffers
(sysfs attribute buffer_count) for his HiperSockets device. 128 is
nowadays the default, but older qeth driver versions run with a default
of 16. If you see the tx_errors even though your receiver runs already
with the maximum of 128 buffers, you either have to live with the
autotuning mechanisms of tcp or you take actions to slow down the sender
or to accelerate the receiver.

As Alan suggested we can document this in the Device Driver book. The
other option would be to change the current behavior of the qeth driver
and increase probably both the tx_dropped and the tx_error counter.

It is definitely not a problem to report to SuSe folks.

Kind regards, Ursula Braun, Linux on System z development, IBM Germany

On Thu, 2013-07-25 at 13:18 +, Ron Foster wrote:
> Carsten,
> Do you know where I would start looking for causes of the transmit errors on 
> Hipersockets?
> The error is occurring on SLES11 SP2 systems.  We are not having it on our 
> SLES10 SP4 systems.
> Do I need to open a problem with the SuSe folks?
>
> Thanks,
> Ron Foster
> Baldor Electric Company
> 5711 R S Boreham Jr Street
> Fort Smith, AR 72901



The information contained in this e-mail message is intended only for the 
personal and confidential use of the designated recipient(s) named above. This 
message may be an attorney-client or work product communication which is 
privileged and confidential. It may also contain protected health information 
that is protected by federal law. If you have received this communication in 
error, please notify us immediately by telephone and destroy (shred) the 
original message and all attachments. Any review, dissemination, distribution 
or copying of this message by any person other than the intended recipient(s) 
or their authorized agents is strictly prohibited. Thank you.

Re: TX-Errs on hipersocket interface.

[Ursula Braun]

Ron,

Carsten's first explanation is correct. If you see tx_errors on a
HiperSockets interface, it usually means transmission of a packet fails
because the receiver has currently no free receive buffer. You should
verify first if the receiver has configured the maximum of 128 buffers
(sysfs attribute buffer_count) for his HiperSockets device. 128 is
nowadays the default, but older qeth driver versions run with a default
of 16. If you see the tx_errors even though your receiver runs already
with the maximum of 128 buffers, you either have to live with the
autotuning mechanisms of tcp or you take actions to slow down the sender
or to accelerate the receiver.

As Alan suggested we can document this in the Device Driver book. The
other option would be to change the current behavior of the qeth driver
and increase probably both the tx_dropped and the tx_error counter.

It is definitely not a problem to report to SuSe folks.

Kind regards, Ursula Braun, Linux on System z development, IBM Germany

On Thu, 2013-07-25 at 13:18 +, Ron Foster wrote:
> Carsten,
>
> Do you know where I would start looking for causes of the transmit errors on 
> Hipersockets?
>
> The error is occurring on SLES11 SP2 systems.  We are not having it on our 
> SLES10 SP4 systems.
>
> Do I need to open a problem with the SuSe folks?
>
> Thanks,
>
> Ron Foster
>
> Baldor Electric Company
>
> 5711 R S Boreham Jr Street
>
> Fort Smith, AR 72901
>
> Phone:479-648-5865
>
> Fax:479-646-5440
>
> Email: ron.fos...@baldor.abb.com
>
> IM Address:rfos...@baldor.com
>
> www.baldor.com
>
>
>
> 
> From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of Carsten Otte 
> [co...@de.ibm.com]
> Sent: Thursday, July 25, 2013 7:53 AM
> To: LINUX-390@VM.MARIST.EDU
> Subject: Re: TX-Errs on hipersocket interface.
>
> Alan wrote:
> >Carsten, this is information that really needs to be in the Device Driver
> >book, as it differs from the traditional interpretation of TX/RX counters.
> Ah, you're right - that would be accouned as dropped, not TX error. Forget
> about my
> reply then, time to look at other causes for that TX error. Sorry for the
> noise.
>
> with kind regards
> Carsten Otte
> System z firmware development / Boeblingen lab
> ---
> Every revolution was first a thought in one man's mind;
> and when the same thought occurs to another man, it is the key to that era.
>
>  - Ralph Waldo Emerson, Essays: First Series, 1841
>
> --
> 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/
>

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

new IBM zBC12

[Dave Jones]

http://bits.blogs.nytimes.com/2013/07/23/mainframe-computers-that-change-with-the-times/?_r=0
--
Dave Jones
V/Soft Software
www.vsoft-software.com
Houston, TX
281.578.7544

--
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: Query for Destination z article -- computer museums

[David Boyes]

> It has been years since I was there but the Chicago Museum of Science and
> Industry had great exhibit of computers.
> I remember they had an IBM RAMAC 305 (I think it was working) along with
> many other historic devices.

Saw one version of it a few years ago. I don't think their RAMAC works. 

Another one with a good collection: Smithsonian Museum of American History.

--
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: TX-Errs on hipersocket interface.

[Ron Foster]

Carsten, 

Do you know where I would start looking for causes of the transmit errors on 
Hipersockets?

The error is occurring on SLES11 SP2 systems.  We are not having it on our 
SLES10 SP4 systems.

Do I need to open a problem with the SuSe folks?

Thanks,

Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.com

IM Address:rfos...@baldor.com

www.baldor.com




From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of Carsten Otte 
[co...@de.ibm.com]
Sent: Thursday, July 25, 2013 7:53 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: TX-Errs on hipersocket interface.

Alan wrote:
>Carsten, this is information that really needs to be in the Device Driver
>book, as it differs from the traditional interpretation of TX/RX counters.
Ah, you're right - that would be accouned as dropped, not TX error. Forget
about my
reply then, time to look at other causes for that TX error. Sorry for the
noise.

with kind regards
Carsten Otte
System z firmware development / Boeblingen lab
---
Every revolution was first a thought in one man's mind;
and when the same thought occurs to another man, it is the key to that era.

 - Ralph Waldo Emerson, Essays: First Series, 1841

--
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: Performance on SLES11 SP2 guest after migration from SLES10 SP4

[Ron Foster]

Berry,

Thanks

Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.com

IM Address:rfos...@baldor.com

www.baldor.com




From: Linux on 390 Port [LINUX-390@VM.MARIST.EDU] on behalf of van Sleeuwen, 
Berry [berry.vansleeu...@atos.net]
Sent: Thursday, July 25, 2013 1:48 AM
To: LINUX-390@VM.MARIST.EDU
Subject: Re: Performance on SLES11 SP2 guest after migration from SLES10 SP4

Hi Ron,

There is a bug in vmstat that results in zero IO. I have seen the same when 
investigating a CCL problem. So don't (for now) rely on the IO counter in 
VMSTAT.

I did report it to IBM and I guess through that channel an update for vmstat 
will be created.

Regards, Berry.

-Original Message-
From: Linux on 390 Port [mailto:LINUX-390@VM.MARIST.EDU] On Behalf Of Ron Foster
Sent: woensdag 24 juli 2013 18:03
To: LINUX-390@VM.MARIST.EDU
Subject: Performance on SLES11 SP2 guest after migration from SLES10 SP4


Hello listers,



Over the weekend, we migrated a couple of large SAP systems from SLES10 SP4 to 
SLES11 SP2.  These are large SAP application servers (22GB).



Our SAP folks have a transaction that can be used to measure SAP response time. 
 Our servers are grouped by the applications they run.



Intermittantly one of the SAP application servers in one group will for a while 
have a response time that is about 3 times larger that the SLES10 systems.  
1600 ms  vs 500 ms.  The other sles11 system in the other application group 
will have a response time that is around 700 ms, and the others in the group 
have around 350 ms.  After a few minutes the response times on the SLES11 
systems return to normal.



I start to look at things.  I issue the vmstat command and find something.  The 
in column in the system area is all zeros.  The man page says that this is the 
number of interrupts per second.



Anyone else experience response time problems, or not get the interrupts 
information?



Ron Foster

Baldor Electric Company

5711 R S Boreham Jr Street

Fort Smith, AR 72901

Phone:479-648-5865

Fax:479-646-5440

Email: ron.fos...@baldor.abb.com

IM Address:rfos...@baldor.com

www.baldor.com



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





Dit bericht is vertrouwelijk en kan geheime informatie bevatten enkel bestemd 
voor de geadresseerde. Indien dit bericht niet voor u is bestemd, verzoeken wij 
u dit onmiddellijk aan ons te melden en het bericht te vernietigen. Aangezien 
de integriteit van het bericht niet veilig gesteld is middels verzending via 
internet, kan Atos Nederland B.V. niet aansprakelijk worden gehouden voor de 
inhoud daarvan. Hoewel wij ons inspannen een virusvrij netwerk te hanteren, 
geven wij geen enkele garantie dat dit bericht virusvrij is, noch aanvaarden 
wij enige aansprakelijkheid voor de mogelijke aanwezigheid van een virus in dit 
bericht. Op al onze rechtsverhoudingen, aanbiedingen en overeenkomsten 
waaronder Atos Nederland B.V. goederen en/of diensten levert zijn met 
uitsluiting van alle andere voorwaarden de Leveringsvoorwaarden van Atos 
Nederland B.V. van toepassing. Deze worden u op aanvraag direct kosteloos 
toegezonden.

This e-mail and the documents attached are confidential and intended solely for 
the addressee; it may also be privileged. If you receive this e-mail in error, 
please notify the sender immediately and destroy it. As its integrity cannot be 
secured on the Internet, the Atos Nederland B.V. group liability cannot be 
triggered for the message content. Although the sender endeavours to maintain a 
computer virus-free network, the sender does not warrant that this transmission 
is virus-free and will not be liable for any damages resulting from any virus 
transmitted. On all offers and agreements under which Atos Nederland B.V. 
supplies goods and/or services of whatever nature, the Terms of Delivery from 
Atos Nederland B.V. exclusively apply. The Terms of Delivery shall be promptly 
submitted to you on your request.

Atos Nederland B.V. / Utrecht
KvK Utrecht 30132762

--
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: Query for Destination z article -- computer museums

[Tom Huegel]

It has been years since I was there but the Chicago Museum of Science and
Industry had great exhibit of computers.
I remember they had an IBM RAMAC 305 (I think it was working) along with
many other historic devices.

It has been quite a while since I was there, has anyone seen this exhibit
lately?


On Wed, Jul 24, 2013 at 5:27 PM, David Boyes  wrote:

> Second this one. They have the other running 360/20 in the world. Lots of
> vintage gear.
>
>
>
> On Jul 24, 2013, at 6:09 PM, "Dave Jones"  wrote:
>
> > Hi, Gabe.
> >
> > I hear that the IBM Boebligin (Germany) lab has a nice S/360 museum.
> >
> > Have a good one, too.
> >
> > DJ
> >
> > On 07/24/2013 08:41 AM, Gabe Goldberg wrote:
> >> They're everywhere -- once I started looking for them.
> >>
> >> I knew about -- have toured -- Computer History Museum  --
> >> www.computerhistory.org/
> >>
> >> And I recently saw a great presentation on The Living Computer Museum
> >> -- www.livingcomputermuseum.org/
> >>
> >> But I hadn't known about American Computer & Robotics Museum --
> >> www.compustory.com/
> >>
> >> I wonder what other museums exist -- especially any with relevance to
> >> mainframes -- so I'll appreciate tips/pointers and, especially, hearing
> >> about experiences joining/supporting/visiting them. (Or contributing
> >> artifacts to them. Maintaining private collections of mainframe
> >> components as some people I know do is interesting but might not qualify
> >> as operating a museum. My wife called one such residence decorated with
> >> large mainframe components a "computer mausoleum" -- but I liked it.)
> >>
> >> Too bad, I have no budget for world tour of museums -- so I'll have to
> >> visit virtually.
> >>
> >> Please copy me directly so responses don't get lost in list digests.
> >> Thanks...
> >>
> >> --
> >> Gabriel Goldberg, Computers and Publishing, Inc.
> g...@gabegold.com
> >> 3401 Silver Maple Place, Falls Church, VA 22042   (703)
> 204-0433
> >> LinkedIn: http://www.linkedin.com/in/gabegoldTwitter:
> GabeG0
> >>
> >> --
> >> 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/
> >>
> >
> > --
> > Dave Jones
> > V/Soft Software
> > www.vsoft-software.com
> > Houston, TX
> > 281.578.7544
> >
> > --
> > 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/
>

--
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: TX-Errs on hipersocket interface.

[Carsten Otte]

Alan wrote:
>Carsten, this is information that really needs to be in the Device Driver
>book, as it differs from the traditional interpretation of TX/RX counters.
Ah, you're right - that would be accouned as dropped, not TX error. Forget
about my
reply then, time to look at other causes for that TX error. Sorry for the
noise.

with kind regards
Carsten Otte
System z firmware development / Boeblingen lab
---
Every revolution was first a thought in one man's mind;
and when the same thought occurs to another man, it is the key to that era.

 - Ralph Waldo Emerson, Essays: First Series, 1841

--
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: TX-Errs on hipersocket interface.

[Alan Altmark]

On Thursday, 07/25/2013 at 02:58 EDT, Carsten Otte 
wrote:
> TX errors on a Hipersocket are business as usual. When the receiver
fails
> to pick up packets at the same rate that the transmitter transmits, the
> queues will run full over time. TCP uses packet loss as a measure to
> tune the TCP window size, which effectively will reduce the transmit
rate.
> Thus, the packet loss you see only indicates that trimming down
transmits
> to match the receiver's performance is taking place.

Carsten, this is information that really needs to be in the Device Driver
book, as it differs from the traditional interpretation of TX/RX counters.

Alan Altmark

Senior Managing z/VM and Linux Consultant
IBM System Lab Services and Training
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://www.marist.edu/htbin/wlvindex?LINUX-390
--
For more information on Linux on System z, visit
http://wiki.linuxvm.org/