| Author |
Message
|
| zpat |
 Posted: Thu Mar 09, 2006 12:36 am Post subject: REXX/MQ on z/OS and MATCH_CORREL_ID |
 |
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
I am using the REXX interface for MQ on z/OS (MA18), which is great but I can't seem to find out how to do a MQGET with MQMO_MATCH_CORREL_ID to select a message by CORRELID.
Anyone know if this is supported in MA18? |
|
| Back to top |
|
 |
| Mr Butcher |
| Posted: Thu Mar 09, 2006 12:46 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
it should work, please show your code....
_________________
Regards, Butcher |
|
| Back to top |
|
|
| zpat |
| Posted: Thu Mar 09, 2006 12:53 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Well it's just that the MA18 documentation does not mention MQMO_MATCH_CORREL_ID at all, and does not give any examples of selecting messages by id.
However I think this is something to do with MA18 predating MQGMO_VERSION_2 which introduced the match options field.
I think if I set the Correlid value in the MQMD it will automatically match without the need to code MQMO_MATCH_CORREL_ID. |
|
| Back to top |
|
|
| Mr Butcher |
| Posted: Thu Mar 09, 2006 1:18 am Post subject: |
|
|
Padawan
Joined: 23 May 2005
Posts: 1716
|
i think so too.
please notice that MA18 is withdrawn, so its nice to use it for some tests and to play around a little, but i would not expect new features being implemented in ma18 (its quite old...)
_________________
Regards, Butcher |
|
| Back to top |
|
|
| zpat |
| Posted: Thu Mar 09, 2006 1:31 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
REXX remains a key feature of z/OS, so why does IBM withdraw MQI support for it?
It would be helpful for IBM to release the source code of support pacs if they don't want to support them. |
|
| Back to top |
|
|
| bob_buxton |
| Posted: Thu Mar 09, 2006 2:08 am Post subject: |
|
|
Master
Joined: 23 Aug 2001
Posts: 266
Location: England
|
Remember you don't need to use MQMO_MQMO_MATCH_CORREL_ID since the default is MQMO_MATCH_CORREL_ID+MQMO_MATCH_MSG_ID.
Just set the input correlid field to the desired value and the message id to MQMI_NONE.
There are a number of reasons why support for MA18 was dropped which I am not prepared to discuss here.
Making the source available would not be helpful since it was written in PL/X, IBM's internal systems programming language. Compilers for this are not widely available.
However C source for the distributed platforms versions of the support packs is, I believe, included with them. It should be possible to port this code to z series.
A SMOP  - is anybody up to the challenge? 
_________________
Bob Buxton
Ex-Websphere MQ Development |
|
| Back to top |
|
|
| zpat |
| Posted: Thu Mar 09, 2006 2:59 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
MA18 was/is a superb piece of work. Seems a waste to withdraw it but it still works, so I'll keep using it for prototyping.
Similarly I was disappointed to see the Lotuscript MQLSX withdrawn, since Lotuscript is still supported.
It's handy to have MQI support in interpreted languages for quick development and prototyping. |
|
| Back to top |
|
|
|
|
