That is the purpose of the PROFILE XEDIT; to customize it to your own preferences. My "best" is likely to not be your "best. Changing the system wide default of something that has been around for 1 or 2 coon's ages would have the potential for causing many people/programs anguish. It is, in my opinion, best left as is, especially since it is documented to act that way and you have the ability to customize it.
Regards, Richard Schuh ________________________________ From: The IBM z/VM Operating System [mailto:ib...@listserv.uark.edu] On Behalf Of P S Sent: Thursday, January 28, 2010 7:08 AM To: IBMVM@LISTSERV.UARK.EDU Subject: Re: XEDIT SET CASE default setting - is it the best? On Thu, Jan 28, 2010 at 10:01 AM, Michael MacIsaac <mike...@us.ibm.com<mailto:mike...@us.ibm.com>> wrote: Hi, I was asked for help with a Linux install problem and it seems that the Linux parameter file, stored in a CMS file, had been folded to upper case. Getting the parameter file with the correct case will probably fix the problem. The default setting seems to be CASE UPPER for most file types (though I don't see that specifically stated in the XEDIT Commands manual - maybe I missed it). I do see on line 4 of the PROFILE XEDIT shipped on the MAINT 191 disk, the command "SET CASE M I". So the default is overridden on MAINT, but not on other user IDs that don't have a PROFILE XEDIT. Does this make sense? There is an argument that changing this default would break existing code/environments. Do people agree with this argument? Or would you prefer to see the default change to CASE MIXED? (not that I have much influence on such a possible decision :)) Thanks. It defaults per filetype based on the tables in DMSXTF, which haven't been updated in a coon's age, maybe two coons. Defaulting to CASE MIXED has always seemed to make sense to me, especially if the tables in DMSXTF still applied (i.e., if the ones that are explicitly CASE UPPER stayed that way).
