[EMAIL PROTECTED] wrote:
Likewise for VM/ESA 3340's, 3370's.
that should be 3310 & 3370s ... 3330, 3340, 3350 were all ckd. 3340s were
removable packs that were totally enclosed including the arm access mechanism.
There was 3375 which basically was (hardware) emulation of CKD on 3370 device.
part of the issue was that cp & cms ... always treated disks as logical FBA ...
even going back to cp40 and cp67 implementations in the mid60s on 2311 and 2314
(ckd) ... and didn't really leverage any ckd features.
the one possible exception was internal modification originally done for the
HONE system. HONE was the world-wide vm370 (originally cp67) based online
service for marketing, sales, and field people. In the mid-70s the various US
HONE datacenters were consolidated in northern cal (and the US HONE system
started being cloned in more and more places around the world). I provided
highly customized kernel for HONE operations for period of 15yrs or so (and
some of my first trips outside the US was personally installing HONE clones in
other parts of the world ... first one was when EMEA hdqtrs moved from US to
Paris). misc. past posts mentioning hone
http://www.garlic.com/~lynn/subtopic.html#hone
the consolidation of some of the HONE vm370 datacenters provided opportunity for development of vm370
"single-system-image" support with front-end load-balancing and availability infrastructure directing branch office logon
to specific processor. The mechanism utilized a special CKD sequence that performed a logical "compare&swap" channel
program to correctly syncronize logins across all processors in the complex. The "compare&swap" channel program had
originally been developed by the people at the Uithorn HONE system in Europe ... for coordinating logins across all processors in
loosely-coupled complex. I believe that JES2 multi-access spool then started using a similar logical "compare&swap"
channel program for its loosely-coupled operation. This was to avoid the heavy penalty and overhead of doing full device
reserve/release sequence.
Later the US hone complex was replicated first in Dallas and then a 3rd in
Boulder (and could
provide geographic availability to US branch offices logins across all three
datacenters).
for other drift ... recent post
http://www.garlic.com/~lynn/2007e.html#16 Attractive Alternatives to Mainframes
mentioning coining "disaster survivability" and "geographic survivability"
http://www.garlic.com/~lynn/subtopic.html#available
when we were doing ha/cmp product
http://www.garlic.com/~lynn/subtopic.html#hacmp
For completely other topic drift ... the 370 "compare&swap" instruction was
originally invented by charlie at the science center
http://www.garlic.com/~lynn/subtopic.html#545tech
as part of his work on fine-grain multiprocessing locking for cp67 kernel (precusor to vm370
developed at the science center). "CAS" was then chosen for the instruction ...
because they are charlie's initials ... and then had to come up with instruction name to go
along with his initials. a couple recent posts on effort to get compare&swap instruction
into 370 architecture.
Then I also started doing a highly customized kernel for the disk development
and product test labs
http://www.garlic.com/~lynn/subtopic.html#disk
related previous posts
http://www.garlic.com/~lynn/2007d.html#48 IBM S/360 series operating systems
history
http://www.garlic.com/~lynn/2007d.html#51 IBM S/360 series operating systems
history
http://www.garlic.com/~lynn/2007d.html#52 CMS (PC Operating Systems)
http://www.garlic.com/~lynn/2007d.html#65 IBM S/360 series operating systems
history
http://www.garlic.com/~lynn/2007d.html#69 IBM S/360 series operating systems
history
http://www.garlic.com/~lynn/2007d.html#72 IBM S/360 series operating systems
history
http://www.garlic.com/~lynn/2007e.html#27 IBM S/360 series operating systems
history
http://www.garlic.com/~lynn/2007e.html#32 I/O in Emulated Mainframes
http://www.garlic.com/~lynn/2007e.html#33 IBM S/360 series operating systems
history
http://www.garlic.com/~lynn/2007e.html#35 FBA rant
for other topic drift:
http://www.garlic.com/~lynn/2001l.html#53 mainframe question
http://www.garlic.com/~lynn/2001l.html#63 MVS History (all parts)
http://www.garlic.com/~lynn/2002o.html#3 PLX
http://www.garlic.com/~lynn/2003b.html#7 Disk drives as commodities. Was Re:
Yamhill
http://www.garlic.com/~lynn/2005t.html#50 non ECC
http://www.garlic.com/~lynn/2006c.html#46 Hercules 3.04 announcement
http://www.garlic.com/~lynn/2006s.html#32 Why magnetic drums was/are worse than
disks ?
http://www.garlic.com/~lynn/2006v.html#31 MB to Cyl Conversion
I'm trying to fill in rest of these code-names:
2301 fixed-head/track (2303 but 4 r/w heads at time)
2303 fixed-head/track r/w 1-head (1/4th rate of 2301)
Corinth 2305-1 fixed-head/track
Zeus 2305-2 fixed-head/track
2311
2314
2321 data-cell "washing machine"
Piccolo 3310 FBA
Merlin 3330-1
Iceberg 3330-11
Winchester 3340-35
3340-70
3344 (3350 physical drive simulating multiple 3340s)
Madrid 3350
NFP 3370 FBA
Florence 3375 3370 supporting CKD
Coronado 3380 A04, AA4, B04
EvergreenD 3380 AD4, BD4
EvergreenE 3380 AE4, BE4
3830 disk controller, horizontal microcode engine
Cybernet 3850 MSS (also Camanche & Oak)
Cutter 3880 disk controller, jib-prime (vertical) mcode engine
Ironwood 3880-11 (4kbyte/page block 8mbyte cache)
Sheriff 3880-13 (full track 8mbyte cache)
Sahara 3880-21 (larger cache for "11")
?? 3880-23 (larger cache for "13")
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
