From mboxrd@z Thu Jan 1 00:00:00 1970 X-Spam-Checker-Version: SpamAssassin 3.4.4 (2020-01-24) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.0 required=5.0 tests=MAILING_LIST_MULTI, T_SCC_BODY_TEXT_LINE autolearn=ham autolearn_force=no version=3.4.4 Received: (qmail 31692 invoked from network); 28 Jul 2023 03:38:32 -0000 Received: from minnie.tuhs.org (2600:3c01:e000:146::1) by inbox.vuxu.org with ESMTPUTF8; 28 Jul 2023 03:38:32 -0000 Received: from minnie.tuhs.org (localhost [IPv6:::1]) by minnie.tuhs.org (Postfix) with ESMTP id F134D40EFE; Fri, 28 Jul 2023 13:38:29 +1000 (AEST) Received: from lax.lemis.com (www.lemis.com [45.32.70.18]) by minnie.tuhs.org (Postfix) with ESMTP id 10A3D40BD1 for ; Fri, 28 Jul 2023 13:38:20 +1000 (AEST) Received: from eureka.lemis.com (121-200-11-253.79c80b.mel.nbn.aussiebb.net [121.200.11.253]) by lax.lemis.com (Postfix) with ESMTP id 7B866280BF; Fri, 28 Jul 2023 03:38:19 +0000 (UTC) Received: by eureka.lemis.com (Postfix, from userid 1004) id C14A22635C7; Fri, 28 Jul 2023 13:38:18 +1000 (AEST) Date: Fri, 28 Jul 2023 13:38:18 +1000 From: Greg 'groggy' Lehey To: Paul Winalski Message-ID: <20230728033818.GG92211@eureka.lemis.com> References: <20230727191643.AE34718C079@mercury.lcs.mit.edu> MIME-Version: 1.0 Content-Type: multipart/signed; micalg=pgp-sha1; protocol="application/pgp-signature"; boundary="Sw7tCqrGA+HQ0/zt" Content-Disposition: inline In-Reply-To: Organization: LEMIS, 29 Stones Road, Dereel, VIC, Australia Phone: +61-3-5309-0418 Mobile: +61-490-494-038. Use only as instructed. WWW-Home-Page: http://www.lemis.com/grog X-PGP-Fingerprint: 9A1B 8202 BCCE B846 F92F 09AC 22E6 F290 507A 4223 User-Agent: Mutt/1.6.1 (2016-04-27) Message-ID-Hash: SP7VKSSZVMHT6RMV4B6R7ZANBKKFZLKV X-Message-ID-Hash: SP7VKSSZVMHT6RMV4B6R7ZANBKKFZLKV X-MailFrom: grog@lemis.com X-Mailman-Rule-Misses: dmarc-mitigation; no-senders; approved; emergency; loop; banned-address; member-moderation; nonmember-moderation; administrivia; implicit-dest; max-recipients; max-size; news-moderation; no-subject; digests; suspicious-header CC: COFF X-Mailman-Version: 3.3.6b1 Precedence: list Subject: [COFF] Re: What Happened to Interdata? List-Id: Computer Old Farts Forum Archived-At: List-Archive: List-Help: List-Owner: List-Post: List-Subscribe: List-Unsubscribe: --Sw7tCqrGA+HQ0/zt Content-Type: text/plain; charset=us-ascii Content-Disposition: inline On Thursday, 27 July 2023 at 16:33:54 -0400, Paul Winalski wrote: > On 7/27/23, Noel Chiappa wrote: > >> Someone who's familiar with the 360 instruction set should be able to look >> at e.g.: >> >> and see how compatible it is. > > Interdata has some data types and instructions for manipulating them > not present in S/360. Circular lists, for example, and instructions > for CRC calculation. Yes, it's possible that both Interdata and RCA/UNIVAC/ICL instruction sets are supersets of the /360 instruction set. The only one I still remember is the LI (load immediate) instruction. The /360 did the same function with LA (load address), but IIRC that was RX (4 bytes), while LI was RR (2 bytes). > I didn't see anything about packed or zoned decimal support. > > So perhaps an extended subset of S/360. I'd have to do a side-by-side > comparison between this document and S/360 Principles of Operation to > determine the level of binary program compatibility, if any. But it > looks like it might be better than the HitchHiker's Guide to the > Galaxy adage: "almost, but not quite, entirely unlike tea." Yes, that seems reasonable. My guess was that binary compatibility wasn't a big issue in those days, since nearly all applications software was written only for specific installations. And of course licensing issues would preclude running IBM OS on the other machines. Greg -- Sent from my desktop computer. Finger grog@lemis.com for PGP public key. See complete headers for address and phone numbers. This message is digitally signed. If your Microsoft mail program reports problems, please read http://lemis.com/broken-MUA.php --Sw7tCqrGA+HQ0/zt Content-Type: application/pgp-signature; name="signature.asc" -----BEGIN PGP SIGNATURE----- iEYEARECAAYFAmTDOCoACgkQIubykFB6QiNHQgCgnogW1Nag7IbhAv06DgxLI6Sh DJAAnRV2Ha6fHL+48t2c/01ZP7abUbfw =4oBo -----END PGP SIGNATURE----- --Sw7tCqrGA+HQ0/zt--