On Fri, 29 Mar 2019 07:56:36 -0500, Elardus Engelbrecht wrote: >Jeremy Nicoll wrote: > >>Remember that when an ispf edit macro starts to execute you have access to >>the underlying ispf session, and indeed underlying TSO. So change the macro >>to, for example: > >>address ispexec "vget (parmin parmuit) profile" > Neat! I never became proficient with the ISPF variable pool.
Is there any restriction on the content of ISPF variables? Special characters? Length? Can they be delimited strings, subject to the design deficiencies of delimited strings? I've sometimes resorted to adding a temporary data set to my SYSEXEC concatenation and creating Execs/Macros dynamically there, often with a TSO REPRO from an instream data set. -- gil ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
