RE: QCMDEXC Wrapper

The only thing that bothered me about this was the fact that now the
prototype in the calling program is named autocomp and the prototype in the
CALLPed program is SALAUTO2, but I guess they will be OK because the calling
program has the EXTPROC keyword?

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: Gary L Peskin [mailto:garyp@firstech.com]
>Sent: Thursday, August 16, 2001 1:53 PM
>To: midrange-l@midrange.com
>Subject: Re: QCMDEXC Wrapper
>
>
>Or, you could leave it as autocomp and add an extpgm('SALAUT02') on the
>D-PR in the called program (ie in SALAUTO2).
>
>Gary
>
>"Joel R. Cochran" wrote:
>> 
>> One more note:
>> 
>> In order to get this to compile, I had to change the name in 
>the CALLPed
>> module to reflect the EXTPROC name on the calling Prototype 
>like so (note
>> the >>>):
>> 
>> 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 SALAUTO2        pr
>> d sbrecn                         7  0
>> d sbstry                         3
>> d sbfrpr                         8  0
>> d sbtopr                         8  0
>> 
>> >>> d SALAUTO2        pi
>> d sbrecn                         7  0
>> d sbstry                         3
>> d sbfrpr                         8  0
>> d sbtopr                         8  0
>> 
>> 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: Joel R. Cochran [mailto:jrc@masi-brac.com]
>> >Sent: Thursday, August 16, 2001 1:27 PM
>> >To: 'midrange-l@midrange.com'
>> >Subject: RE: QCMDEXC Wrapper
>> >
>> >
>> >Thanks Gary, great responses!  The whole P spec deal was
>> >really throwing me
>> >off, but I think I've got it straight now.
>> >
>> >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: Gary L Peskin [mailto:garyp@firstech.com]
>> >>Sent: Thursday, August 16, 2001 1:04 PM
>> >>To: midrange-l@midrange.com
>> >>Subject: Re: QCMDEXC Wrapper
>> >>
>> >>
>> >>"Joel R. Cochran" wrote:
>> >>>
>> >>> 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?
>> >>
>> >>The EXPORT keyword for a procedure goes on the P-spec.  
>Since there is
>> >>no P-spec for main procedures, you don't specify it :).  
>(See below re
>> >>P-specs).
>> >>
>> >>> Is there a way to have both the PI and the *ENTRY? (just curious)
>> >>
>> >>I just tried this.  I get:
>> >>
>> >>*RNF5401 30 a      001800  The entry parameters have already been
>> >>defined using a
>> >>                           procedure-interface definition.
>> >>
>> >>> I assume I need the P specs?
>> >>
>> >>No.  These are for subprocedures.  Not main procedures.
>> >>
>> >>>
>> >>> 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?
>> >>
>> >>When I remove it, I get:
>> >>
>> >>*RNF3781 30      7 000700  The procedure-interface 
>definition for the
>> >>main procedure
>> >>                           must have a name.
>> >>
>> >>> If
>> >>> this was a sub-procedure I would have the EXPORT keyword, do
>> >>I not need that
>> >>> here?
>> >>
>> >>Again, there is no P-spec.
>> >>
>> >>>
>> >>> Thanks... since I do sub-procedures all the time this
>> >>shouldn't be so hard
>> >>> for me... just getting adle brained! :)
>> >>
>> >>Just code it up and try it.  The compiler will tell you if you have
>> >>problems!!
>_______________________________________________
>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
>