|
Jean Claude, The simplest approach would be to "map" the MQ buffer from MQGET to a data structure containing your defined subfields. You would then use this modified DS on your MQPUT. BTW: As a general rule, it isn't a good idea to pass packed fields in an MQ buffer as MQ won't know how to perform data translation. Obviously this isn't a problem between AS/400's but use caution when moving these types of messages between (or through) other platforms. Regards, Michael Rooney Citigroup International -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of MITTELHEISSER Jean Claude Sent: Friday, June 18, 2004 8:14 AM To: Midrange Systems Technical Discussion Subject: RE: MQPUT and MQGET API So I've started to write my first RPG/400 program on wednesday. I'm very glad because I'm still able to read a queue and to print some messages. However I have a little problem which can be resolved by any of you, I'm sure. I have a buffer which contains the message and I would like to overwrite a part of this buffer. But on program start, I don't even know were this part is. I find it by using SUBST. So I have the buffer and a pointer to the part in packed format. Best Regards. JC Mittelheisser -----Message d'origine----- De : midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx]De la part de Carl Galgano Envoyé : mardi 15 juin 2004 18:34 À : 'Midrange Systems Technical Discussion' Objet : RE: MQPUT and MQGET API The sample code is very helpful. About 6 months ago I had to write an entire, fairly complex communication system with the US Customs Service using MQ. I knew nothing about MQ. Using the sample code, a post or 2 here and Google I was able to write a rock solid comm system. We are very pleased with the way it works. cjg Carl J. Galgano EDI Consulting Services, Inc. 600 Kennesaw Avenue, Suite 400 Marietta, GA 30060 (770) 422-2995 - voice (419) 730-8212 - fax mailto:cgalgano@xxxxxxxxxxxxxxxxx http://www.ediconsulting.com AS400 EDI, Networking, E-Commerce and Communications Consulting and Implementation http://www.icecreamovernight.com Premium Ice Cream Brands shipped Overnight Visit our website to subscribe to our FREE AS/400 Timesharing Service -----Original Message----- From: Rooney, Michael P [mailto:michael.p.rooney@xxxxxxxxxxxxx] Sent: Tuesday, June 15, 2004 10:29 AM To: Midrange Systems Technical Discussion Subject: RE: MQPUT and MQGET API Jean Claude, Excellent. If I can be of assistance please feel free to contact me off line. Regards, Michael Rooney Citigroup International -----Original Message----- From: midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx]On Behalf Of MITTELHEISSER Jean Claude Sent: Tuesday, June 15, 2004 10:14 AM To: Midrange Systems Technical Discussion Subject: RE: MQPUT and MQGET API Hi Michael, My program is very simple : MQGET a non-synchronous message from a queue, post some data on this message and MQPUT this message to the next recipient. I have found IBM samples and with Carsten's utility, I hope I'll be able to write my first RPG program. Thank you all. Best Regards. JC Mittelheisser -----Message d'origine----- De : midrange-l-bounces@xxxxxxxxxxxx [mailto:midrange-l-bounces@xxxxxxxxxxxx]De la part de Rooney, Michael P Envoyé : mardi 15 juin 2004 15:13 À : Midrange Systems Technical Discussion Objet : RE: MQPUT and MQGET API Jean Claude, Generating and/or receiving MQ messages is the simple part. If you are attempting to integrate your AS/400 with your other Distributed MQ platforms may be more complex then simply putting and/or getting messages. For example, are the messages expecting replies? Do they use synchronous or asynchrounous "dialogue"? If replies are expected, how are they reconciled with requests (msgId or CorrelId)? What should happen to the messages in queue when the Queue Manager is stopped (i.e during IPL or maintenance)? My apologies if I appear to be "over engineering" but when (if) integrating MQ messages in a disparate environment such as yours, it is typically necessary (i.e. recommended) that participating applications, be they RPG, C, COBOL or JAVA, understand the respective life cycle and model of underlying messages. That said, as michaelr_41 suggests, the IBM-supplied examples provide an excellent starting point for learning/understanding the functionality of MQSeries. While I have never seen Carsten's utility, I'm confident, given his contributions to the AS/400 community, it also provides an excellent starting point for your MQ indoctrination. Respectfully, 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 14, 2004 3:52 AM To: midrange-l@xxxxxxxxxxxx Subject: MQPUT and MQGET API Hello, We have several systems like OS/390, AIX, Windows and OS/400 in our company. Most of them communicate through MQ Series. We have also a software which tests if these communications are OK by sending a message which is forwarded over our network from a machine to another. Each machine reads this message and sends it to the next. In case of a problem, sending stops and we know were the problem resides. We would like to include OS/400 in this testing but we have no real RPG competence to create programs in our company. So we would like to know if someone has developed around MQ Series to create perhaps a MQPUT and a MQGET command on OS/400, in any case a simple way to read and put messages on MQ Series queues. Thank You. Best Regards. -- 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. -- 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. -- 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.