RE: CALLPRC with RTNVAL

A really weird thought - use a full 121 characters in the chgvar. There was
something about this in the knowledge base article, that you need to do
this with parms. Maybe with RTNVAL too.

At 10:40 AM 4/3/02 -0500, you wrote:

>Rob Berendt wrote:
> >How's about the prototype for the service program?
>
>Rob,
>
>The service pgm doesn't have a prototype - it exports the parm:
>
>  Dparm1            s            121    export
>
>That's it for the d-spec's in the whole pgm (it's only 18 lines long.)
>
>If an RPG pgm calls the srvpgm, then the value of parm1 is correct when it
>returns to the calling pgm.  Not so when CL calls it.
>
>Phil
>
>
> >I'm having trouble with the data returned from a srvpgm which is called
> >from
> >a CL with CALLPRC:
> >
> >      PGM        parm(&parm)
> >      dcl &parm *char 121
> >
> >      if cond(%sst(&parm 1 1) *eq ' ') then(do)
> >        chgvar &parm value(' ')
> >        callprc prc(getParm) rtnval(&parm)
> >      enddo
>
>_______________________________________________
>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.