In [EMAIL PROTECTED], on 06/23/2006
at 06:59 PM, Anne Lynn Wheeler [EMAIL PROTECTED] said:
tss/360 (the real operating system that was suppose to be for
360/67) had a different mechanism ... moving address constants out
of the program image
You don't consider a PSECT to be part of the
On Fri, 23 Jun 2006 19:26:58 -0300, Shmuel Metz (Seymour J.) shmuel+ibm-
[EMAIL PROTECTED] wrote:
In [EMAIL PROTECTED], on 06/23/2006
at 10:38 AM, Tom Marchant [EMAIL PROTECTED] said:
Amdahl didn't believe in virtual memory. It seems like he would have
anticipated the need for it, with the
In a message dated 6/26/2006 7:34:24 A.M. Central Standard Time,
[EMAIL PROTECTED] writes:
Not that I am aware of.
The second one went to U of M, as I recall. IIRC, the first went to NASA.
So long ago(and far away). My advisor was from Michigan and he always
complained that we didn't
On Mon, 26 Jun 2006 07:34:10 -0500, Tom Marchant [EMAIL PROTECTED]
wrote:
On Fri, 23 Jun 2006 19:26:58 -0300, Shmuel Metz (Seymour J.) shmuel+ibm-
[EMAIL PROTECTED] wrote:
Didn't they ship one 470/6? It definitely was the machine originally
announced. As I recall the first 470V went to Bernie
Thomas Kern wrote:
At the Goddard Institute of Space Studies initially, and then we moved it
down to Maryland and became the Goddard Modelling and Simulation Facility.
Just think about it, we used to run multiple global weather models in the 6M
of real memory that maxed out the 470/V6. You can't
On Mon, 26 Jun 2006 08:54:22 EDT, Ed Finnell [EMAIL PROTECTED] wrote:
So long ago(and far away). My advisor was from Michigan and he always
complained that we didn't have this and didn't have that like they did at
Michigan.
I don't remember them all LaPlume, TSS,
snip!
... decided to write
In a message dated 6/26/2006 9:13:56 A.M. Central Standard Time,
[EMAIL PROTECTED] writes:
worked. I never worked with MTS, but they continued to run it intil
the mid to late 1990s. It was the first of the mainframe operating
systems that they dumped. For a time, we ran MVT under MTS on
In [EMAIL PROTECTED], on 06/26/2006
at 07:34 AM, Tom Marchant [EMAIL PROTECTED] said:
The second one went to U of M, as I recall. IIRC, the first went to
NASA.
If UofM was 2nd then NASA was definitely first.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see
://www.garlic.com/~lynn/2006m.html#27 Old Hashing Routine
in past posts i've told the story both ways ... both of the unused bits
by architecture allowing PTEs to address up to 2**14 4k real pages
(64mbyte) or one unused bit by 3033 to support 2**13 4k real pages. I
remember lots of 32mbyte 3081s
Anne Lynn Wheeler wrote:
the other issue is that ckd dasd from the 60s ... traded off i/o thruput
with extended ( multi-track) searches for real memory use ... i.e. more
real memory intensive tended to cache indexes to specific disk location
... while vtoc pds multi-track search spun the
In [EMAIL PROTECTED], on 06/22/2006
at 10:16 AM, Charles Mills [EMAIL PROTECTED] said:
Was it Gene Amdahl who said the biggest mistake of the 360
architecture was the 24-bit addresses?
I don't know, but it certainly shocked me, given that there were
already machines with a million words of
On Fri, 23 Jun 2006 11:10:59 -0300, Shmuel Metz (Seymour J.) shmuel+ibm-
[EMAIL PROTECTED] wrote:
In [EMAIL PROTECTED], on 06/22/2006
at 10:16 AM, Charles Mills [EMAIL PROTECTED] said:
Was it Gene Amdahl who said the biggest mistake of the 360
architecture was the 24-bit addresses?
snip!
I
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of Shmuel Metz (Seymour J.)
Sent: Friday, June 23, 2006 7:11 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Old Hashing Routine
I wouldn't call that the biggest mistake, however. When the S/360 came
out
Discussion List, IBM
ReplyTo: Mainframe Discussion List, IBM
Sent: Jun 22, 2006 11:42
Subject: Re: Old Hashing Routine
just a thought
1. there are numerous callable routines in icsf to (de)encrypt/hash
anything, esp pin's, ie the finical services suite. even smp is into icsf
hashing and w/ 1.7 you
Shmuel Metz , Seymour J. wrote:
I don't know, but it certainly shocked me, given that there were
already machines with a million words of memory. It didn't take a
crystal ball to forsee growing memory demand.
I wouldn't call that the biggest mistake, however. When the S/360 came
out virtually
In [EMAIL PROTECTED], on 06/23/2006
at 09:13 AM, Charles Mills [EMAIL PROTECTED] said:
I agree it's a shortcoming. FWIW, My impression has always been that
the hardware architects thought the base register/displacement scheme
was their answer to or version of hardware relocation.
Indeed, but
In [EMAIL PROTECTED], on 06/23/2006
at 10:38 AM, Tom Marchant [EMAIL PROTECTED] said:
Amdahl didn't believe in virtual memory. It seems like he would have
anticipated the need for it, with the 360/67 already out, but the
original design for the 470/6 (IIRC) had to be stopped while they
added
IBM Mainframe Discussion List IBM-MAIN@BAMA.UA.EDU wrote on 06/23/2006
02:11:54 PM:
so 3033 came up with a hack for supporting 32mbyte real storage. the 370
page table entry was 16bits with a 12bit page number field (for
specifying a real 4k page ... 12+12 gives 24bit addressing or
Shmuel Metz , Seymour J. wrote:
Indeed, but they forgot the need to adjust address constants and
variables when moving things around. They should have given the
software types more say in the design.
os/360 relocatable address constants are a real pain.
tss/360 (the real operating system that
My client has instructed me to modify some modules so that they run
above the line. This was a no brainer until I ran across a call to
module BQKDPRS in several of the modules. This is an old (1970's)
hashing routine for encrypting and decrypting a pin
number. Naturally the client only has
PROTECTED] On Behalf
Of Stephen M. Wiegand
Sent: Thursday, June 22, 2006 7:01 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Old Hashing Routine
My client has instructed me to modify some modules so that they run
above the line. This was a no brainer until I ran across a call to
module BQKDPRS in several
just a thought
1. there are numerous callable routines in icsf to (de)encrypt/hash
anything, esp pin's, ie the finical services suite. even smp is into icsf
hashing and w/ 1.7 you don't even need to start up icsf, i've heard
2. leave the hash routine as a separate callable load module in 24b
Charles Mills wrote:
There is nothing about an older program that necessarily means it will
not
run AMODE 31.
A common practice used by older programs is using LA to clear the how
order byte, which is a problem if it's a 31-bit address.
it a try. There's no guarantee that it WON'T work.
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of Richard Tsujimoto
Sent: Thursday, June 22, 2006 8:42 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Old Hashing Routine
Charles Mills wrote
You might take a look at the HASHWF package on the IBM z/VM Downloads website:
HASHWF 2000-01-12 A General HASH function (S/370 and other systems)
The hashing code is supplied in Assembler source code. I do not know if it is
really capable of running above the line, but the Rexx function
If you can use a 'new fangled' program object instead of a load module as
your executable, then RMODE(SPLIT) provides a nice resolution of such
problems as you describe: AMODE(24) for a few intractable, difficult to
convert routines and RMODE(31) for all the rest.
John Gilmore
Ashland, MA
was the 24-bit addresses?
Charles
-Original Message-
From: IBM Mainframe Discussion List [mailto:[EMAIL PROTECTED] On Behalf
Of john gilmore
Sent: Thursday, June 22, 2006 9:47 AM
To: IBM-MAIN@BAMA.UA.EDU
Subject: Re: Old Hashing Routine
If you can use a 'new fangled' program object
Subject: Old Hashing Routine
My client has instructed me to modify some modules so that they run
above the line. This was a no brainer until I ran across a call to
module BQKDPRS in several of the modules. This is an old (1970's)
hashing routine for encrypting and decrypting a pin
number. Naturally
28 matches
Mail list logo
