IMHO certainly it is, as long as it is part of a "normal" (FSVO "normal") development cycle and not an emergency fix for the abend that just stopped the works at oh-dark-thirty.
And also as long as the QA group are made aware in a timely manner that a full regression testing for the function should be part of the QA process for the cycle, and not just a "new function" test, and that the QA workload for the cycle permits that level of effort. The problem is, of course, the temptation to also convert to code-register-baseless and reentrant variable storage areas at the same time. Too many changes at once can really make for a mess. BTDTGTTS. There are many parts to the machine, and they must all hang together or they shall surely hang alone (with apologies to my Revolutionary forebears). Peter -----Original Message----- From: IBM Mainframe Assembler List [mailto:[email protected]] On Behalf Of Martin Packer Sent: Friday, April 19, 2013 2:09 PM To: [email protected] Subject: Re: AMODE(24). How much is there? A question - to which I don't personally have an answer - is... ... when you open the code up to make a business-required change is it also sensible to contemplate changing AMODE while the code is open? I suspect it depends heavily on the language. Cheers, Martin -- This message and any attachments are intended only for the use of the addressee and may contain information that is privileged and confidential. If the reader of the message is not the intended recipient or an authorized representative of the intended recipient, you are hereby notified that any dissemination of this communication is strictly prohibited. If you have received this communication in error, please notify us immediately by e-mail and delete the message and any attachments from your system.
