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 changed to REXX */
trace off
'extract /FT/'
if ftype.1 = 'EXEC' |,
ftype.1 = 'REXX' |,
ftype.1 = 'XEDIT'|,
ftype.1 = '2YEAR'|,
ftype.1 = 'RAW2YEAR'|,
ftype.1 = 'HOLDINGS'|,
ftype.1 = 'THISDATE' then do
SET CASE M
end
'SET NULLS ON'
'SET REMOTE ON'
'SET AUTOSAVE 100 A'
On Thu, 28 Jan 2010 10:01:40 -0500, 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 cas
e.
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.
"Mike MacIsaac" <[email protected]> (845) 433-7061
