Article View: alt.folklore.computers
Article #621513Re: Old word processors
From: hanc...
Date: Thu, 29 Mar 2018 23:48
Date: Thu, 29 Mar 2018 23:48
62 lines
5114 bytes
5114 bytes
On Wednesday, March 28, 2018 at 8:09:21 PM UTC-4, Lynn Wheeler wrote: > this was in period (late 70s/early 80s) where 3270 terminals were part > of fall budget cycle and each one required VP-level sign-off. Then there > was a rapidly spreading rumor that some of the corporate executive > committee members were using email ... and all of a sudden every middle > manager in the company had to have 3270 terminal on their desk (even if > they never actually used them, spending the day with the vm370 login > screen or possibly PROFS menu being burned into screen) ... pre-empting > annual 3270 terminal deliveries justified for development projects. When PCs came out, every manager wanted one for the prestige of it, and also wanted the better models (faster chip). The people who actually did work got stuck with the lesser models. So a manager would have a nice AT that never got touched, while the clerk pounding away all day had the XT. As to terminals, I think most places started off with a terminal room where the terminals were shared among a large staff of programmers. Then as the cost dropped, more and more programmers got them. For us, it was in 1989 that finally every programmer got a terminal. One welcome terminal feature (I think provided by the controller) was the ability to get multiple sessions and easily toggle between them. This way a programmer could look at his source code and then the execution on CICS. (Another welcome feature was software that allowed one to step through execution of a CICS program, being able to look at results of each line and of all the fields. We had both the IBM product and the one from an independent vendor.) > other trivia: PROFS group had collecting some number of internal > applications (including telephone books) and wrapping MENUs around > them. They had taken very early version of VMSG for the email > client. When the VMSG tried to offer them a much enhanced version, the > PROFS group attempted to get him fired (since they had already claimed > credit for everyting). Things quieted down when VMSG author > demonstrated that every PROFS email had his initials in non-displayed > field (after that the VMSG author only shared source with me and one > other person). Our corporate phone book was also on PROFS. Most useful. I liked PROFS, and used it until it was unplugged. Others liked the PC email packages. It's sad to read of intra-department squabbles at IBM, but it seems from the IBM Early Computer history that this is nothing new. Back in the early 1950s there was rivalry between the Endicott and Poughkeepsie labs. The S/360 development had a lot of sharp differences of opinion on the direction to go. Some CEO's believe conflict in an organization is healthy and spurs people onward. Watson Jr said in his memoirs that he liked to purposely shake things up in the company. Personally, I think a company functions better as a united team and conflicting are best worked out at a low level when possible.
Technical Details
Message-ID:
<5f2fc0d2-b4a0-4dd1-82e9-80553292a36f@googlegroups.com>Path:
mbox-mo1.pugleaf.net!c39ni707qta.0!nntp.google.com!j29no585986qtc.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mailReferences:
<87k1ub4vgf.fsf@usenet.ankman.de> <396ec331-b5a3-4137-ac0f-c45471afccb7@googlegroups.com> <87fu4y4d8m.fsf@usenet.ankman.de> <p8l274$r1u$1@dont-email.me> <XnsA8A98D082B822admin127001@85.214.115.223> <p8matd$94n$1@dont-email.me> <eff02c9e-2715-42e2-bca8-b3165b0b6426@googlegroups.com> <797bbd92d9i308or8op7ig56h12t7499lt@4ax.com> <bfahoe-anh.ln1@Telcontar.valinor> <e1gcbdphsj192r12m6non65sangfoboq74@4ax.com> <d4ednZtjc4sdOivHnZ2dnUU78eXNnZ2d@giganews.com> <p96q0e$eh4$1@dont-email.me> <cc470d3d-08f3-4629-821d-9589941dc1a4@googlegroups.com> <87woxywsdv.fsf@garlic.com> <502a8c0c-b45e-43ae-a464-3060d0ab699d@googlegroups.com> <p9cc9i01jmq@news1.newsguy.com> <p9cj6a$lf6$1@dont-email.me> <c20015d0-118b-4a14-855b-bfbfc5d00d81@googlegroups.com> <87lgebivyq.fsf@garlic.com>Show Full Headers
Complete Article Headers
X-Received: by 10.200.19.69 with SMTP id f5mr31431534qtj.23.1522367288557; Thu, 29 Mar 2018 16:48:08 -0700 (PDT) X-BeenThere: alt.folklore.computers@googlegroups.com Received: by 10.200.38.97 with SMTP id v30ls4727065qtv.4.gmail; Thu, 29 Mar 2018 16:48:07 -0700 (PDT) X-Received: by 10.200.52.46 with SMTP id u43mr35652173qtb.15.1522367287765; Thu, 29 Mar 2018 16:48:07 -0700 (PDT) X-Received: by 10.31.140.138 with SMTP id o132mr2135854vkd.8.1522367287460; Thu, 29 Mar 2018 16:48:07 -0700 (PDT) Path: mbox-mo1.pugleaf.net!c39ni707qta.0!nntp.google.com!j29no585986qtc.0!postnews.google.com!glegroupsg2000goo.googlegroups.com!not-for-mail Newsgroups: alt.folklore.computers Date: Thu, 29 Mar 2018 16:48:07 -0700 (PDT) In-Reply-To: <87lgebivyq.fsf@garlic.com> Complaints-To: groups...@google.com Injection-Info: glegroupsg2000goo.googlegroups.com; posting-host=8.41.192.198; posting-account=WKyNOQkAAACNglsCZiIox1kdy9R-66KH NNTP-Posting-Host: 8.41.192.198 References: <87k1ub4vgf.fsf@usenet.ankman.de> <396ec331-b5a3-4137-ac0f-c45471afccb7@googlegroups.com> <87fu4y4d8m.fsf@usenet.ankman.de> <p8l274$r1u$1@dont-email.me> <XnsA8A98D082B822admin127001@85.214.115.223> <p8matd$94n$1@dont-email.me> <eff02c9e-2715-42e2-bca8-b3165b0b6426@googlegroups.com> <797bbd92d9i308or8op7ig56h12t7499lt@4ax.com> <bfahoe-anh.ln1@Telcontar.valinor> <e1gcbdphsj192r12m6non65sangfoboq74@4ax.com> <d4ednZtjc4sdOivHnZ2dnUU78eXNnZ2d@giganews.com> <p96q0e$eh4$1@dont-email.me> <cc470d3d-08f3-4629-821d-9589941dc1a4@googlegroups.com> <87woxywsdv.fsf@garlic.com> <502a8c0c-b45e-43ae-a464-3060d0ab699d@googlegroups.com> <p9cc9i01jmq@news1.newsguy.com> <p9cj6a$lf6$1@dont-email.me> <c20015d0-118b-4a14-855b-bfbfc5d00d81@googlegroups.com> <87lgebivyq.fsf@garlic.com> User-Agent: G2/1.0 MIME-Version: 1.0 Message-ID: <5f2fc0d2-b4a0-4dd1-82e9-80553292a36f@googlegroups.com> Subject: Re: Old word processors From: hanc...@bbs.cpcn.com Injection-Date: Thu, 29 Mar 2018 23:48:07 +0000 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit