Shmuel ! I sent my original source, and it was REXX. Having a few spare moments, I quickly converted the REXX to CLIST and all of the FIND's worked as a clist. Oddly, they work with or withOUT SCAN OFF. Whether the problem belongs to ISPF, REXX, or both is not my problem. These commands should work as a REXX. I'll let IBM sort it out.
From: "Shmuel Metz (Seymour J.)" <[email protected]> To: [email protected] Date: 07/19/2012 07:17 AM Subject: Re: REXX ISPF edit FIND failing Sent by: IBM Mainframe Discussion List <[email protected]> In <9b26bc6a6df52d4483dd73b1fe7b4b0658b83d6...@uspho-mxvs07.amer.thermo.com>, on 07/18/2012 at 10:37 AM, "Hardee, Chuck" <[email protected]> said: >Uh, I don't think so. >You're thinking CLIST not REXX. I doubt it. What he wrote was 'The problem is that ISPF/ISREDIT evaluates/substitutes any ISPF variable, which in this case is "&PDQR".', which does not refer to either CLIST or REXX variables. >Try adding the statement: &PDQR="A" To set the ISPF variable PDQR from REXX he needs to dreop the ampersand: PDQR="A" >You will see in the trace that &PDQR was not substituted. In what trace? The REXX trace is not relevant to substitutions performed by ISPF. -- Shmuel (Seymour J.) Metz, SysProg and JOAT Atid/2 <http://patriot.net/~shmuel> 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: INFO IBM-MAIN ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
