×
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.
"WDSCI-L" <wdsci-l-bounces@xxxxxxxxxxxx> wrote on 11/30/2017 02:20:59 PM:
Just compiler directives...
Ok, so it is just a tricky way of inserting the usual compiler
directives into the service program's source that allows the caller to use
the usual additional compiler directives to selectively extract source
when you INCLUDE the actual service program's entire source. Seems that
would be klunky, because you would need two different DEFINEs for a single
block of definitions in order to always use it in the service program but
only selectively use it in the caller. Is there some trick I don't see
with this method?
Regarding the *NOUINREF not being perfect...
It was suggested to me by an IBM'er to open a PMR if I really want it
improved...
There are two issues with *NOUNREF as I see it. #1 It seems that
definitions might not be used but if they are only referenced by a
prototype (using LIKE or LIKEDS) then they get included in the compiled
object even though the prototype, itself, is not referenced. #2 It seems
that even though a definition might get excluded (because of non-use) from
the compiled object, it still shows up in the compile listing that is
included in the compiled object. I will suggest to the programmer here
that always complains about this that they should open an issue with IBM.
Sincerely,
Dave Clark
midrange.com
