|
If you're talking external program calls then you're basically correct. MI is the exception as it can pass/receive parms by value. It sounds like MQ series uses an ILE procedure interface. I would expect large parameters like a buffer to be passed as a pointer. Not very efficient to pass a buffer by value. The buffer parm is likely defined as either a "pointer by value" or a "varsize field by reference". Actually both of these are the effectively the same (pointer to data). Keith ----- Original Message ----- From: "jt" <jt@xxxxxx> To: "Midrange Systems Technical Discussion" <midrange-l@xxxxxxxxxxxx> Sent: Monday, March 22, 2004 8:35 AM Subject: RE: Record size limitation in RPG - MQ Series > If doing this in RPG, when RPG passes a parm it is actually passing a > pointer TO the parm. This is because RPG passes parms "by reference" rather > than "by value", normally. (I don't recall, right now, if RPG even CAN pass > by value, but think that mebbe was added with CONST or some such.) I dunno > MQ, however, but sounds like you just pass the variable-name and it'll work. > > | -----Original Message----- > | [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of Carl Galgano > | Sent: Monday, March 22, 2004 10:58 AM > > | How do you pass the > | pointer to a user > | space to the MQPUT? There is an API to call to do the MQPUT, but I don't > | know how to pass the pointer. > > > _______________________________________________ > This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list > To post a message email: MIDRANGE-L@xxxxxxxxxxxx > To subscribe, unsubscribe, or change list options, > visit: http://lists.midrange.com/mailman/listinfo/midrange-l > or email: MIDRANGE-L-request@xxxxxxxxxxxx > 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.