×
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.
Hi Charles,
Had you been using CALLP, moving a given module to a *SRVPGM would
simply be a matter of recreating the program that was making use of
it, no other code changes needed. (Well you might add an h-spec with
the binding directory )
I certainly agree that CALLP (or EVAL or free format, or any of the
myriad other ways to use a prototype) is a better choice, but...
I don't understand why you think CALLP would be easier to transition to
the srvpgm than CALLB is. Why couldn't he re-create the code (leaving
the CALLB) and get the exact same result?
I mean... the binding part is exactly the same whether you use CALLB or
a prototype. The advantage to the prototypes come from additional
capabilities, better syntax checking, etc. But that's all done at
compile time. The binding part is exactly the same, so referencing a
binding directory to call a *SRVPGM instead of a *MODULE is exactly the
same with CALLB as it would've been with a prototype.
Why do you say that using CALLB maikes it harder?
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.
midrange.com
