I'm currently in University on my Co-op term as a COBOL programmer for host
systems (zOS). I have a few basic questions regarding the zArchitecture that I
can't seem to elicit answers to from my co-workers. The questions are as
follows:
1. zOS has a kernel called the BCP, or Base Control Progra
I'll take a try at a few of these.
> -Original Message-
> From: IBM Mainframe Discussion List
> [mailto:[EMAIL PROTECTED] On Behalf Of Kuredjian, Michael
> Sent: Tuesday, July 18, 2006 2:46 PM
> To: IBM-MAIN@BAMA.UA.EDU
> Subject: Newbie Questions!
>
>
>
At least for question 1, go find a manual called the "Principles of
Operations". You can search the IBM website by that name and then download
it to read.
The BCP is nothing more than the core MVS components. MVS is comprised of
many subsystems, each doing a specialized function. The "Kernel" i
djian, Michael" <[EMAIL PROTECTED]>
Reply-To: IBM Mainframe Discussion List
To: IBM-MAIN@BAMA.UA.EDU
Subject: Newbie Questions!
Date: Tue, 18 Jul 2006 15:46:27 -0400
I'm currently in University on my Co-op term as a COBOL programmer for host
systems (zOS). I have a few basic qu
Hi. Welcome to the world of z and IBM-MAIN.
Go to http://www.ibm.com/servers/eserver/zseries/zos/bkserv/
On the right side of the page there is a link to the z/OS basics
skill center and a z/OS Basics Redbook. This Redbook may be a
good place to start along with the basics skill center.
If y
h nearly everything I say above. Welcome to
IBM-MAIN.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of Kuredjian, Michael
Sent: Tuesday, July 18, 2006 12:46 PM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Newbie Questions!
I'm currently in Un
Charles Mills wrote:
... I guess the correct name at
this point for the processor hardware design is "zSeries architecture"
It's called "z/Architecture", just like it says on the cover of the
Principles of Operation manual.
--
Edward E Jaffe
Phoenix Software International, Inc
5200 W Century
>It's called "z/Architecture"
I always called the manual "z/Arch POP".
I picked that up from a Canadian IBM'r.
But, most didn't understand what that meant.
When in doubt.
PANIC!!
--
For IBM-MAIN subscribe / signoff / archive
All of the threads here where right on target, and should serve you well if
you follow them as prescribed. I have found that there is no definitive
source on the architecture. It is really a vast landscape , I actually
read the hardware manual supplied with the 3031 CPU's,, they had a lot of
instr
'Humility'? Anyone entering a new field has perforce much to learn from
some of its experienced denizens, but humility should be short-lived.
No good programmer I have every known was at all humble, and the great ones
were/are well aware of their abilities, even [some few of them] arrogant
ab
I strongly disagree. Some good programmers are arrogant, but then again so are
some bad ones. The best ones realize that they don't -- and can't -- know it
all, and they make allowances for it.
Edsger Dijkstra even made humility the point of a paper he delivered at a
Turing Award lecture, s
On Tue, 18 Jul 2006 15:46:27 -0400, Kuredjian, Michael
<[EMAIL PROTECTED]> wrote:
>I'm currently in University on my Co-op term as a COBOL programmer for
host systems (zOS). I have a few basic questions regarding the
zArchitecture that I can't seem to elicit answers to from my co-workers.
The
I can retrieve the model # of this system as well?
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED]
Behalf Of Tom Marchant
Sent: Wednesday, July 19, 2006 10:35 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Newbie Questions!
On Tue, 18 Jul 2006 15:46:27 -0400, Kur
Kuredjian, Michael wrote:
... It seems as through IBM is modernizing the arch to handle more
OOE/Superscalar execution as they make a push to SOA and e-business models.
IBM invented superscalar. It was used _heavily_ on the mainframes of old
(bipolar ... before CMOS). Those older processors a
Tom,
> FICON is essentially Fibre
> Channel with extra layers to improve security.
Extra layers to improve security?
I would have said that essentially FICON is ESCON encapsulated in Fibre
Channel Protocol.
Ron
--
For IBM-MAIN
On Thu, 20 Jul 2006 02:02:08 +0800, Ron and Jenny Hawkins <[EMAIL PROTECTED]
CABLE.COM> wrote:
>Tom,
>
>> FICON is essentially Fibre
>> Channel with extra layers to improve security.
>
>Extra layers to improve security?
>
>I would have said that essentially FICON is ESCON encapsulated in Fibre
>Ch
I would have said that essentially FICON is ESCON encapsulated in Fibre
Channel Protocol.
Ron, I don't pretend to be expert in channel protocols, but from what I
read the FICON protocols are quite different from ESCON. I've read that
ESCON does a channel-CU conversation for each CCW in a chain
In
<[EMAIL PROTECTED]>,
on 07/18/2006
at 05:26 PM, SUBSCRIBE IBM-MAIN tdell
said:
>To recap..
Much of that is wrong.
>Mainframes don't actually have a backplane that's governed by a bus
>arbitrator scheme as some implementation have done in the past.
Some do.
>That channel subsystem as it
In
<[EMAIL PROTECTED]>,
on 07/18/2006
at 03:46 PM, "Kuredjian, Michael" <[EMAIL PROTECTED]>
said:
>1. zOS has a kernel called the BCP, or Base Control Program.
Now. The term "kernel" in CS carries with it a load of assumptions
that simply don't apply; they aren't even wrong, but totally
meanin
In <[EMAIL PROTECTED]>, on 07/19/2006
at 12:55 AM, john gilmore <[EMAIL PROTECTED]> said:
>No good programmer I have every known was at all humble,
That depends on what you mean be "humility"; every good programmer
that I've met was aware of his own abilities *and* of his own
limitations.
>ev
In <[EMAIL PROTECTED]>,
on 07/19/2006
at 09:57 AM, Jon Brock <[EMAIL PROTECTED]> said:
>Edsger Dijkstra even made humility the point of a paper he delivered
>at a Turing Award lecture, said paper being entitled "The Humble
>Programmer."
Unfortunately, he displayed supreme arrogance in that ve
On 7/19/06, Kuredjian, Michael <[EMAIL PROTECTED]> wrote:
> Through the ISPVCALL STATUS function, I found that the system I'm on is
a zArch 2064 with 4 CPUs; however, is there a way I can retrieve the model #
of this system as well?
2064 is the model number, which is a zSeries 900 processor
Gabriel Tully wrote:
On 7/19/06, Kuredjian, Michael <[EMAIL PROTECTED]> wrote:
> Through the ISPVCALL STATUS function, I found that the system I'm
on is
a zArch 2064 with 4 CPUs; however, is there a way I can retrieve the
model #
of this system as well?
2064 is the model number, which is a z
On 7/19/06, Edward Jaffe <[EMAIL PROTECTED]> wrote:
2064 is the model number, which is a zSeries 900 processor.
>No. 2064 is the CPU type. The model number is a (usually three digit)
>number that follows the type, separated by a hyphen. For example,
2064-101.
Semantics in my opinion. I'
To reap what I have sowed.
Most programmers have confidence, which is not to be confused with
arrogance, which has no place in a craft like this. This is a practiced
craft, so I haven't met anybody , with the exception of the Scientist's at
Palo Alto , who could call themselves above their craft (
>>> Through the ISPVCALL STATUS function, I found that the system I'm
>>> on is a zArch 2064 with 4 CPUs; however, is there a way I can retrieve
the
>>> model # of this system as well?
>>
> >2064 is the model number, which is a zSeries 900 processor.
>
>No. 2064 is the CPU type. The model number
Bruce,
> Ron, I don't pretend to be expert in channel protocols, but from what I
> read the FICON protocols are quite different from ESCON. I've read that
> ESCON does a channel-CU conversation for each CCW in a chain, with data
> blocks in between, but FICON batches up CCWs and usually sends an
>There are many mainframes. The ones that z/OS runs on have
>architectures called S/390 and zSeries.
>
>>If not, are there any documents that I can look into that will
>>describe the CPU architecture for me?
>
>Wouldn't such documents mean that there *is* a common architecture?
>As, in fact, there
> >>> Through the ISPVCALL STATUS function, I found that the system I'm
> >>> on is a zArch 2064 with 4 CPUs; however, is there a way I can
retrieve
[snip]
>All that being said it could be a 2064-104, 2064-1C4, or a 2064-2C4
>depending on features. You can use the command
>"D M=CPU" to find your m
In
<[EMAIL PROTECTED]>,
on 07/20/2006
at 08:47 AM, "Hunkeler Peter (KIUB 34)"
<[EMAIL PROTECTED]> said:
>You're mixing up machine series with architectures:
Good catch. Yes, that's z/Architecture Principles of Operation.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position;
In
<[EMAIL PROTECTED]>,
on 07/19/2006
at 05:02 PM, SUBSCRIBE IBM-MAIN tdell
said:
>PDP's have a bus arbitration or granting scheme,
DEC had a number of very different processors with "PDP" in their
name; I suspect that you're thinking of the PDP-11, and I'm not sure
that it is even true for a
31 matches
Mail list logo