Copying MSG_TYPE from the get to the send message is not necessarily correct. It is an arbitrary positive number that MSGSND sends to the receiver. The receiver may use this information any way it desires. It is simply a standard. E.g. Think about MVS SMF record types. Everyone agree's on the values and how they will be used. MSG_TYPE is similar but each queue may have it's own meaning for the values that it represents..
When using the MVS interfaces to UNIX functionality, you should also look at the UNIX documentation for the UNIX version of the interface. That documentation is heavily used and more complete because of usage. In this case, you would immediately see a structure that contains the TYPE and message where as MVS gives you an IMPORTANT note that says the TYPE is the first word preceding the message. The MVS versions simply don't get enough use and users often already know the functionality from using the UNIX version. Jon Perryman. >________________________________ > From: "esst...@juno.com" <esst...@juno.com> > > >The issue with the Reason Code has to do with the setting >of the MSG_TYPE. The documentation does not expalin it well enough that the >MSG_ID returned from BXP1QGT needs to be stored in the MSG_TYPE field prior to >the MSG_TEXT before issuing BPX1QSND. I can noe WRITE and RED from the queue. > ---------------------------------------------------------------------- For IBM-MAIN subscribe / signoff / archive access instructions, send email to lists...@listserv.ua.edu with the message: INFO IBM-MAIN
