[OT ] Mainframe memories

Cross-posted to IBM-VM, IBM-MAIN and LINUX-390 To commemorate the 50th anniversary of S/360 I wrote a blog that many of you may have seen already but just in case you missed it: http://butmostlyaboutcats.blogspot.com/2014/03/mainframe-memories.html Neale ---

Re: [OT ] Mainframe memories

> To commemorate the 50th anniversary of S/360 I wrote a blog that many of you > may have seen already but just in case you missed it: > > http://butmostlyaboutcats.blogspot.com/2014/03/mainframe-memories.html Very nice, thank you. One thing I noted was the bit about the colors - how each upgrad

Re: [OT ] Mainframe memories

u could use the /*ROUTE JCL card to actually state which colour  you wanted the job to run on - -teD -   Original Message   From: William Donzelli Sent: Thursday, March 6, 2014 23:12 To: IBM-MAIN@LISTSERV.UA.EDU Reply To: IBM Mainframe Discussion List Subject: Re: [OT ] Mainframe memories > To co

Re: [OT ] Mainframe memories

scussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Ted MacNEIL Sent: Friday, March 07, 2014 1:04 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [OT ] Mainframe memories When I worked for the Ontario government in the early 1980's, we had four 3033's all named after the original colours tha

Re: [OT ] Mainframe memories

" stories? > > Al Nims > Systems Admin/Programmer 3 > Information Technology > University of Florida > (352) 273-1298 > > -Original Message- > From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On > Behalf Of Ted MacNEIL > Sent: Friday, March

Re: [OT ] Mainframe memories

@LISTSERV.UA.EDU Subject: Re: [OT ] Mainframe memories A nit: VM/370. Was no VM/360. On Fri, Mar 7, 2014 at 2:56 PM, Nims,Alva John (Al) wrote: > One of my memories is that for short period of time I worked for the > administration group at my university, which at the time used a IBM

Re: [OT ] Mainframe memories

>Anyone have 360 "Emergency Pull" stories? This is secondhand, but I heard of operators playing Frisbee in the machine room and-yeah, emergency PUSH button, no guard. I've used that story to explain to people why there's a guard over it. I also heard of a manager being in the computer room when

Re: [OT ] Mainframe memories

om -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Phil Smith Sent: Friday, March 07, 2014 3:31 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [OT ] Mainframe memories >Anyone have 360 "Emergency Pull" stories? ___

Re: [OT ] Mainframe memories

E: cblaic...@syncsort.com -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Phil Smith Sent: Friday, March 07, 2014 3:31 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [OT ] Mainframe memories Anyone have 360

Re: [OT ] Mainframe memories

, Date: 03/07/2014 12:34 PM Subject:Re: [OT ] Mainframe memories Sent by:IBM Mainframe Discussion List >Anyone have 360 "Emergency Pull" stories? This is secondhand, but I heard of operators playing Frisbee in the machine room and-yeah, emergency PUSH button, no gua

Re: [OT ] Mainframe memories

> One of the operators came in and set her purse on the table by the keyboard. > Sure enough, it tipped over and started an IPL Interesting. We had an operator who dropped a book on it. Same result. Bob Shannon Rocket Software

Re: [OT ] Mainframe memories

I am sure everyone remembers raised tiles, right? Well our cleaning people started to use some cleaning solution that weakened the tile on the raised floor. This caused people to stumble on these. One Sunday morning we came in to test and found that "someone" (it turned out to be a disk C

Re: [OT ] Mainframe memories

@LISTSERV.UA.EDU Subject: Re: [OT ] Mainframe memories >Anyone have 360 "Emergency Pull" stories? ATTENTION: - The information contained in this message (including any files transmitted with this message) may contain proprietary, trade secret or other conf

Re: [OT ] Mainframe memories

going fast enough. -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Gary Jacek Sent: Friday, March 07, 2014 3:12 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [OT ] Mainframe memories At a former employer, we had a red master EPO switch

Re: [OT ] Mainframe memories

ibm science center was on part of the 4th flr of 545 tech sq ... some past posts http://www.garlic.com/~lynn/subtopic.html#545tech but the machine room occupied part of the 2nd flr. it had duplex (two processor) 360/67, 768kbytes memory, three 2301 "drums", five 8+1 drive 2314 string plus one 5 dr

Re: [OT ] Mainframe memories

My two favorite memories are: 1 - I got called at 0230 because first the system crashed for no apparent reason, then when they went to IPL, it failed to. So I drive into work, go to the machine room, and as I am trying to figure out what is going on, I notice some tape rings on the floor. So I do

Re: [OT ] Mainframe memories

Wayne -- did you ever find out where the tape rings came from, and who'd munged the Write Inhibit switches? On Fri, Mar 7, 2014 at 10:10 PM, Wayne Driscoll wrote: > My two favorite memories are: > 1 - I got called at 0230 because first the system crashed for no apparent > reason, then when they

Re: [OT ] Mainframe memories

Guys, I started in Computer Operations, we were running on. 370/135 running DOS/VS/POWER and we had removal 2319 disk drives. I heard a notice told my Operations manager and at the same time we had DOS/VS message saying we had a equipment check on that drive, so my boss removed that disk pack an

Re: [OT ] Mainframe memories

My memory was about an incident that occurred at an installation that I worked at. Their DASD were 2314s (which were 9 drive units - 8 live and one spare). The address of the drives were controlled by a round plug that could be removed and placed in the address hole of another drive. There were

Re: [OT ] Mainframe memories

My most amusing memory of working on Big Blue Iron happened in '71 or '72. At that time Penn State was replacing a 360/50 with a 370/165. The day the 360/50 was being removed from the machine room floor, someone printed up a very nice sign and posted it to the inside door of the freight elevator.

Re: [OT ] Mainframe memories

Saturday, March 08, 2014 2:51 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [OT ] Mainframe memories My memory was about an incident that occurred at an installation that I worked at. Their DASD were 2314s (which were 9 drive units - 8 live and one spare). The address of the drives were controlled b

Re: [OT ] Mainframe memories

Many years ago I was hired by a large bank as a business analyst. I'd worked in a branch of the bank, but I knew nothing about computers. My boss figured I needed to know some basic computer concepts to deal with programmers, so he gave me a COBOL manual to read. When I got to chapter 3, it gave

Re: [OT ] Mainframe memories

In <68b5f70ac126ab4dad0e627d782a606a38f...@ufexch-mbxn01.ad.ufl.edu>, on 03/07/2014 at 07:56 PM, "Nims,Alva John (Al)" said: >IBM 4341 running VM/360 No such animal; there was a CP-67 for the S/360, but VM was strictly for the S/370 and its name reflected that. -- Shmuel (Seymour J.)

Re: [OT ] Mainframe memories

In , on 03/07/2014 at 08:50 PM, "Blaicher, Christopher Y." said: >When working for a third party disk vendor I was in a computer room >and there was an IBM CE working on a 360/45. No such animal; I might believe 360/40 or 370/145. -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO

Re: [OT ] Mainframe memories

shmuel+ibm-m...@patriot.net (Shmuel Metz , Seymour J.) writes: > No such animal; there was a CP-67 for the S/360, but VM was strictly > for the S/370 and its name reflected that. re: http://www.garlic.com/~lynn/2014d.html#16 [OT ] Mainframe memories almost. one of the earliest uses

Re: [OT ] Mainframe memories

[mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Shmuel Metz (Seymour J.) Sent: Saturday, March 08, 2014 7:54 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [OT ] Mainframe memories In , on 03/07/2014 at 08:50 PM, "Blaicher, Christopher Y." said: >When working for a third party disk

Re: [OT ] Mainframe memories

On 03/08/2014 06:43 PM, Shmuel Metz (Seymour J.) wrote: > In <68b5f70ac126ab4dad0e627d782a606a38f...@ufexch-mbxn01.ad.ufl.edu>, > on 03/07/2014 >at 07:56 PM, "Nims,Alva John (Al)" said: > >> IBM 4341 running VM/360 > No such animal; there was a CP-67 for the S/360, but VM was strictly > for th

Re: [OT ] Mainframe memories

At 19:54 -0500 on 03/08/2014, Shmuel Metz (Seymour J.) wrote about Re: [OT ] Mainframe memories: In , on 03/07/2014 at 08:50 PM, "Blaicher, Christopher Y." said: When working for a third party disk vendor I was in a computer room and there was an IBM CE working on a 360/45.

Re: [OT ] Mainframe memories

At 15:13 -0600 on 03/08/2014, Barry Merrill wrote about Re: [OT ] Mainframe memories: In 1972, the Corporation's Annual P&L job read multiple tape reels from each of the 26 regional offices, so 26 tape drives were allocated to the job, which took over 40 hours across a dedicated wee

Re: [OT ] Mainframe memories

Metavance safe for all HUMANAty -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Blaicher, Christopher Y. Sent: Saturday, March 08, 2014 10:33 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [IBM-MAIN] [OT ] Mainframe memories Right you are

Re: [OT ] Mainframe memories

retroactively think of CP-40 or CP-67 as equivalent to > a "VM/360", since both required more than basic S/360 architecture. re: http://www.garlic.com/~lynn/2014d.html#16 [OT ] Mainframe memories http://www.garlic.com/~lynn/2014d.html#22 [OT ] Mainframe memories Bob Creasy (manager

Re: [OT ] Mainframe memories

the machine as 360/65 with os/360. > http://en.wikipedia.org/wiki/TSS/360 re: http://www.garlic.com/~lynn/2014d.html#16 [OT ] Mainframe memories http://www.garlic.com/~lynn/2014d.html#22 [OT ] Mainframe memories http://www.garlic.com/~lynn/2014d.html#23 [OT ] Mainframe memories as undergraduate

Re: [OT ] Mainframe memories

l...@garlic.com (Anne & Lynn Wheeler) wrote: one of the things that I did have lots of problems with was supporting position independent code (mentioned in the tss/360 wiki article) ...constantly having to hack code to make in position independent Is 'position independent' code the same as loca

Re: [OT ] Mainframe memories

re: http://www.garlic.com/~lynn/2014d.html#16 [OT ] Mainframe memories http://www.garlic.com/~lynn/2014d.html#22 [OT ] Mainframe memories http://www.garlic.com/~lynn/2014d.html#23 [OT ] Mainframe memorie http://www.garlic.com/~lynn/2014d.html#25 [OT ] Mainframe memorie univ ran fortran student

Re: [OT ] Mainframe memories

ith no fondness a 60-year-old pseudo-random number generator > that was location-dependent.) re: http://www.garlic.com/~lynn/2014d.html#25 [OT ] Mainframe memories I've used position & location independence somewhat interchangeably. In my use for cp67/cms page mapped filesystem and i

Re: [OT ] Mainframe memories

Was the smoke black or white? -Original Message- From: IBM Mainframe Discussion List [mailto:IBM-MAIN@LISTSERV.UA.EDU] On Behalf Of Chris Hoelscher Sent: Sunday, March 09, 2014 9:48 AM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [OT ] Mainframe memories Maybe IBM elected a new chairman

Re: [OT ] Mainframe memories

In <531be625.2040...@acm.org>, on 03/08/2014 at 09:55 PM, "Joel C. Ewing" said: >I believe the CP-40 and CP-67 precursors of VM/370 required more than >just S/360 architecture; For CP-40 the extension was nonstandard, but for CP-67 the extension was part of a standard 360/67, even though it w

Re: [OT ] Mainframe memories

In <531be625.2040...@acm.org>, on 03/08/2014 at 09:55 PM, "Joel C. Ewing" said: >I remember an IBM 3033 putting out a puff of smoke once, Much earlier, someone decided that the power unit for the 650 was of a convenient height for drying socks. A Selenium rectifier blew out. Coincidence? --

Re: [OT ] Mainframe memories

On 9 March 2014 09:01, Shmuel Metz (Seymour J.) wrote: > Much earlier, someone decided that the power unit for the 650 was of a > convenient height for drying socks. A Selenium rectifier blew out. Not a pleasant smell (the rectifier; no comment on the socks), as anyone who's been near a cooked on

Re: [OT ] Mainframe memories

In , on 03/09/2014 at 03:47 PM, Anne & Lynn Wheeler said: >... the executable image on disk could be directly mapped to any >address in memory w/o any further alterations or changes. You don't consider a PSECT to be part of the image? -- Shmuel (Seymour J.) Metz, SysProg and JOAT

Re: [OT ] Mainframe memories

shmuel+ibm-m...@patriot.net (Shmuel Metz , Seymour J.) writes: > You don't consider a PSECT to be part of the image? re: http://www.garlic.com/~lynn/2014d.html#25 Mainframe memories http://www.garlic.com/~lynn/2014d.html#27 Mainframe memories the paradigm allowed the same executable image part c

Re: [OT ] Mainframe memories

On 10 March 2014 10:57, Anne & Lynn Wheeler wrote: > I would tend to use the distinction that for the psect, a private copy > was loaded and adjusted for the specific virtual address space location > ... separately from (r/o) memory mapping the executable image with no > requirement for pre-loadin

Re: [OT ] Mainframe memories

ick was that these tasks were never > preempted, so it was permissible to have a register containing an > address within the module, as long as it was made relative before > (loosely) calling the dispatcher, which might result in relocation. re: http://www.garlic.com/~lynn/2014d.html#25 [OT

Re: [OT ] Mainframe memories

Guess the naming gnomes were trying to subliminally suggest it had no SS instructions. In a message dated 3/10/2014 1:56:17 P.M. Central Daylight Time, et...@tulsagrammer.com writes: IBM System/360 Model 44, optimized for scientific work

Re: [OT ] Mainframe memories

On 3/8/14, 6:49 PM, Shmuel Metz , Seymour J. wrote: In , on 03/07/2014 at 08:50 PM, "Blaicher, Christopher Y." said: When working for a third party disk vendor I was in a computer room and there was an IBM CE working on a 360/45. No such animal; I might believe 360/40 or 370/145. But t

Re: [OT ] Mainframe memories

A.EDU] On Behalf Of Eric Chevalier Sent: Monday, March 10, 2014 1:56 PM To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [OT ] Mainframe memories On 3/8/14, 6:49 PM, Shmuel Metz , Seymour J. wrote: > In > om>, > on 03/07/2014 > at 08:50 PM, "Blaicher, Christopher Y." >

Re: [OT ] Mainframe memories

Now that's something to be proud of, and funny too! Richard and Vickie Pinion --- ba...@mxg.com wrote: From: Barry Merrill To: IBM-MAIN@LISTSERV.UA.EDU Subject: Re: [OT ] Mainframe memories Date: Mon, 10 Mar 2014 14:09:58 -0500 In 1966 we got 360/44 Serial 2 a

Re: [OT ] Mainframe memories

In , on 03/10/2014 at 01:33 PM, Anne & Lynn Wheeler said: >2714 2741? -- Shmuel (Seymour J.) Metz, SysProg and JOAT ISO position; see We don't care. We don't have to care, we're Congress. (S877: The Shut up and Eat Your spam act of

Write Inhibit (Was: Re: [OT ] Mainframe memories)

On 3/7/2014 7:10 PM, Wayne Driscoll wrote: ... 3 of the drives had the Write Inhibit switch in the wrong position. There should still be write inhibit "switch" for a volume, even if only a logical one. It can be very useful, when running under z/VM, to be able to define some z/OS volumes as r

Re: Write Inhibit (Was: Re: [OT ] Mainframe memories)

On Fri, 7 Mar 2014 22:47:26 -0800, Ed Jaffe wrote: >There should still be write inhibit "switch" for a volume, even if only >a logical one. It can be very useful, when running under z/VM, to be >able to define some z/OS volumes as read-only. It would be nice if you >could do something similar in a

Re: Write Inhibit (Was: Re: [OT ] Mainframe memories)

>There should still be write inhibit "switch" for a volume, even if only a >logical one. It can be very useful, when running under z/VM, to be able to >define some z/OS volumes as read-only. It would be nice if you could do >something similar in a z/OS LPAR. Amen. We could really use this featu

Re: Write Inhibit (Was: Re: [OT ] Mainframe memories)

On 3/8/2014 4:36 AM, Bob Shannon wrote: There should still be write inhibit "switch" for a volume, even if only a logical one. It can be very useful, when running under z/VM, to be able to define some z/OS volumes as read-only. It would be nice if you could do something similar in a z/OS LPAR.

Re: Write Inhibit (Was: Re: [OT ] Mainframe memories)

> >There should still be write inhibit "switch" for a volume, even if > only a logical one. It can be very useful, when running under z/VM, > to be able to define some z/OS volumes as read-only. It would be > nice if you could do something similar in a z/OS LPAR. > > Amen. We could really use t