On Dec 4, 2008, at 01:22, John P. Hartmann wrote:
Changing the system configuration file sets the system-wide default. Unless yours is a one-user VM system, that is likely to upset other users, if not for any other reason, then because it would appear as a gratiotous change.
The problem worst affects inexperienced users who simply don't know what's happening; their passwords don't work. And when some of them have come to me for advice, and I guess their problem, and ask them if there are any of the troublesome characters in their passwords, they prudently suspect me of malicious human engineering. The problem is hard to recognize because passwords are never echoed. One beneficial design change might be to never apply line editing to text typed in nondisplayed fields. CMS users ought not be burdened forever by an accommodation made for a terminal design that's hardly in use any longer.
You can turn them all of in your directory entry with DIRMAINT. There are four in all.
I can make changes to my directory entry, or is this again something I must request of my administrator? Again, for new directory entries for new users who won't perceive a gratuitous change, the default should be OFF.
And there is no difficulty in editing my macros; you just have to remember to escape the hash: x "#incdec macro
Not since IBM fixed it by APAR many years ago. And the problem was not with the XEDIT command from the CMS command line, but from the XEDIT LOAD command issued from PROFILE EXEC.
Or do it from FILELIST.
The problem, now fixed, equally affected XEDIT when invoked from FILELIST. I don't even think XEDIT was aware whether it was being invoked from FILELIST. -- gil
