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
+---