In a recent note, Steve Comstock said:
> Date: Sat, 12 Aug 2006 06:43:23 -0600
>
> Try coding it as
>
> 'CHANGE C''(&FOO,BAR)'' C''wombat'' ALL'
>
> in other words, I've always thought both the first and
> second operands had to be bounded by the same delimiters
> (although I know there are cases that is not necessary,
> it never seems to hurt my chances of success).
>
Alas, no:
31 *-* address 'ISREDIT' 'SCAN OFF'
>>> "SCAN OFF"
32 *-* 'CHANGE c''(&FOO,BAR)'' ''wombat'' ALL'
>>> "CHANGE c'(&FOO,BAR)' 'wombat' ALL"
+++ RC(4) +++
Again, pasting the failed command from the log to the command
line makes the change.
The "same delimiters" rule would be kind of harsh -- you'd never
be able to change an apostrophe to a quote with:
CHANGE "'" '"'
OK. I've managed it with two commands, one to remove the
apparent symbol, and one to make the final change:
36 *-* 'CHANGE c''FOO,BAR)'' ''/OO,BAR)'' ALL'
>>> "CHANGE c'FOO,BAR)' '/OO,BAR)' ALL"
37 *-* 'CHANGE c''(&/OO,BAR)'' wombat ALL'
>>> "CHANGE c'(&/OO,BAR)' wombat ALL"
This aspirates. Isn't there a more transparent way?
-- gil
--
StorageTek
INFORMATION made POWERFUL
----------------------------------------------------------------------
For IBM-MAIN subscribe / signoff / archive access instructions,
send email to [EMAIL PROTECTED] with the message: GET IBM-MAIN INFO
Search the archives at http://bama.ua.edu/archives/ibm-main.html
