In <[EMAIL PROTECTED]>,
on 08/03/2005
at 12:03 PM, "Gil, Victor x28091" <[EMAIL PROTECTED]> said:
>When a source line happens to contain an ampersand it can still be
>read by
> ISREDIT (THELINE) = LINE &ROW
>However, an attempt to rewrite it back [even unchanged!]
> ISREDIT LINE &ROW = &THELINE
>fails, and so does an attempt to examine its contents with the
>&SUBSTR function.
Your problem has nothing to do with ISPF; EXEC stage 2 swallows the
ampersand and ISPF never sees it. This is one of the areas where REXX
is easier than CLIST.
>I've looked through the manuals, tried SCAN OFF/ON
That doesn't help because the damage was done before ISPF saw the
command. It would be appropriate if you were passing the line by
value from REXX.
>Am I missing something stupid or is this a known limitation?
The problems of handling apostrophes and ampersands in CLIST are
known. If you must use CLIST, then you'll need to either use no rescan
or equivalent or to pass the line by name rather than value.
--
Shmuel (Seymour J.) Metz, SysProg and JOAT
ISO position; see <http://patriot.net/~shmuel/resume/brief.html>
We don't care. We don't have to care, we're Congress.
(S877: The Shut up and Eat Your spam act of 2003)
----------------------------------------------------------------------
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
