Author: Robert Sample
Posted: Wed May 04, 2016 2:41 am (GMT 5.5)
One obvious difference is that Xpediter has to insert code to break for each line of code with F9 and doesn't have to do that for F12. I think your best bet is to contact the vendor for assistance -- they most likely have seen the problem before and know just how to resolve it.
I've seen a similar problem in the past -- a program wouldn't work until it was Xpedited at which time the code worked fine. IIFC (and it's been more than 20 years so that recall may not be correct), the issue was a storage overlay involving a map in CICS; since the Xpediter screen was injected in the middle it prevented the problem for showing up.
_________________
TANSTAAFL
The first rule of code reuse is that the code needs to be worth re-using.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth
Posted: Wed May 04, 2016 2:41 am (GMT 5.5)
One obvious difference is that Xpediter has to insert code to break for each line of code with F9 and doesn't have to do that for F12. I think your best bet is to contact the vendor for assistance -- they most likely have seen the problem before and know just how to resolve it.
I've seen a similar problem in the past -- a program wouldn't work until it was Xpedited at which time the code worked fine. IIFC (and it's been more than 20 years so that recall may not be correct), the issue was a storage overlay involving a map in CICS; since the Xpediter screen was injected in the middle it prevented the problem for showing up.
_________________
TANSTAAFL
The first rule of code reuse is that the code needs to be worth re-using.
"We should forget about small efficiencies, say about 97% of the time: premature optimization is the root of all evil." -- Donald Knuth