× 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.



Thanks Barbara (and Phil)... I just can't get my head around treating full
blown programs like sub-procedures, so just a couple more questions:

Can I omit the EXPORT keyword?
Is there a way to have both the PI and the *ENTRY? (just curious)
I assume I need the P specs?

Here's my example if someone could verify that I'm on track...

In the calling program:

d autocomp        pr                  extpgm('SALAUTO2')
d sbrecn                         7  0
d sbstry                         3
d sbfrpr                         8  0
d sbtopr                         8  0

In the CALLPed program:

d autocomp        pr                  extpgm('SALAUTO2')
d sbrecn                         7  0
d sbstry                         3
d sbfrpr                         8  0
d sbtopr                         8  0

d autocomp        pi                 
d sbrecn                         7  0
d sbstry                         3
d sbfrpr                         8  0
d sbtopr                         8  0


What I'm getting at is do I still need the name 'autocomp' on the PI? If
this was a sub-procedure I would have the EXPORT keyword, do I not need that
here?

Thanks... since I do sub-procedures all the time this shouldn't be so hard
for me... just getting adle brained! :)

Joel R. Cochran
Director of Internet Services
VamaNet.com
800-480-8810 (va toll free)
540-885-8050 (phone)
540-886-1589 (fax)
www.vamanet.com
mailto:custservice@vamanet.com


>-----Original Message-----
>From: bmorris@ca.ibm.com [mailto:bmorris@ca.ibm.com]
>Sent: Wednesday, August 15, 2001 5:56 PM
>To: midrange-l@midrange.com
>Subject: RE: QCMDEXC Wrapper
>
>
>
>> From: Joel R. Cochran
>> Sent: Wednesday, August 15, 2001 5:29 PM
>>
>> I've been messing around with Prototyping 'normal' calls.  I've
>> gotten this to work fine when calling an external program that
>> has a *ENTRY plist.  How do I change from *ENTRY to a PI in the
>> called program? Do I need any special keywords or can I just make
>> it a copy of the PR and change the PR to PI?
>
>The PI is expected to be match the PR, so that should work fine.
>You'll just have to remove the EXTPGM keyword.  And if you didn't
>give the parameters names in the PR, you'll have to name them in
>the PI.
>
>You still need to code the prototype (/copy it in before you code
>the PI).
>
>Barbara Morris
>
>_______________________________________________
>This is the Midrange Systems Technical Discussion (MIDRANGE-L) 
>mailing list
>To post a message email: MIDRANGE-L@midrange.com
>To subscribe, unsubscribe, or change list options,
>visit: http://lists.midrange.com/cgi-bin/listinfo/midrange-l
>or email: MIDRANGE-L-request@midrange.com
>


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.