|
Found the answer, of all places in the CL Programming manual. RTFM, eh? Use RTNVAL(%BIN(&RTNVAL 1 4)). At 09:21 PM 3/30/02 -0600, you wrote: >I've had trouble recently, too. On V5R1. Tried to use RTNVAL with a *CHAR 4 >with a function that is supposed to return an integer (4-byte). Works fine >in C, of course, but garbage in CLLE. > >At 10:34 AM 3/30/02 -0500, you wrote: >>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 >> >>The srvpgm (RPG) returns the correct data, and works fine when called by an >>RPG pgm. The srvpgm exports the parm. >> >>The problem is the value of parm is not correct. >> >>Can anyone tell me what I've got wrong? >> >>Thanks, >> >>Phil >> >> >> >>_______________________________________________ >>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. > >_______________________________________________ >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.