Many companies do not see the depreciation interval for a purchased mainframe to be an automatic trigger for the purchase of a new replacement mainframe. Instead, some of them quite enjoy the lack of hardware expenditures.
We often encounter old machines at customer sites, and must make sure that our code runs successfully on *all* machines that are supported by the base level of z/Architecture. I am certain that you will receive a similar answer from many of the others on this list who develop code for a broader audience than their own companies. -- Regards, Gord Tomlin Action Software International (a division of Mazda Computer Corporation) Tel: (905) 470-7113, Fax: (905) 470-6507 On 2013-04-13 17:44, John Gilmore wrote:
As I attempted to make clear in my earlier post, this old-hardware argument is specious. If you want to support old machines, write a macro called TRTE for them, but use TRTE in your code. It reduces clutter, increases readability, improves performance where the instruction is installed, etc., etc. Note also that the '7th edition' of the PrOp was published in 2008 February, a bit more than five years ago and longer than the depreciation interval for a purchased mainframe. I have made my views and the reasons for them clear. Others are of course free to do as they think best. How not? John Gilmore, Ashland, MA 01721 - USA
