/marklwheeler
Date: Thu, 28 Jan 2010 09:02:09 -0800
From: rsc...@visa.com
Subject: Re: XEDIT SET CASE default setting - is it the best?
To: IBMVM@LISTSERV.UARK.EDU
That is the purpose of the PROFILE XEDIT; to customize it to your own
preferences. My "best" is likely to not be your "bes
That is in keeping with the bit of wisdom that has been frequently passed on in
this forum and at other places, "If it is documented, it will not change unless
absolutely necessary. If not documented, it can change at any time; use or rely
on it at your own risk."
Regards,
Richard Schuh
>
Sir Alan writes:
> FWIW, I have learned that a Supplicant intends to petition Supreme High
> Council of z/VM Design (known in some circles as "The Coven") ...
Yes, *it is I* who dare to summon The Coven. I chant appropriately, tug on
my forelock, and will even bring some young REXX EXECs for sac
Long, long ago, at UofW, I wrote an "AUTOCASE" setting. If AUTOCASE was on, but
CASE was U, altering a line would examine the line and see if it was all
uppercase. If not, it would leave case alone. If it was all uppercase (or all
blank, or all non-alpha, anyway), entered alpha characters were f
And here I thought it was the Knights Who Say Nee, and that you had to
bring a shrubbery.
-Original Message-
FWIW, I have learned that a Supplicant intends to petition Supreme High
Council of z/VM Design (known in some circles as "The Coven") to change
the default CASE setting in XEDIT
On Friday, 01/29/2010 at 01:10 EST, Kris Buelens
wrote:
> And, if a newly typed text is unexpectedly in mixed case, there always
is the
> UPPER command. And as there is no "BackToMixed" command to restore my
> carefully type text, Mixed would be a better default nowadays for the
XEDIT
> un
On Fri, Jan 29, 2010 at 7:10 PM, Kris Buelens wrote:
> And, if a newly typed text is unexpectedly in mixed case, there always is
> the UPPER command. And as there is no "BackToMixed" command to restore my
> carefully type text, Mixed would be a better default nowadays for the XEDIT
> unexperien
On Fri, Jan 29, 2010 at 12:34 PM, Chip Davis wrote:
> Okay, I concede. Even though he's a relative newcomer to VM, Phil's is
> longer then mine...
>
Hah. I know when I'm being baited...let's see, it was about 1975. So no, I
don't go back to VM/370 R1.
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 go
And, if a newly typed text is unexpectedly in mixed case, there always is
the UPPER command. And as there is no "BackToMixed" command to restore my
carefully type text, Mixed would be a better default nowadays for the XEDIT
unexperiended
2010/1/29 Schuh, Richard
> That is why I suggested later
On Friday, 01/29/2010 at 12:47 EST, Nick Laflamme
wrote:
> Ardent goes scampering off to find the TCP/IP samples disk, to see if
there's a
> stray PROFILE XEDSAMP on it that he'd want to study very carefully
before
> running
No no no. Totally unnecessary. Totally. There's no need to s
On Jan 29, 2010, at 9:32 AM, Alan Altmark wrote:
> This discussion has taken the inevitable religious turn and, as expected
> with this crowd, each of us has the best view of the Light. As it
> happens, I know that I alone posess the One True Profile and I am content.
>
> At the End of Days, w
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.
That said, the ability to choose whether or not to change it cou
Okay, I concede. Even though he's a relative newcomer to VM, Phil's is longer
then mine...
On 1/29/10 16:18 Phil Smith III said:
Chuckie wrote:
At the End of Days, we will be Judged, not by our actions or who we are,
but by the sophistication of our respective PROFILEs. I am ready. Are
you?
Chuckie wrote:
> At the End of Days, we will be Judged, not by our actions or who we are,
>but by the sophistication of our respective PROFILEs. I am ready. Are
>you?
I sure am -- I bet my PROFILE XEDIT does more than yours, neener neener!
Seriously, it does do some things that reflect 30 year
Typing is good for my arthritis; it saves me a fortune at the pharmacy.
On Thu, 28 Jan 2010 22:55:57 -0500, Les Koehler
wrote:
>Using WORDPOS() would be a *lot* more efficient and easier
>to type!
>
>Les
>
This discussion has taken the inevitable religious turn and, as expected
with this crowd, each of us has the best view of the Light. As it
happens, I know that I alone posess the One True Profile and I am content.
At the End of Days, we will be Judged, not by our actions or who we are,
but by
On Thu, 28 Jan 2010 09:02:09 -0800 Schuh, Richard said:
>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
On Fri, Jan 29, 2010 at 9:40 AM, Les Koehler wrote:
> I didn't mean to imply 'best practices', just another alternative to
> consider.
>
And I hope my tongue-in-cheek quip wasn't taken as being critical! It sure
wasn't intended as such.
I didn't mean to imply 'best practices', just another
alternative to consider.
Les
Chip Davis wrote:
Perhaps. But this thread evolved into a "best practices" discussion.
That is a
wide gamut which conceivably extends down to Rexx coding suggestions.
For example, my PROFILE XEDIT checked th
Perhaps. But this thread evolved into a "best practices" discussion. That is a
wide gamut which conceivably extends down to Rexx coding suggestions.
For example, my PROFILE XEDIT checked the first line of the file and if it found
a lower-case character, it 'SET CASE MIXED RESPECT', otherwise i
On Thu, Jan 28, 2010 at 10:55 PM, Les Koehler wrote:
> Using WORDPOS() would be a *lot* more efficient and easier to type!
>
And so the wars resume...
Using WORDPOS() would be a *lot* more efficient and easier
to type!
Les
C. Lawrence Perkins wrote:
You can test the FILETYPE ( or FILENAME or FILEMODE ) within PROFILE XEDI
T
and set your CASE to whatever you want based on what the variable extract
s
for you. Sample:
/*PROFILE change
On Thu, Jan 28, 2010 at 6:41 PM, C. Lawrence Perkins
wrote:
> You can test the FILETYPE ( or FILENAME or FILEMODE ) within PROFILE XEDIT
> and set your CASE to whatever you want based on what the variable extracts
> for you. Sample:
If you do UPDATE in XEDIT, you may want to look at BASEFT as we
On Thu, Jan 28, 2010 at 2:47 PM, Schuh, Richard wrote:
> The company where I was for Y2K ignored our advice and pleas to do
> something about it, pleas starting in the 1980s and continuing until they
> looked into it in 3Q 1997. Their conclusive action was to outsource the
> entire IT function.
On Thu, Jan 28, 2010 at 12:31 PM, Mike Walter wrote:
> Excellent response, Richard! Changing ancient defaults is not backward
> compatible, and risks breaking untold old (and perhaps poorly written)
> XEDIT macros.
>
This is of course correct. The best solution is a time machine, to go back
to 1
The company where I was for Y2K ignored our advice and pleas to do something
about it, pleas starting in the 1980s and continuing until they looked into it
in 3Q 1997. Their conclusive action was to outsource the entire IT function.
Where's the fun in that?
Regards,
Richard Schuh
On Thu, Jan 28, 2010 at 2:34 PM, Schuh, Richard wrote:
> That is not far enough back, it has to go back at least to 1972 :-)
>
Not for XEDIT?! But when I finish it, it will go back earlier, to fix:
- ASCII vs. EBCDIC
- null-terminated strings
- case sensitivity in *IX
All three of those have
: Re: XEDIT SET CASE default setting - is it the best?
On Thu, Jan 28, 2010 at 12:31 PM, Mike Walter
mailto:mike.wal...@hewitt.com>> wrote:
Excellent response, Richard! Changing ancient defaults is not backward
compatible, and risks breaking untold old (and perhaps poorly written)
XEDIT
On Thu, Jan 28, 2010 at 12:31 PM, Mike Walter wrote:
> Excellent response, Richard! Changing ancient defaults is not backward
> compatible, and risks breaking untold old (and perhaps poorly written)
> XEDIT macros.
>
This is of course correct. The best solution is a time machine, to go back
to 1
You can test the FILETYPE ( or FILENAME or FILEMODE ) within PROFILE XEDI
T
and set your CASE to whatever you want based on what the variable extract
s
for you. Sample:
/*PROFILE changed to REXX */
trace off
'extract /FT/'
if ftype.1 = 'EXEC' |,
ftype.1 = 'REXX' |,
ftype.1 =
> since it is documented to act that way
I couldn't find that.
"Mike MacIsaac"(845) 433-7061
"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
m [ib...@listserv.uark.edu] On Behalf Of Rob
van der Heij [rvdh...@gmail.com]
Sent: Thursday, January 28, 2010 11:31 AM
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: XEDIT SET CASE default setting - is it the best?
PS Could the "feature" stem from the days where folks had terminals
that displayed on
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
mailto:mike...@us.ibm.com>> wrote:
Hi,
I was asked for help with a Linux install problem and it seems that the Linux
On Thu, Jan 28, 2010 at 4:07 PM, P S wrote:
> 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 o
and yes sometimes I wear a belt and suspenders ;-)
Bill Munson
Sent by: The IBM z/VM Operating System
01/28/2010 10:33 AM
Please respond to
The IBM z/VM Operating System
To
IBMVM@LISTSERV.UARK.EDU
cc
Subject
Re: XEDIT SET CASE default setting - is it the best?
it can be in both
it can be in both
which I do - just to be sure
Scott Rohling
Sent by: The IBM z/VM Operating System
01/28/2010 10:22 AM
Please respond to
The IBM z/VM Operating System
To
IBMVM@LISTSERV.UARK.EDU
cc
Subject
Re: XEDIT SET CASE default setting - is it the best?
I think you&#x
ating System [mailto:ib...@listserv.uark.edu] On
Behalf Of P S
Sent: January 28, 2010 10:12
To: IBMVM@LISTSERV.UARK.EDU
Subject: Re: XEDIT SET CASE default setting - is it the best?
On Thu, Jan 28, 2010 at 10:08 AM, Bill Munson
wrote:
Mike,
I have been creating my own "XEDIT" on any C
I think you're thinking of the PROFILE EXEC .. ?
Scott
On Thu, Jan 28, 2010 at 8:18 AM, Bill Munson wrote:
> and I agree with just one addition
>
> SET PF12 RETRIEVE
>
> munson
>
>
>
>
and I agree with just one addition
SET PF12 RETRIEVE
munson
P S
Sent by: The IBM z/VM Operating System
01/28/2010 10:11 AM
Please respond to
The IBM z/VM Operating System
To
IBMVM@LISTSERV.UARK.EDU
cc
Subject
Re: XEDIT SET CASE default setting - is it the best?
On Thu, Jan 28
Mike,
The XEDIT default settings are described in Appendix A of the "z/VM: XEDIT
Commands and Macros Reference". The case settings are determined by the
filetype of the file. If the filetype is not one in the "recognized" list,
then the case defaults to upper.
Thanks!
Mike
On Thu, Jan 28, 2010 at 10:08 AM, Bill Munson wrote:
> Mike,
>
> I have been creating my own "XEDIT" on any CMS userid I use, for so long,
> that is almost the first thing I do when I encounter a new System
>
> It is annoying when you go to a NEW place and it is not set up "properly"
>
And now we
c
Sent by: The IBM z/VM Operating System
01/28/2010 10:01 AM
Please respond to
The IBM z/VM Operating System
To
IBMVM@LISTSERV.UARK.EDU
cc
Subject
XEDIT SET CASE default setting - is it the best?
Hi,
I was asked for help with a Linux install problem and it seems that the
Linux param
On Thu, Jan 28, 2010 at 10:01 AM, Michael MacIsaac 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
> pro
I don't believe I edit anything without my own Profile Xedit so I know
exactly what the settings are. Well except for when I create my Profile
Xedit the first time on any VM.
On Thu, Jan 28, 2010 at 10:01 AM, Michael MacIsaac wrote:
>
> Hi,
>
> I was asked for help with a Linux install problem a
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
47 matches
Mail list logo
