|
This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] Are you exporting a variable and not the subprocedure? If this is truly the entire D specs from the service program then this is what you are doing. And it seems like only a week ago if someone asked if anyone is exporting a variable in any of their service programs. 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 10:40 AM Please respond to midrange-l To: "MIDRANGE-L" <MIDRANGE-L@midrange.com> cc: Fax to: Subject: RE: CALLPRC with RTNVAL 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.
As an Amazon Associate we earn from qualifying purchases.
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.