Article View: alt.folklore.computers
Article #621445Re: Old word processors
From: Dan Espen
Date: Sat, 24 Mar 2018 22:44
Date: Sat, 24 Mar 2018 22:44
47 lines
3430 bytes
3430 bytes
hanc...@bbs.cpcn.com writes: > On Monday, March 19, 2018 at 7:09:04 PM UTC-4, Dan Espen wrote: > >> Wang VS was a great system. >> The OS was nothing like anything from IBM. >> I was working on it for a while before I stumbled onto one of the >> Wang's IBM-isms. Even then, a little of IBM, a lot of great Wang stuff. >> >> So, I'm editing a COBOL program and the editor allows me to run >> a test. I think I've submitted a job and that's it, but a message >> comes back to my screen telling me I have a S0C7 (IBM speak for invalid >> data). Unlike anything from IBM, >> it shows me the send and receive fields and their contents. >> Also, it lets me type new data into either or both fields. Or it offers >> to take me to the offending line in the COBOL program. >> >> Of course all you get from IBM, is watch the job until it ends, then >> read a huge dump. >> Using Wang VS made it so clear how bad IBM software was. > > The latest IBM mainframe COBOL has improved somewhat on debugging > aids in case of an abend. Last time I checked, still quite cumbersome to use. Wang VS presented a unified system. At the time I was using my own editor so it tried to return me to their editor. I did a little checking and found out what I needed to get the same stuff to work with the editor I wrote. >> The Wang hardware was a bit different too. >> Their systems spanned a huge range of power. >> The VS 5 was a $12,000 system. Way lower priced >> than anything in the IBM mainframe lineup. >> When I connected from home using a Wang terminal the OS >> loaded a micro-program into my terminal. I think it did that >> with all it's peripherals. Seemed like a good idea to me. >> The host really did control it's devices. > > What happened to the Wang Company? PCs. -- Dan Espen
Technical Details
Message-ID:
<p96kcq$9lg$1@dont-email.me>Path:
mbox-mo1.pugleaf.net!n24ni13633wmi.0!nntp.google.com!goblin3!goblin2!goblin.stu.neva.ru!aioe.org!eternal-september.org!feeder.eternal-september.org!reader02.eternal-september.org!.POSTED!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> <87r2oh9q5a.fsf@garlic.com> <0b3f83bf-08c5-4ebe-a399-a304bfb68d23@googlegroups.com> <p8pfuf$7am$1@dont-email.me> <e1b101c1-3924-4c64-87c1-401384ab29fc@googlegroups.com>Show Full Headers
Complete Article Headers
X-Received: by 10.28.207.134 with SMTP id f128mr1330630wmg.11.1521931483917; Sat, 24 Mar 2018 15:44:43 -0700 (PDT) X-BeenThere: alt.folklore.computers@googlegroups.com Received: by 10.28.71.29 with SMTP id u29ls892372wma.5.gmail; Sat, 24 Mar 2018 15:44:43 -0700 (PDT) X-Received: by 10.28.184.143 with SMTP id i137mr1569578wmf.7.1521931483156; Sat, 24 Mar 2018 15:44:43 -0700 (PDT) Path: mbox-mo1.pugleaf.net!n24ni13633wmi.0!nntp.google.com!goblin3!goblin2!goblin.stu.neva.ru!aioe.org!eternal-september.org!feeder.eternal-september.org!reader02.eternal-september.org!.POSTED!not-for-mail From: Dan Espen <dan1...@gmail.com> Newsgroups: alt.folklore.computers Subject: Re: Old word processors Date: Sat, 24 Mar 2018 18:44:42 -0400 Organization: A noiseless patient Spider Lines: 47 Message-ID: <p96kcq$9lg$1@dont-email.me> References: <87k1ub4vgf.fsf@usenet.ankman.de> <396ec331-b5a3-4137-ac0f-c45471afccb7@googlegroups.com> <87fu4y4d8m.fsf@usenet.ankman.de> <p8l274$r1u$1@dont-email.me> <87r2oh9q5a.fsf@garlic.com> <0b3f83bf-08c5-4ebe-a399-a304bfb68d23@googlegroups.com> <p8pfuf$7am$1@dont-email.me> <e1b101c1-3924-4c64-87c1-401384ab29fc@googlegroups.com> Mime-Version: 1.0 Injection-Info: reader02.eternal-september.org; posting-host="ea4dbb30f7f6e4cf3be200e9dde9b3a5"; logging-data="9904"; mail-complaints-to="ab...@eternal-september.org"; posting-account="U2FsdGVkX18J5tCDeuCTRfIu/5vK7ZOE3s8ouu5+c88=" User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.3 (gnu/linux) Cancel-Lock: sha1:Fh2rpq6mc/Ip+dL5LSJ7MbPsESw= Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 7bit