| Author |
Message |
 Topic: Different client/server conn behavior: v9.4 LTS vs CD |
rekarm01
Replies: 3
Views: 598
|
 Forum: IBM MQ API Support Posted: Wed Mar 04, 2026 11:17 am Subject: Re: Different client/server conn behavior ... |
| Thanks for your reply. Our original goal was to (transparently) use an existing user application, (compiled with -lmqm), with either local or client connections, but it wasn't working for client conn ... |
| Topic: Different client/server conn behavior: v9.4 LTS vs CD |
rekarm01
Replies: 3
Views: 598
|
Forum: IBM MQ API Support Posted: Fri Feb 27, 2026 7:10 pm Subject: Different client/server conn behavior: v9.4 LTS vs CD |
We had one MQ installation (v9.4 LTS) on Linux, ($ LD_LIBRARY_PATH='/usr/lib64/' MQSERVER='RMT.SVRCONN/TCP/HostName(PortNum)' ./amqsgbr QueueName RmtQMgrName
Sample AMQSGBR0 (browse) ... |
| Topic: JSON Parsing error |
rekarm01
Replies: 6
Views: 40356
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Mar 08, 2024 2:05 pm Subject: JSON Parsing error |
| For ace12, the server.conf.yaml file provides a JSON parser property, '[url=https://www.ibm.com/docs/en/app-connect/12.0?topic=command-parameter-values-json-parser]numberPrecisionType', (instead of an ... |
| Topic: MRM message set generates toolkit error instead of warning |
rekarm01
Replies: 1
Views: 6519
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri May 12, 2023 2:07 pm Subject: Re: MRM message set generates toolkit error instead of warni |
The message set validation levels are configurable from the toolkit menu bar: Window -> Preferences -> Integration Development -> Message Sets -> Validation .
But different fix packs ha ... |
| Topic: MRM message set generates toolkit error instead of warning |
rekarm01
Replies: 1
Views: 6519
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri May 12, 2023 9:18 am Subject: MRM message set generates toolkit error instead of warning |
| We are in the process of migrating message flows from iib10 to ace12, some of which still include MRM message sets for SOAP. We may go back and replace the MRM message set with a message model (schem ... |
| Topic: Keywords not visible in deployed shared library in ACE12 |
rekarm01
Replies: 2
Views: 3886
|
Forum: WebSphere Message Broker (ACE) Support Posted: Fri Oct 07, 2022 12:39 pm Subject: Re: Keywords not visible in deployed shared library in ACE12 |
| ACE v12.0.6.0 includes a fix (APAR IT41593), so that mqsilist displays the full path for barfiles deployed using the Integration API. It should no longer be necessary to use keywords as a workaround ... |
| Topic: Is NTLM authorization supported in WMB 8.0.0.4? |
rekarm01
Replies: 3
Views: 3892
|
Forum: WebSphere Message Broker (ACE) Support Posted: Wed Aug 24, 2022 3:18 pm Subject: Re: Is NTLM authorization supported in WMB 8.0.0.4? |
Upgrading WMB is not an option.
Does that include even applying the latest fixpack for wmb8? Perhaps that had support for NTLM authentication.
Another option is to replace the SOAP nodes with HTT ... |
| Topic: User Exit sample code |
rekarm01
Replies: 9
Views: 7996
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Feb 01, 2022 6:42 pm Subject: Re: User Exit sample code |
... never written c language code before ...
Find a C programmer to write the user exit. C can get tricky.
We are installing app dynamic tool for IIB ... please share sample user exit file for mo ... |
| Topic: How to find negotiated MAXMSGL for client channel |
rekarm01
Replies: 3
Views: 8293
|
Forum: General IBM MQ Support Posted: Sun Jan 30, 2022 9:27 pm Subject: Re: How to find negotiated MAXMSGL for client channel |
Thanks for the responses, but I still have some questions ...
First off, max message length is limited to the base 2 value for 100 MB, which is 104,857,600 bytes. I suspect that's where you're gett ... |
| Topic: How to find negotiated MAXMSGL for client channel |
rekarm01
Replies: 3
Views: 8293
|
Forum: General IBM MQ Support Posted: Thu Jan 27, 2022 6:06 pm Subject: How to find negotiated MAXMSGL for client channel |
| On our MQ server, we defined a QMGR with MAXMSGL set to 104 MB, and also defined a SVRCONN channel with MAXMSGL set to 104 MB. And on our application server we created a JSON CCDT file to connect to ... |
| Topic: Packed decimal conversion issue |
rekarm01
Replies: 16
Views: 73270
|
Forum: Mainframe, CICS, TXSeries Posted: Wed Oct 27, 2021 5:55 pm Subject: Packed decimal conversion issue |
Is this Java, or JMS? If it's JMS, then is it a TextMessage, or a BytesMessage?
I think i found the root cause of the issue. It is the character encoding used which is changing the byte stream.
N ... |
| Topic: How to set Timestamp multiple times in ESQL |
rekarm01
Replies: 15
Views: 24764
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sun Oct 03, 2021 3:22 pm Subject: Re: How to set Timestamp multiple times in ESQL |
Nope, just for getting system timestamp suggesting to use Java its not good one.
You can use PASSTHRU to achieve this
Or, just create a [url=http://www.mqseries.net/phpBB2/viewtopic.php?p=413269#4 ... |
| Topic: MRM converting xml attributes to elements |
rekarm01
Replies: 11
Views: 9144
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Jul 06, 2021 10:56 am Subject: Re: MRM converting xml attributes to elements |
I've seen libraries and applications when we upgraded to v8 but we never get on the task of updating all existing flows and sub-flows.
Until then, message flows in Integration projects can also use m ... |
| Topic: Bad chars : reason to fail |
rekarm01
Replies: 14
Views: 12718
|
Forum: WebSphere Message Broker (ACE) Support Posted: Tue Jun 08, 2021 2:41 pm Subject: Re: Bad chars : reason to fail |
What actually works is this small ESQL:
SET contents = ASBITSTREAM(InputRoot.MRM
CCSID InputRoot.Properties.CodedCharSetId
ENCODING InputRoot.Properties.Encoding
... |
| Topic: Bad chars : reason to fail |
rekarm01
Replies: 14
Views: 12718
|
Forum: WebSphere Message Broker (ACE) Support Posted: Sun Jun 06, 2021 1:12 pm Subject: Re: Bad chars : reason to fail |
Is there any way to force failure on FileInput node if the characters are not ASCII?
No. The FileInput node just copies bytes from the file to assemble the source message. Some downstream component ... |
