|
Jean Claude, Glad to hear of your success. Three minor points that I'd just like to bring to your attention: 1. As the MQ API accepts a "pointer" (i.e. parm 7) on the MQPUT call, there are no restrictions in supplying an array, DS or field. This also applies to the MQPUT1 call. 2. I would caution against providing 9999 as your buffer-length (parm 6) as it wastes space and bandwidth. I have seen this have serious negative impact to overall throughout. 3. If you are providing 9999 as your buffer-length, the recipient must either provide for a 9999 message buffer on their MQGET or specify "accept truncated message" as part of their MQGMO structure. Regards, Michael Rooney Citigroup International -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of MITTELHEISSER Jean Claude Sent: Monday, June 21, 2004 9:47 AM To: Midrange Systems Technical Discussion Subject: RE: MQPUT and MQGET API Hi, What I have done : I use an array : E BUF 9999 1 So I can access each byte of BUF. And it works because MQPUT accepts this array as message data. If somebody is interested by the code of my program I can send it. Surely not optimized but it works. Thanks everybody. Best regards. -----Message d'origine----- De : midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx]De la part de Joe Pluta Envoyé : vendredi 18 juin 2004 19:03 À : 'Midrange Systems Technical Discussion' Objet : RE: MQPUT and MQGET API > From: MITTELHEISSER Jean Claude > > Thanks but I can't do that, because buffer has not a fixed structure. The > part I want to modify can be on position 15 one time and next time on > position 16. Jean Claude, have you tried using a BASED variable? D MyBuffer s 128 D MyPackedField s 5p 0 based(pField) /free pField = %addr(MyBuffer) + 15; MyPackedField = 123; /end-free This will update positions 16 thru 18 of the buffer with x'00 12 3F'. Joe -- 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. -- 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.