× The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.



That makes sense, Jon, and I'll try that and report back. However, I'm seeing the same problem in production on a field that is then used in a report. I would expect that assigning the value to a field that is then used in an O-spec would be enough to de-optimize it, no?

In any case, my optimization is normally *NONE and DSPPGM tells me my optimization level is *NONE on the module. But I'll put in the DSPLY and get back to the list.

Joe

Only time I would expect to see this Joe is when compiling with optimization. The variable is not used inside your subproc and so the optimizer would throw away the assignment. Even if you are not compiling this way it is possible a similar effect is occurring (which hopefully is cured by PTF) but either way adding a DSPLY of the variable in the subproc should "cure" it.


Jon Paris


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Replies:

Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].

Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.