At 08:43 -0500 on 02/10/2013, John Gilmore wrote about Re: DSPSERV with SCOPE=?:
For execution-time binding Robert Rosenberg's scheme, or something very like it, is the only viable one. (I looked at the macro definition.) John Gilmore, Ashland, MA 01721 - USA
At 10:01 -0500 on 02/10/2013, Peter Relson wrote about Re: DSPSERV with SCOPE=?:
The only supported approach to parameterize the SCOPE value at runtime is brute force, in your case triple-pathing the code for the three choices you want to make available. Peter Relson z/OS Core Technology Design
I just posted a simpler single path solution. Just overlay the actual branch that the ends of the MF=E expansion code, issue the MF=E generated instruction that differs and THEN do the overlayed branch. You end up with the desired result without needing to triple path. You still need to pass the required scope to the routine but depending on how that parm in the MF=L to be set you can just copy the passed parm or select the correct instruction to issue.
