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" Thanks for showing where to put the vget and vput commands. That was the missing link I needed. >Personally I'd also set up error handling, probably at least a little >validation of the incoming parameters, and I might check that the 'save' >actually works before 'end'ing the macro. As it stands you won't be able to >tell from the invoking rexx exec whether what the macro was intended to do >actually worked. Excellent! I will remember this. >So, what happens is that you use the ispf variables support to save the values >of parmin etc before invoking edit, then once the macro has control it asks >ispf for the values that were saved. Thanks, this is what I want. I want variables which can be used in 'child' processes including macros. Anyways, I will play around with your suggestions, while 'they' will put the DFSORT solution in production. At least this (vget + vput) is something new for me to keep me busy. ;-) Groete / Greetings Elardus Engelbrecht ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to [email protected] with the message: INFO IBM-MAIN
