Re: CALLPRC with RTNVAL

[rob@xxxxxxxxx]

This is a multipart message in MIME format.
--
[ Picked text/plain from multipart/alternative ]
You could add another subprocedure, or module to the service program. This
one would do the return vs the export.  No need to have another *PGM or
*SRVPGM object.

Rob Berendt
--
"They that can give up essential liberty to obtain a little temporary
safety deserve neither liberty nor safety."
Benjamin Franklin




"Phil" <sublime78ska@attbi.com>
Sent by: midrange-l-admin@midrange.com
04/03/2002 01:43 PM
Please respond to midrange-l


        To:     <midrange-l@midrange.com>
        cc:
        Fax to:
        Subject:        Re: CALLPRC with RTNVAL


Paul,

Thanks for explaining.  This service pgm has been around for many years,
and
I'm not about to change it!  I'll probably have the CL call an RPG which
then calls the service pgm.

Phil

> Subject: Re: CALLPRC with RTNVAL
> Reply-To: midrange-l@midrange.com
>
> Phil,
>
> There in lies your problem. A CL program cannot "import" a field.
>
> The RTNVAR parameter on CALLPRC refers to a parameter reurned by
> the called
> procedure. i.e. your RPG program should say:
>
> C                                        Return              Parm1.
>
> The procedure interface should be
>
> D GetParm              PI                            121
>
> with the corresponding prototype of
>
> D GetParm             PR
> 121                             Export
>
> HTH
>
> Paul Tuohy
>

_______________________________________________
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
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.