| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| IH03 MQPUTSC.EXE and W10 |
« View previous topic :: View next topic » |
| Author |
Message
|
| zpat |
 Posted: Wed Jun 02, 2021 2:29 am Post subject: IH03 MQPUTSC.EXE and W10 |
 |
|
Jedi Council
Joined: 19 May 2001
Posts: 5849
Location: UK
|
Windows 10, MQ v9.2 (full), MQPUTSC.EXE
I am using IH03 version 7.5 and getting 2059 trying to connect to a z/OS QM using the MQPUTSC utility.
It may be trying to use a binding connection not a client connection.
How can I get the latest binary (I cannot compile anything) for MQPUTS/C (and for that matter the rest of IH03)?
NB: Those who upload to GITHUB - please supply binaries ready to use - do NOT assume users can compile source code.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
 |
| markt |
| Posted: Wed Jun 02, 2021 3:19 am Post subject: |
|
|
Knight
Joined: 14 May 2002
Posts: 502
|
See https://github.com/ibm-messaging/mq-rfhutil for the package. The README tells what's there.
Source is there and some Windows binaries, though it's usually expected these days that you should be able to build github packages yourself. Apart from anything else, it's one way of ensuring a) you know what you're running and b) it matches your environment.
There are too many variations in some platforms that it's not always practical, outside of a full (expensive) product release/test environment, to give binaries that work for everyone. Makefiles, Dockerfiles, scripts etc are usually provided to assist with building. My personal machine might have newer levels of some component that make a binary unrunnable on an older level of OS.
As with all programs that aren't explicitly coded to act one way or the other, you can set MQ_CONNECT_TYPE=CLIENT env var to force client mode. So there's no need for xxxxC.exe variants of the programs. |
|
| Back to top |
|
|
| zpat |
| Posted: Wed Jun 02, 2021 4:39 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5849
Location: UK
|
If you could upload (no warranty implied) binaries for the most common environments (Windows and Linux on intel) it would help many users.
MQ admins are not developers (in the main) and I simply never normally have any need to compile source code (and literally do not know how to. nor have any license for a compiler).
Alternatively an idiots guide to using a freeware (GNU?) compiler might be enough (showing what options to use).
However I have now got mqputsc to work with the version that I have by using SETMQENV -n and pointing it to a MQ Client installation name.
MQ_CONNECT_TYPE=CLIENT didn't work, I am guessing that came in after the version I have (probably the last support pac version).
I don't really know how to use GITHUB either, I just want a single ZIP file with everything in like in the good old support pac days...
Thanks
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| hughson |
| Posted: Thu Jun 03, 2021 2:52 am Post subject: |
|
|
Padawan
Joined: 09 May 2013
Posts: 1914
Location: Bay of Plenty, New Zealand
|
| zpat wrote: |
| MQ_CONNECT_TYPE=CLIENT didn't work, I am guessing that came in after the version I have (probably the last support pac version) |
The last support pac version of the MQ client was V9.1.
MQ_CONNECT_TYPE=[ CLIENT | LOCAL ] came in at V7.1 (at the same time as "smart libraries", i.e can make client connection using mqm library). So long as you have a version of MQ that is at least V7.1, MQ_CONNECT_TYPE should work fine.
In case you're spelling it wrong or something (not apparent from your post), here's a post about it with a how-to to get it working with amqsput
IBM MQ Little Gem #30: MQ_CONNECT_TYPE
Maybe try that out and then once it is correctly set up, try again with mqputs
Cheers,
Morag
_________________
Morag Hughson @MoragHughson
IBM MQ Technical Education Specialist
Get your IBM MQ training here!
MQGem Software |
|
| Back to top |
|
|
| zpat |
| Posted: Thu Jun 03, 2021 4:48 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5849
Location: UK
|
I meant I was using the last support pac version of IH03.
I have MQv9.2 full and MQv9.1 client installations.
Is SET in the current command window enough or does this var have to be set in windows settings?
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| bruce2359 |
| Posted: Thu Jun 03, 2021 5:11 am Post subject: |
|
|
Poobah
Joined: 05 Jan 2008
Posts: 9396
Location: US: west coast, almost. Otherwise, enroute.
|
The SET command (and EXPORT in UNIX) is for this shell only.
_________________
I like deadlines. I like to wave as they pass by.
ב''ה
Lex Orandi, Lex Credendi, Lex Vivendi. As we Worship, So we Believe, So we Live. |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
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
|
|
|
|
