Actually, IBM already did make some significant changes to XEDIT defaults. I still have the MEMO file sitting on our X disk (from the days when DTRIPF did more than a NOPAN), dated Dec 12, 1984, wherein we tell our users that since the new release of VM/SP changed the way XEDIT behaved, we were going to change the system's PROFILE XEDIT to make it easier to live with. So ever since then, the IBM defaults have been overridden. Everyone gets our altered version of PROFILE XEDIT unless they already have their own altered version on their A disk.
BTW, the change made in VM/SP was the ability to control the line where the message line was set to. In prior releases we could only turn XEDIT messages on or off. The new ability let us move the message line to somewhere other than the command line. And since this new function also made the command line go away when a message was sent (which it didn't do before), it caused some panic among users. When the answer came back "working as designed", we re-designed the profile edit. Had I only looked last month we could have had a 25th anniversary party! Ron On Fri, Jan 29, 2010 at 11:41 AM, Schuh, Richard <rsc...@visa.com> wrote: > That is why I suggested later that if such a change were to be made, it > should be at a release boundary and the Conversion Guide should scream about > it. Even then, there would be those who missed noticing it until it bit the > users. > > So there are alternatives to having IBM change the default actions. Some even > give you greater control over the initial, and I emphasize initial, settings > a user sees. Once the id has been turned over to a user, it is out of your > hands. The user will keep or change settings at will. And, believe me, there > are some users who will do wild and crazy things and then ask you why the > system is broken. >
