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!!