The following message is a courtesy copy of an article that has been posted to alt.folklore.computers as well.
[EMAIL PROTECTED] (Steve Samson) writes: > As for 32-bit mode (TSS) I don't have a POPS for that architecture but > I suspect the HO bit is treated as any other. TSS did not use the > "sign bit" as a signal, just as an address bit. lots of 360 documents at bitsavers: http://bitsavers.org/pdf/ibm/360/ including various functional characteristics http://bitsavers.org/pdf/ibm/360/funcChar/ specifically 360/67 functional characteristics a27-2719-0 http://bitsavers.org/pdf/ibm/360/funcChar/A27-2719-0_360-67_funcChar.pdf and ga27-2719-2 http://bitsavers.org/pdf/ibm/360/funcChar/GA27-2719-2_360-67_funcChar.pdf which has a lot of the gory details. as somewhat referenced here ... 360/67 was originally intended for use by tss/360 ... but for a whole variety of reasons, most of them ran cp67 (or in straight 360/65 mode with mvt w/o using virtual memory hardware) http://www.garlic.com/~lynn/2007r.html#64 CSA 'above the bar' curtesy of science center http://www.garlic.com/~lynn/subtopic.html#545tech in any case, psw format, pg. 15 bit meaning 0-3 spare (must be 0) 4 24-32 bit address mode 5 translation control 6 i/o mask (summary) 7 external mask (summary) 8-11 protection key 12 ascii-8 mode 13 machine check mask 14 wait state 15 problem state 16-17 instruction length code 18-19 condition code 20-23 program mask 24-31 spare 32-63 instruction address ... there were a quite a few of the machines used internally. one of the projects were adding 370 "virtual machine" option to cp67 simulation ... this was having cp67 simulate the new instructions added to 370 (prior to announcement of 370 virtual memory). one of the places that deployed numerous of these machines was in the field/data processing/sales division for a project called HONE http://www.garlic.com/~lynn/subtopic.html#hone for hands-on network environment ... the idea was that in the wake of 23jun69 unbundling announcement http://www.garlic.com/~lynn/subtopic.html#unbundle that SEs in the branch office could get operating system "hands-on" experience with (370) systems running in cp67 (370) virtual machines. however, the science center had also ported apl\360 to cms for cms\apl and done a lot of work enhancing it to operate in "large" virtual memory environment (most apl\360 was limited to 16k workspaces, hardly adequate for many real world problems). With cms\apl, there were lots of new (internal) apl-based applications developed (some number of them of the genre that today would be done with spreadsheets) ... including "configurators" ... which basically filled out mainframe system orders for the branch office personal. As the use of these applications grew on HONE ... eventually they eclipsed the virtual guest "hands-on" training and would consume all available resources. at some point in the 70s, it was not even possible to submit a mainframe order that hadn't been run thru HONE configurator. science center had also done quite a bit of work in the area of sophisticated system performance modeling ... including laying the groundwork for what would become capacity planning. some of this i've commented about with regard to calibrating and validating http://www.garlic.com/~lynn/subtopic.html#benchmark the release of my resource manager http://www.garlic.com/~lynn/subtopic.html#fairshare in addition, a flavor of the performance modeling work was also deployed on HONE as the (apl based) "performance predictor". Branch office people could submit customer configuration and workload details/characteristics and then ask "what-if" questions of the "performance predictor" ... as to what would happen if there was configuration and/or workload changes. another project was doing the cp67 changes to support a full 370 virtual memory implementation. this had a version cp67 running either in a 360/67 virtual machine (under cp67) or stand-alone real 360/67 simulating virtual machine with full 370 virtual memory operation. Then there was a custom version of cp67 that believed it ran on 370 virtual memory "hardware" (rather than on 360/67 hardware). This was in regular production use a year before the first engineering 370 machine with virtual memory support was operational (and long before announcement). past posts in the related thread: http://www.garlic.com/~lynn/2007r.html#56 CSA 'above the bar' http://www.garlic.com/~lynn/2007r.html#62 CSA 'above the bar' http://www.garlic.com/~lynn/2007r.html#64 CSA 'above the bar' http://www.garlic.com/~lynn/2007r.html#65 CSA 'above the bar' http://www.garlic.com/~lynn/2007r.html#67 CSA 'above the bar' misc. past posts mentioning "performance predictor" http://www.garlic.com/~lynn/2001i.html#46 Withdrawal Announcement 901-218 - No More 'small machines' http://www.garlic.com/~lynn/2002b.html#64 ... the need for a Museum of Computer Software http://www.garlic.com/~lynn/2002c.html#45 cp/67 addenda (cross-post warning) http://www.garlic.com/~lynn/2002q.html#28 Origin of XAUTOLOG (x-post) http://www.garlic.com/~lynn/2003g.html#15 Disk capacity and backup solutions http://www.garlic.com/~lynn/2003p.html#29 Sun researchers: Computers do bad math ;) http://www.garlic.com/~lynn/2004g.html#42 command line switches [Re: [REALLY OT!] Overuse of symbolic constants] http://www.garlic.com/~lynn/2004k.html#31 capacity planning: art, science or magic? http://www.garlic.com/~lynn/2004o.html#10 Multi-processor timing issue http://www.garlic.com/~lynn/2005d.html#1 Self restarting property of RTOS-How it works? http://www.garlic.com/~lynn/2005d.html#6 [Lit.] Buffer overruns http://www.garlic.com/~lynn/2005d.html#33 Thou shalt have no other gods before the ANSI C standard http://www.garlic.com/~lynn/2005d.html#48 Secure design http://www.garlic.com/~lynn/2005h.html#1 Single System Image questions http://www.garlic.com/~lynn/2005h.html#15 Exceptions at basic block boundaries http://www.garlic.com/~lynn/2005j.html#12 Performance and Capacity Planning http://www.garlic.com/~lynn/2005k.html#17 More on garbage collection http://www.garlic.com/~lynn/2005o.html#30 auto reIPL http://www.garlic.com/~lynn/2005o.html#34 Not enough parallelism in programming http://www.garlic.com/~lynn/2006b.html#15 {SPAM?} Re: Expanded Storage http://www.garlic.com/~lynn/2006b.html#17 {SPAM?} Re: Expanded Storage http://www.garlic.com/~lynn/2006f.html#22 A very basic question http://www.garlic.com/~lynn/2006f.html#30 A very basic question http://www.garlic.com/~lynn/2006g.html#34 The Pankian Metaphor http://www.garlic.com/~lynn/2006h.html#25 The Pankian Metaphor http://www.garlic.com/~lynn/2006l.html#3 virtual memory http://www.garlic.com/~lynn/2006o.html#23 Strobe equivalents http://www.garlic.com/~lynn/2006o.html#25 CPU usage for paging http://www.garlic.com/~lynn/2006s.html#24 Curiousity: CPU % for COBOL program http://www.garlic.com/~lynn/2006t.html#28 Why these original FORTRAN quirks? http://www.garlic.com/~lynn/2007k.html#65 Non-Standard Mainframe Language? misc. past posts discussing internal cp67 versions that supported 370 virtual machines and/or ran on 370 (as opposed to running on 360/67) http://www.garlic.com/~lynn/2002j.html#0 HONE was .. Hercules and System/390 - do we need it? http://www.garlic.com/~lynn/2004b.html#31 determining memory size http://www.garlic.com/~lynn/2004h.html#27 Vintage computers are better than modern crap ! http://www.garlic.com/~lynn/2004p.html#50 IBM 3614 and 3624 ATM's http://www.garlic.com/~lynn/2005c.html#59 intel's Vanderpool and virtualization in general http://www.garlic.com/~lynn/2005d.html#66 Virtual Machine Hardware http://www.garlic.com/~lynn/2005g.html#17 DOS/360: Forty years http://www.garlic.com/~lynn/2005h.html#18 Exceptions at basic block boundaries http://www.garlic.com/~lynn/2005j.html#50 virtual 360/67 support in cp67 http://www.garlic.com/~lynn/2005p.html#27 What ever happened to Tandem and NonStop OS ? http://www.garlic.com/~lynn/2006.html#38 Is VIO mandatory? http://www.garlic.com/~lynn/2006e.html#7 About TLB in lower-level caches http://www.garlic.com/~lynn/2006f.html#5 3380-3390 Conversion - DISAPPOINTMENT http://www.garlic.com/~lynn/2006l.html#21 Virtual Virtualizers http://www.garlic.com/~lynn/2006m.html#26 Mainframe Limericks http://www.garlic.com/~lynn/2006o.html#19 Source maintenance was Re: SEQUENCE NUMBERS http://www.garlic.com/~lynn/2006q.html#1 Materiel and graft http://www.garlic.com/~lynn/2006q.html#45 Was FORTRAN buggy? http://www.garlic.com/~lynn/2006q.html#49 Was FORTRAN buggy? http://www.garlic.com/~lynn/2006w.html#3 IBM sues maker of Intel-based Mainframe clones http://www.garlic.com/~lynn/2007b.html#20 How many 36-bit Unix ports in the old days? http://www.garlic.com/~lynn/2007f.html#12 FBA rant http://www.garlic.com/~lynn/2007i.html#16 when was MMU virtualization first considered practical? http://www.garlic.com/~lynn/2007p.html#74 GETMAIN/FREEMAIN and virtual storage backing up http://www.garlic.com/~lynn/2007q.html#23 GETMAIN/FREEMAIN and virtual storage backing up ---------------------------------------------------------------------- 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
