> On 2 Aug 2023, at 11:38 am, Jon Perryman wrote:
>
>> On Tuesday, August 1, 2023 at 05:18:46 PM PDT, David Crayford
>> wrote:
>> The obvious difference is that C/C++ etc are still evolving.
>> The z/OS COBOL compiler hasn’t implemented significant features
>> of the ANSI standard. If I were
> The IBM z16 can have up to 1,536 PCIe+ slots
I'm gonna quit explaining this and just say, "WRONG" every time you say
this as if it's a fact :)
On 8/1/2023 8:01 PM, Jon Perryman wrote:
> On Tuesday, August 1, 2023 at 05:20:33 PM PDT, David Crayford
wrote:
What’s the difference between
> On Tuesday, August 1, 2023 at 05:18:46 PM PDT, David Crayford
> wrote:
> The obvious difference is that C/C++ etc are still evolving.
> The z/OS COBOL compiler hasn’t implemented significant features
> of the ANSI standard. If I were a COBOL programmer I would like
> the language to
Take for example an Emulex (Broadcom) HBA. The quad port adapter can handle up
to 10M IOPS with a throughput rate of 12,800MB/s full duplex using 16-lane PCIe
which utilities DMA. All I/O is offloaded, interrupts, multiplexing etc. When
you consider that a standard commodity rack server such as
> On Tuesday, August 1, 2023 at 05:20:33 PM PDT, David Crayford
> wrote:
> What’s the difference between between channelized I/O and a rack of
> x86 servers connected to a SAN using fibre channel driven by high speed HBAs?
PCIe was created specifically for PCs and IBM z16 chose to use that
On 8/1/23 7:20 PM, David Crayford wrote:
What’s the difference between between channelized I/O and a rack
of x86 servers connected to a SAN using fibre channel driven by high
speed HBAs?
I don't know.
My understanding is that Fibre Channel is an evolution of SCSI which is
supposedly a
What’s the difference between between channelized I/O and a rack of x86 servers
connected to a SAN using fibre channel driven by high speed HBAs?
> On 2 Aug 2023, at 6:53 am, Grant Taylor
> <023065957af1-dmarc-requ...@listserv.ua.edu> wrote:
>
> On 8/1/23 3:10 PM, Rick Troth wrote:
>> Look
> On 31 Jul 2023, at 10:28 pm, Seymour J Metz wrote:
>
> The media sling around terms like dinosaur and legacy for mainframes and
> mainframe software, and tout "new" languages and platforms like C, Unix and
> windows. But look at the dates and explain to me, e.g., how z is legacy but
> x86
On 8/1/23 3:10 PM, Rick Troth wrote:
Look for channelized I/O,
Didn't supers ~> cray use channelized I/O?
Also, I feel like there is another slippery slope discussion of what is
channelized I/O in this context.
then other physical attributes (not just size, not just the instruction
set).
I do not recall Multi-core cpus being part of the initial z/arch
disclosure in 1979 when I was at that special meeting in POK for
CA. The ideas of the G3 chipset was announced about 2001 at
another disclosure meeting I went to in NY (forgot the name of
the town, it was not POK) given by Bob
> On Tuesday, August 1, 2023 at 12:54:10 PM PDT, Steve Thompson
> wrote:
> when IBM comes up with a new Architecture...
AFAIK, IBM z is not a new architecture. Intel, Sun & HP invented multi-core CPU
chips. Intel invented PCI and PCIe. What is the new architecture that IBM z
introduced?
> On Tuesday, August 1, 2023 at 07:59:07 AM PDT, Grant Taylor wrote:
>> On 8/1/23 2:49 AM, Colin Paice wrote:
>> You can have synchronous write - used in same "site" and async -
>> where the remote end is miles away. This is used for media failure.
> Yes. Emphasis on /media/
W dniu 01.08.2023 o 19:52, Phil Smith III pisze:
Sebastian Welton wrote:
https://www.fujitsu.com/de/products/computing/servers/mainframe/bs2000/
Heh heh, "BS2000". Reminds me of the company that bought the NOMAD product: Select
Business Systems; their domain was SelectBS.com. Wow, make that
I've been told by some sales folks not to use the M-word when talking
about LinuxONE. I feel like HAL keeping secrets from the crew of
Discovery One. No relation to Linux One - or is there?
On 8/1/2023 12:44 PM, Phil Smith III wrote:
Jon Perryman wrote:
The last Fujitsu mainframe is
I had a brief exposure to Burroughs machines in the mid-1970s.
I would say that the B6700 was definitely a mainframe, as well as the B6800
that
followed it.
I've never worked with any Univac mainframes, nor am I familiar with the
current
line from Unisys. It has been said here that the
I don't know what you mean, Mike. Access Registers (introduced with ESA/390) do
not
point to pages or bytes, but to address spaces or data spaces.
--
Tom Marchant
On Tue, 1 Aug 2023 15:09:01 -0500, Mike Schwab wrote:
>Of course ¿ESA? did create access registers that point to 4K pages
An access register points (indirectly) to an entire address space, not just a
page.
From: IBM Mainframe Discussion List on behalf of
Mike Schwab
Sent: Tuesday, August 1, 2023 4:09 PM
To: IBM-MAIN@LISTSERV.UA.EDU
Subject: Re: Mainframe Makers WAS:
On 8/1/23 15:44, Phil Smith III wrote:
Jon Perryman wrote:
The last Fujitsu mainframe is scheduled for 2030 and dropping all
support by 2035. Honeywell Bull GCOS and Unisys OS 2200 and MCP are
now x86 based. Are these mainframes or are they PCs?
PCframes? mainCs? It is hard to define
On 40TB main memory now, so only 20,480 x since 1999 intro of 64 in 24
years.
Of course ¿ESA? did create access registers that point to 4K pages instead
of bytes, so 8/16 TB was possible.
On Tue, Aug 1, 2023, 14:54 Steve Thompson wrote:
> How about we change from Mainframe to zFrame?
>
> Yeah,
How about we change from Mainframe to zFrame?
Yeah, I know, then when IBM comes up with a new Architecture...
How long will it take to need > 64bit addressing?
Steve Thompson
On 8/1/2023 3:44 PM, Phil Smith III wrote:
Jon Perryman wrote:
The last Fujitsu mainframe is scheduled for 2030 and
Jon Perryman wrote:
>The last Fujitsu mainframe is scheduled for 2030 and dropping all
>support by 2035. Honeywell Bull GCOS and Unisys OS 2200 and MCP are
>now x86 based. Are these mainframes or are they PCs?
PCframes? mainCs? It is hard to define rigorously, but as someone else quoted
SCOTUS,
Sebastian Welton wrote:
>https://www.fujitsu.com/de/products/computing/servers/mainframe/bs2000/
Heh heh, "BS2000". Reminds me of the company that bought the NOMAD product:
Select Business Systems; their domain was SelectBS.com. Wow, make that "is", it
lives:
Brian Westerman asked:
>so you can use authsmtp.com to send directly from CSSMTP?
It's just an SMTP server, so if you can get there from your network, sure.
>When you send the email, does it come from where you say it should or
>do you have to use a special email that they give you?
You tell it
Williams tube: periodic regeneration
Drum: stable
Delay line: amplification
Core, rod, thin film: destructive read followed by rewrite
From: IBM Mainframe Discussion List on behalf of
Mike Schwab
Sent: Tuesday, August 1, 2023 12:24 PM
To:
I think most pre- semiconductor memory including core memory in S/360 was
destructive reads with hardware rewiting the store, so you can certainly
understand using move, not to mention C for Compare instructions had few
alternatives.
On Tue, Aug 1, 2023, 10:51 Seymour J Metz wrote:
> The term
The term of art "move" goes back at least to the 705, well before COBOL, so
even if it's confusing it's not likely to change.
From: IBM Mainframe Discussion List on behalf of
Gary Weinhold
Sent: Tuesday, August 1, 2023 11:38 AM
To:
>> Wayne B wrote:
COBOL MOVE was not intuitive. Should have been PROPOGATE or COPY, COPY was
already taken I guess.
Assembler has the same problem: MVC, MVCL, etc.
Gary Weinhold
Senior Application Architect
DATAKINETICS | Data Performance & Optimization
Phone:+1.613.523.5500 x216
Email:
On 8/1/23 2:49 AM, Colin Paice wrote:
Your Copy on Write - may be what I know as dual write - where you
write to different volumes - usually on different dasd subsystems,
so if you lose one dasd subsystem - the data is available on another.
Nope. "Copy on Write" is explicitly what you were
Thanks to help from Sir Dave the Generous,
we confirmed that the XMITMSGX Rexx support built with Regina works just
fine with ooRexx. Yay!
I had been trying to build against ooRexx expecting some linkage
differences, but *someone* in ooRexx land made things compatible between
ooRexx and
In Co:Z, linerule=L4 (4 byte length prefixes) and linerule=rdw (IBM compatible
RDWs) are different things. There is also a linerule=mfrdw, but you'll have
to look at the documentation for that.
Kirk Wolf
On Mon, Jul 31, 2023, at 6:29 PM, Paul Gilmartin wrote:
> On Mon, 31 Jul 2023 17:16:20
https://www.fujitsu.com/de/products/computing/servers/mainframe/bs2000/
Sebastian
--
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
Your Copy on Write - may be what I know as dual write - where you write to
different volumes - usually on different dasd subsystems, so if you lose
one dasd subsystem - the data is available on another.
You can have synchronous write - used in same "site" and async - where the
remote end is miles
32 matches
Mail list logo
