| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
| MQ and CICS and REXX |
« View previous topic :: View next topic » |
| Author |
Message
|
| jefflowrey |
 Posted: Mon Nov 27, 2006 7:57 am Post subject: |
 |
|
Grand Poobah
Joined: 16 Oct 2002
Posts: 19981
|
I'm sure it's not a process based on whim. It is, perhaps, somewhat insulting to suggest that it could be. I'm not offended, but I think some of the lab folks might not take the suggestion entirely kindly.
On the flip side of things, I wonder if zpat can just call regular CICS MQ API calls from CICS/REXX - and that this is why the support pack was withdrawn, as it was no longer needed.
But, hey, I'm not a mainframe person, nor a CICS person nor a REXX person, nor even a Support Pack person, so I don't know.
As for procedures for raising requirements - I think that starts with a phone call to your IBM sales rep?
_________________
I am *not* the model of the modern major general. |
|
| Back to top |
|
 |
| zpat |
| Posted: Mon Nov 27, 2006 8:05 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
I've not found a way to call the MQI from CICS/REXX.
REXX is the main scripting language for z/OS and as such it should really have a supported interface to the MQI.
We still reply on the MA18 support pac for some production purposes as well as development prototyping and some utilities.
I am OK with using it because it's never had any problems (Robert Harris deserves recognition for a superb piece of programming), but obviously the newer MQI features are not available.
I can see the point of releasing support pacs as-is with source code, but withdrawing OCO ones does leave users in a potential hole.
We also heavily use the MQLSX in production which has also been withdrawn (This is the Lotuscript MQI). |
|
| Back to top |
|
|
| tleichen |
| Posted: Mon Nov 27, 2006 1:41 pm Post subject: |
|
|
Yatiri
Joined: 11 Apr 2005
Posts: 663
Location: Center of the USA
|
| jefflowrey wrote: |
| I'm sure it's not a process based on whim. It is, perhaps, somewhat insulting to suggest that it could be. I'm not offended, but I think some of the lab folks might not take the suggestion entirely kindly. |
I did not mean to offend. The remark was simply meant to imply my own ignorance of this process. So far as I can recollect, I have never seen an MQ supportpac that was ever changed to a higher category of support than the one it was introduced with. However, I don't claim to have kept up with all of them by any means. I have often thought though, over the years, that so many of the most useful supportpacs were often presented "as-is". I'm not certain that this is purely coincidental.
| zpat wrote: |
I've not found a way to call the MQI from CICS/REXX..
...
We also heavily use the MQLSX in production which has also been withdrawn (This is the Lotuscript MQI). |
It's amazing that much of this stuff is not more cohesive than it is. It would seem, at least in theory, that it would not be that difficult for a vendor to keep all their ducks in a line, if they're willing to maintain them. The whole philosophy of MQSeries has always been one of a messaging transport that should work anywhere. So, it still seems surprising that with all the "other" platforms that MQSeries is now running on, that IBM would choose to alienate some of its own.
_________________
IBM Certified MQSeries Specialist
IBM Certified MQSeries Developer |
|
| Back to top |
|
|
|
|
|
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
