|
Alan Shore wrote:program
My original question was how to call a sub-procedure from a service
listfrom within a CLP program
I'm sorry, but that was NOT your original question. Your original
question was (this is a copy/paste from your message):
Is it possible to call a subprocedure from a service program
from within a CL (or CLLE) program?
You'll note that NOWHERE in your message do you way CLP! You mention
CL, which is something else entirely, and CLLE -- CLLE is the only one
of those choices that's ILE, and therefore the only one that can call a
service program.
How do I bind the binding directory
The answer was to use the command CRTPGM
You can't use CRTPGM with a CLP -- CLP is OPM, CRTPGM is ILE. Your
member types should be CLLE if you're using CRTPGM.
This lead to my statement that you replied to
How can I apply a binding directory when using the CRTCLPGM command
Hopefully you can now see my predicament
CRTCLPGM is OPM, it can't compile ILE code!! You can't use a binding
directory with CRTCLPGM!! But, your accusation (or the way I read it,
anyway) is that MKS uses CRTCLPGM for CLLE source member types -- and
that's what I can't believe. I simply can't accept that MKS is 12 years
behind the times and doesn't understand the difference between OPM and
ILE. More likely, you (who have consistently in this thread sounded
confused about the diff between CL, CLP and CLLE) are setting your
member type to CLP instead of the correct CLLE.
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.
As an Amazon Associate we earn from qualifying purchases.
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.