Excellent response, Richard! Changing ancient defaults is not backward
compatible, and risks breaking untold old (and perhaps poorly written)
XEDIT macros.
Our Y-disk contains the following "PROFILE XEDIT Y2", that performs some
(what I call) bare-minimum defaults so that all users get the benefit.
Having ONE place to set defaults has helped over the years.
When "PROFILE XEDIT Y2" it is done, it will call a "userid XEDIT" macro if
one exists. THAT personal file (e.g. 'JQPUBLIC XEDIT') is where users
place their own preferences.
The Y-disk also has a couple basic macros that the users can call from
their own XEDIT macros to handle most of the common settings. After they
call one of those, they can always add their own overrides for their
particular preferences. Providing sample basic settings helps newbies get
started.
PROFMANU XEDIT Y2 V <-- Settings so that IBM documented XEDIT
tutorials work as expected.
PROFSAMP XEDIT Y2 V <-- A sample PROFILE XEDIT that sets more
"intuituive" settings.
Mike Walter
Hewitt Associates
The opinions expressed herein are mine alone, not my employer's.
The Hewitt-standard "PROFILE XEDIT Y2" (with Hewitt-specific stuff
removed):
/* Prolog; See Epilog for additional information ********************
* Exec Name - PROFILE XEDIT from Y-disk. *
* Unit Support - IS *
* Status - Version 3, Release 1.0 *
********************************************************************/
address COMMAND
parse source xos xct xfn xft xfm xcmd xenvir .
parse arg parms 0 operands '(' options ')' parmrest
upper options parmrest /* Retain mixed case fileid */
self=userid()
address XEDIT
'SET PREFIX SYNONYM H PREFIXH' /* For XCOL when curline in middle */
'SET PREFIX SYNONYM HH PREFIXH' /* For XCOL when curline in middle */
/* If you always have your CURRENT LINE at the TOP of the screen, */
/* then you may want to delete the above PREFIXH's and change the */
/* following 'K' and 'KK' to 'H' and 'HH'. */
'SET PREFIX SYNONYM K PREFIXH2' /* For XCOL when curline at top */
'SET PREFIX SYNONYM KK PREFIXH2' /* For XCOL when curline at top */
'SET PREFIX SYNONYM TT T'
'SET PREFIX SYNONYM RR R'
'SET SYNONYM CC CCANCEL'
'SET AUTOSAVE 10'
'SET FULLREAD ON'
'SET NULLS ON'
'SET REMOTE ON'
'EXTRACT /CASE/'
'SET CASE' case.1 'IGNORE'
/* DELETE ME */ /*If you insist on copying this file from the Y-disk,
*/
/* DELETE ME */ /*then delete all lines starting with: /* DELETE ME */
*/
/* DELETE ME */ If xfn<>'PROFILE' then
/* DELETE ME */ Do
/* DELETE ME */ msg 'The PROFILE XEDIT has been improperly copied',
/* DELETE ME */ 'from the Y-disk.'
/* DELETE ME */ msg 'Please read the comments in the EPILOG of',
/* DELETE ME */ 'the PROFILE XEDIT Y and try again.'
/* DELETE ME */ exit 8
/* DELETE ME */ End
/* DELETE ME */ Address Command 'STATE' self 'XEDIT *'
/* DELETE ME */ If rc<>0 then Exit
/* DELETE ME */ If xfn<>self then COMMAND 'MACRO' userid()
Exit;
/* Epilog ***********************************************************
* Function - Provide 'standard' PROFILE XEDIT which can be *
* UPDATED BY SUPPORT PERSONNEL to bypass any bugs *
* in XEDIT without affecting users. *
* *
* When XEDIT is entered, it will execute any *
* commands in the first PROFILE XEDIT file found. *
* The commands in the PROFILE XEDIT Y file have *
* been chosen to provide the best performance and *
* be as 'user friendly' as possible. *
* *
* When the PROFILE XEDIT Y file is done, it will *
* attempt to pass control to (if found) a file *
* named "your userid" XEDIT (e.g. JQPUBLIC XEDIT). *
* It is in THAT file that your personal XEDIT *
* commands should be placed. Thus, there is no *
* reason to copy the PROFILE XEDIT Y to your own *
* disk. Just put the commands you want to take *
* affect after PROFILE XEDIT in a file with your *
* userid as the filename and a filetype of XEDIT. *
* *
* Component of - XEDIT at Hewitt Associates. *
* Command format- N/A *
* Called by - XEDIT *
* Dependencies - VM/SP 3 or higher. *
* Program Lang. - CMS REXX *
* Date Written - 10/25/87 *
* Author - Michael R. Walter *
* Changed | By | Description of Change *
* --------+-----+------------------------------------------------- *
* 01/25/89 mrw -Add 'SET CASE' case.1 'IGNORE' *
* 01/09/92 mrw -Add 'H, HH, K and KK' prefix synonyms for XCOL *
* 06/03/95 mrw -Pretty-up. *
* 20000523 mrw -Update to STATE prexedit before execute. *
* 20010118 mrw -Retain mixed-case fileid. *
* *
********************************************************************/
"Schuh, Richard" <[email protected]>
Sent by: "The IBM z/VM Operating System" <[email protected]>
01/28/2010 11:02 AM
Please respond to
"The IBM z/VM Operating System" <[email protected]>
To
[email protected]
cc
Subject
Re: XEDIT SET CASE default setting - is it the best?
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:[email protected]] On
Behalf Of P S
Sent: Thursday, January 28, 2010 7:08 AM
To: [email protected]
Subject: Re: XEDIT SET CASE default setting - is it the best?
On Thu, Jan 28, 2010 at 10:01 AM, Michael MacIsaac <[email protected]>
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).
The information contained in this e-mail and any accompanying documents may
contain information that is confidential or otherwise protected from
disclosure. If you are not the intended recipient of this message, or if this
message has been addressed to you in error, please immediately alert the sender
by reply e-mail and then delete this message, including any attachments. Any
dissemination, distribution or other use of the contents of this message by
anyone other than the intended recipient is strictly prohibited. All messages
sent to and from this e-mail address may be monitored as permitted by
applicable law and regulations to ensure compliance with our internal policies
and to protect our business. E-mails are not secure and cannot be guaranteed to
be error free as they can be intercepted, amended, lost or destroyed, or
contain viruses. You are deemed to have accepted these risks if you communicate
with us by e-mail.
