|
Rich, Sorry to disagree, but the QMHRDQM API most certainly exists on V2R3 machines. Perhaps you overlooked it because it is documented in the CL Programmer's Guide, which is where most of the data queue APIs were documented back then. - Lou Forlini Software Engineer System Support Products, Inc. At 11:48 AM 3/20/98 -0600, "Rich Duzenbury" <rduz@aros.net> wrote: >HAHAHA! I'm glad there is an API for this task now, but, I can't seem to >find it on my V2R3 machine! > > >Regards, >Rich > >============================================ >Rich Duzenbury >http://rich.dyn.ml.org >http://vpsolutions.com >============================================ >-----Original Message----- >From: bvining@VNET.IBM.COM <bvining@VNET.IBM.COM> >To: MIDRANGE-L@midrange.com <MIDRANGE-L@midrange.com> >Date: Friday, March 20, 1998 11:03 AM >Subject: MI Programming > > >>Rich, >> >>Though I realize your view example was just that, an example, I can't >>resist the opportunity to plug the Retrieve Data Queue Message (QMHRDQM) >>API which provides a non-destructive read of one or more messages from >>a data queue. >> >>I do agree with you that MI is still a viable and effective mechanism >>for solving some of the problems developers run into. Prior to V4R2 >>for instance, MI was the only way to access system mutex support. >> >>Bruce Vining >> >>> >>>... >>>In general, I use MI only when a job cannot be done in RPG or CL at all, >or >>>sometimes cleanly. As an example, some time ago I needed to view the >>>contents of a data queue, and no mechanism was available. Certainly I >could >>>have pulled each entry off the queue, and then re-inserted it, but that >>>caused sequencing problems. I could have also dumped the queue object, >and >>>tried to interpret the spooled file. I considered these methods messy >>>solutions at best. A clean solution, IMO, was an MI program written >around >>>MATQMSG. >>> >>>So, I believe MI is still a viable and effective mechanism for solving >>>problems, thus my desire to be proficient. >>> >>>Regards, >>>Rich +--- | This is the Midrange System Mailing List! | To submit a new message, send your mail to MIDRANGE-L@midrange.com. | To unsubscribe from this list send email to MIDRANGE-L-UNSUB@midrange.com. | Questions should be directed to the list owner/operator: david@midrange.com +---
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.