|
corretion: here is how I call the procedure: callp $rtvRef('USR' :@userID :DSTUSR) note: DSTUSR is a data structure. The procedure will work correctly, if I change the caller program to define DSTUSR as a char field. -----Original Message----- From: Lim Hock-Chai Sent: Wednesday, December 18, 2002 9:52 AM To: midrange-l@midrange.com Subject: RE: CEEDOD here is how I call the procedure: callp $rtvREFERP('USR' :@userID :DSTUSR) note: DSTUSR is a data structure. The procedure will work correctly, if I change the caller program to define DSTUSR as a char field. -----Original Message----- From: Joe Pluta [mailto:joepluta@PlutaBrothers.com] Sent: Wednesday, December 18, 2002 10:03 AM To: midrange-l@midrange.com Subject: RE: CEEDOD > From: Lim Hock-Chai > > The caller did pass all three parms when I was testing it. > However, the parm I passed is a data structure. I did later find > an discussion about CEEDOD wILL not work if the parm being passed > is a data structure. That particular discussion was date Jul > 1999. I wonder if IBM has corrected the problem. This is not an IBM problem. Your procedure expects three parameters. You cannot pass a single data structure and expect it to satisfy those three parameters. You can do one of the following: 1. Send each parameter individually 2. Change the prototype to accept only a single data structure 3. Add an interface procedure that accepts a data structure and passes the elements of that data structure to the original procedure Be very clear on this: you cannot pass a data structure to a procedure that is expecting multiple values. Joe _______________________________________________ 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.