The 360/44, which was not PoOps compliant lacked them: you ad to load the "commercial instruction set feature" in order to run a S/360 operating system. The 360/44 had its own OS that didn't use them.
-- Shmuel (Seymour J.) Metz http://mason.gmu.edu/~smetz3 ________________________________________ From: IBM Mainframe Assembler List [[email protected]] on behalf of [email protected] [[email protected]] Sent: Thursday, June 4, 2020 5:55 AM To: [email protected] Subject: Re: Convert *signed* EBCDIC to packed decimal On 2020-06-04 11:43, Dan Greiner wrote: > In an interview in the "Communications of the ACM" (volume 30, number > 4, April 1987), two of the original instruction-set architects — > Andris Padegs and Richard Case — weighed in on EDIT and EDIT AND MARK. > > The interviewer, Alfred Spector, asked: "Did you ever add instructions > to help justify the machine that in retrospect were not really > necessary?" Richard Case replied, "Yes. The edit instructions are one > clear instance. There are some other examples that are > debatable." Most of the S/360 instructions were unnecessary; all the SS character instructions, decimal, edit, translate etc are redundant. With the basic instruction set, all of these functions can be provided. Nevertheless, life is a lot easier with them. And instructions that do more than a just a basic operation (especially including TR, TRT, ED, EDMK) not only simplify programming, they run faster. > ED and EDMK sparked intense (and occasionally civil) discussion > between CPU engineers, the architecture group, and the languages > groups. The result of such discussions is probably why we decided not > to enhance these ops with ASCII or UNICODE versions.
