Barton, Linda | 25 Mar 15:01 2015
Picon

rulestable processing

I have a frustrating issue with the rulestable not handling messages in the DEAD queue.
Let’s say I have a qmgr QMGRA and QMGRA.DEAD.QUEUE.
My rulestable has these lines:
 
****************************************
* Control data entry
****************************************
 
inputqm(' ') inputq(' ')
 
REASON(2052) ACTION(DISCARD) RETRY(5)
REASON(MQRC_Q_FULL) ACTION(RETRY) RETRY(5)
REASON(MQRC_PUT_INHIBITED) ACTION(RETRY) RETRY(5)
 
And for good measure
DESTQ(AMQ*) ACTION(DISCARD)
 
The offending message I am trying to discard is as follows:
 
You can see that the Backout count is 1 so the ruletable tried to process it, but it did not discard it.  I can’t tell what is going on with this because nothing is logged except this message in the error log: AMQ8708: Dead-letter queue handler started to process INPUTQ.
 
I have other rules in there that have been working fine.  Why can’t I discard this message?  We tried running the rulestable to a stdout log but that does not do anything.
Any suggestions?
 
 
Linda Barton
Liberty Mutual Insurance
 
 
 
 

List Archive - Manage Your List Settings - Unsubscribe

Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com

Thomas, Don | 23 Mar 16:53 2015
Picon

z/OS Cluster questions

Hello Lister,

 

                I am in the midst of a large MQ migration involving Unix and z/OS based MQ environments. Currently I am working on the z/OS portion. This is the current situation. The client has basically “recovered” their LPARs  and Unix servers onto new hosts. Very much like a disaster recovery exercise. The first environment that I’m addressing consists of one queue manager on z/OS that is holding the only FR for a MQ cluster that includes four Unix based queue managers. (Not my design, I know 1 FR is NOT a good idea, I’ll deal with that later.) The existing MQ environment is still being used in the old environment. On the Unix side I’ll be creating all new queue managers with new queue manager names holding all of the existing queues, etc. The old Unix queue managers are not currently running and I really would rather not start them. On the z/OS side the old queue manager name is going to continue to be used (too many lines of code to change is what I was told) and it is currently running. My plan is to dismantle the existing MQ cluster and then recreate it with a new name but with the same clustered components, i.e. queues, that currently exist. Here is my plan to accomplish this:

 

Alter all of the mainframe based clustered queues to CLUSTER(‘ ‘)

 

Remove the Unix based queue managers from the cluster:

RESET CLUSTER(OLDCLUSTER) QMNAME(OLDQMGR01,02, 03, 04) ACTION(FORCEREMOVE) QUEUES(YES)

 

Alter the CLUSRCVR channel TO.zOSQMGR to CLUSTER(‘ ‘)

 

At this point I have a couple of questions. There are messages on the z/OS queue manager’s SCTQ. Can I simply CLEAR the queue? I do not want or need any of those messages.

Now, provided that I can/do CLEAR the SCTQ, I’m thinking that at this point the cluster OLDCLUSTER no longer exists in the new environment. Is that a reasonable assumption? Am I going to have to delete any Auto Cluster SENDER channels or will the RESET CLUSTER FORCEREMOVE take care of that or is there another step that I need to do?

 

Then it’s just a matter of creating the new cluster.

 

Has anyone been in a similar situation before? Does any see any glaring errors in my approach?

Any suggestions or comments would greatly appreciated.

 

MQ is at V7.0.1.10 for all queue managers.

 

TIA,

 

Don Thomas
ES Apps Development US

dont-VXdhtT5mjnY@public.gmane.org
M +1 412 577 8005

 


List Archive - Manage Your List Settings - Unsubscribe

Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com

Costa, D. (Damian | 21 Mar 17:57 2015
Picon

performance of client connection on a queue written to by a recevier channel

Hi all,

We’re battling with a performance issue:

A local Q is written to from a remote qmgr .

An application reads off said queue via a client channel.

 

The writing receiver channel  writes at 10 records per second, over 15 minutes 10291 messages written to the queue.   Over that time the queue depth slowly grows to 1950 records.

The moment the writing application stops it’s feed the reading app then blitzes through the remaining queue depth of 1983 msgs  at 30 records a second .

It seems like the reader app is being impeded by the writing receiver channel .

 

What can I look at the see why the reader app is not keeping up while the queue is being written to?

 

I ran a  trace during the test  to track everything.   I am really hoping the trace does not impede the reading app more than the writing app.

 

Channels are configured to connect as fastpath:

Channels:

   MQIBINDTYPE=FASTPATH

 

Thanks.

 

 

 

 

 


********************
Nedbank Limited Reg No 1951/000009/06. The following link displays
the names of the Nedbank Board of Directors and Company Secretary.
[ http://www.nedbank.co.za/terms/DirectorsNedbank.htm ]
This email is confidential and is intended for the addressee only.
The following link will take you to Nedbank's legal notice.
[ http://www.nedbank.co.za/terms/EmailDisclaimer.htm ]
********************


List Archive - Manage Your List Settings - Unsubscribe

Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com

Roger Lacroix | 20 Mar 17:32 2015

MQ Properties via Java application

All,

I have a very weird problem.  I have a MQ Java application that is setting MQ properties and it works fine on MQ v7.5.0.2 and v8.0.0.0.  It only fails with Reason Code of 2142 (MQRC_HEADER_ERROR) on a Windows running MQ v7.5.0.3.  Yes, a PMR was opened with IBM but so far they are not very helpful.

The MQ Java application is running on Windows MQ v7.5.0.3 (I have verified that the MQ JAR are in fact v7.5.0.3) and is connecting to a queue manager running on Linux.  Here is what the code looks like:

MQPutMessageOptions pmo = new MQPutMessageOptions();
pmo.options = CMQC.MQPMO_FAIL_IF_QUIESCING;
MQMessage sendMsg = new MQMessage();
sendMsg.messageId    = CMQC.MQMI_NONE;
sendMsg.correlationId= CMQC.MQCI_NONE;
sendMsg.messageType  = CMQC.MQMT_DATAGRAM;
sendMsg.format       = CMQC.MQFMT_NONE;
sendMsg.setStringProperty("UFM_Directory", "/home/roger/upload/");
sendMsg.setStringProperty("UFM_FileName", "test1.txt");
sendMsg.write("This is a test message".getBytes());
outQ.put(sendMsg, pmo);

The MQ Knowledge Center does not have a lot of information for RC of 2142 although it says not to set CCSID to MQCCSI_Q_MGR, so I removed that line of code but the problem persist.

No matter what other server I run the code on it works just fine.  Has anybody ever had issues with setting MQ properties?

I'm trying to figure out if it is the MQ Client that is generating the RC of 2142 or if it is the MQ Server.  Does anyone know how to figure that out?  I need to give IBM Support as much information as possible (they have MQ trace files but getting them to look at the files is difficult).

Regards,
Roger Lacroix
Capitalware Inc.


List Archive - Manage Your List Settings - Unsubscribe

Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com

Thomas, Don | 17 Mar 22:33 2015
Picon

Re: FW: MQ symbolic links in /usr/lib for MQ7.0.1.10 on Solaris 10

Hi Phillip,
	Thanks for the reply. It does help. Apparently the Unix SA ran the silent install for the base, but when
applying the maintenance he was only selecting the client. What really confuses me though is that after
the install I was able to create and configure queue managers. I guess none of that activity required a call
to libimqs23as.so.

Thanks again, you got me pointed in the right direction.

Don

-----Original Message-----
From: MQSeries List
[mailto:MQSERIES@...] On Behalf Of
Philip Morten
Sent: Monday, March 16, 2015 6:21 PM
To: MQSERIES@...
Subject: Re: FW: MQ symbolic links in /usr/lib for MQ7.0.1.10 on Solaris 10

Don,

libimqs23as.so is a server library
libimqc23as.so is client
libimqb23as.so is from the common runtime.

So I would infer the first system listed has both the client and server installed while the second one has
only the client.  Both have the common runtime.

The components installed can be seen by using the Solaris command
	pkgparam mqm CLASSES
as shown below.

spleen  / # pkgparam mqm CLASSES
none runtime  base gskit java jre man samples server sol_client

Hope this helps.

--
Philip Morten

On 16/03/2015 18:59, Thomas, Don wrote:
> Hi Listers,
>
>                  I've included the below listing to show some 
> specifics about the issue I'm seeing with the installs.
>
> [mqm <at> Goodserver:/tmp] ls -l /usr/lib | grep 23as
>
> lrwxrwxrwx   1 root     other         27 Mar 16 10:42 libimqb23as.so ->
> /opt/mqm/lib/libimqb23as.so
>
> lrwxrwxrwx   1 root     other         27 Mar 16 10:42 libimqc23as.so ->
> /opt/mqm/lib/libimqc23as.so
>
> lrwxrwxrwx   1 root     other         27 Mar 16 10:42 libimqs23as.so ->
> /opt/mqm/lib/libimqs23as.so
>
> [mqm <at> Badserver:/tmp] ls -l /usr/lib | grep 23as
>
> lrwxrwxrwx   1 root     other         27 Feb 27 18:53 libimqb23as.so ->
> /opt/mqm/lib/libimqb23as.so
>
> lrwxrwxrwx   1 root     other         27 Feb 27 18:53 libimqc23as.so ->
> /opt/mqm/lib/libimqc23as.so
>
> I can't figure out why there is a missing link for the one server. Has 
> anyone seen this before?
>

To unsubscribe, write to LISTSERV@...
and, in the message body (not the subject), write: SIGNOFF MQSERIES Instructions for managing your
mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com
Archive: http://listserv.meduniwien.ac.at/archives/mqser-l.html

To unsubscribe, write to LISTSERV@... and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Thomas, Don | 16 Mar 19:59 2015
Picon

FW: MQ symbolic links in /usr/lib for MQ7.0.1.10 on Solaris 10

Hi Listers,

                I’ve included the below listing to show some specifics about the issue I’m seeing with the installs.

 

[mqm <at> Goodserver:/tmp] ls -l /usr/lib | grep 23as

lrwxrwxrwx   1 root     other         27 Mar 16 10:42 libimqb23as.so -> /opt/mqm/lib/libimqb23as.so

lrwxrwxrwx   1 root     other         27 Mar 16 10:42 libimqc23as.so -> /opt/mqm/lib/libimqc23as.so

lrwxrwxrwx   1 root     other         27 Mar 16 10:42 libimqs23as.so -> /opt/mqm/lib/libimqs23as.so

 

[mqm <at> Badserver:/tmp] ls -l /usr/lib | grep 23as

lrwxrwxrwx   1 root     other         27 Feb 27 18:53 libimqb23as.so -> /opt/mqm/lib/libimqb23as.so

lrwxrwxrwx   1 root     other         27 Feb 27 18:53 libimqc23as.so -> /opt/mqm/lib/libimqc23as.so

I can’t figure out why there is a missing link for the one server. Has anyone seen this before?

 

Regards,

Don

 

From: Thomas, Don
Sent: Monday, March 16, 2015 1:02 PM
To: MQSERIES-0lvw86wZMd9k/bWDasg6f+2wyY2g16FtwPuJ0ROkVbw@public.gmane.org
Subject: MQ symbolic links in /usr/lib for MQ7.0.1.10 on Solaris 10

 

Hi listers,

                Does anyone know if there is any documentation that lists what links MQ will install in /usr/lib on a Solaris 10 during a full installation? I have several new servers I’m trying to migrate to. I’m using the same install software on all of them but I seem to be getting different results. The mq.install file on all servers is showing different results, yet they all indicate that the install was successful.

 

Don Thomas
ES Apps Development US

dont-VXdhtT5mjnY@public.gmane.org
M +1 412 577 8005

 


List Archive - Manage Your List Settings - Unsubscribe

Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com

Thomas, Don | 16 Mar 18:01 2015
Picon

MQ symbolic links in /usr/lib for MQ7.0.1.10 on Solaris 10

Hi listers,

                Does anyone know if there is any documentation that lists what links MQ will install in /usr/lib on a Solaris 10 during a full installation? I have several new servers I’m trying to migrate to. I’m using the same install software on all of them but I seem to be getting different results. The mq.install file on all servers is showing different results, yet they all indicate that the install was successful.

 

Don Thomas
ES Apps Development US

dont-VXdhtT5mjnY@public.gmane.org
M +1 412 577 8005

 


List Archive - Manage Your List Settings - Unsubscribe

Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com

T.Rob | 14 Mar 20:58 2015

Phishing warnings

Hi listers,

 

I've started getting consistent phishing warnings for traffic from this list, in many cases when the only links are in the footer at the bottom - meaning it is the list itself that is considered suspicious.  If you are seeing these warnings, ESPECIALLY if using Office 365 or any Outlook web-hosted email, please add the domain MEDUNIWIEN.AC.AT to the Safe Senders list.  Same thing if you use hosted POP or IMAP and these are landing in your junk folder.

 

There is a slight possibility that the list could end up on one of the spam blacklists causing it to wink out of existence.  Notifying the filtering providers by adding the domain to the Safe Sender's List or using the "this is not junk" option when retrieving emails from the junk folder is like voting for the list to remain available.

 

Kind regards,

-- T.Rob

 

I have availability! For a good time (with IBM MQ) call:

T.Robert Wyatt, Managing partner

IoPT Consulting, LLC

+1 704-443-TROB (8762) Voice/Text

+44 (0) 8714 089 546  Voice

https://ioptconsulting.com

https://twitter.com/tdotrob

 


List Archive - Manage Your List Settings - Unsubscribe

Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com

Ravi Kumar Patnaik Balivada | 14 Mar 19:10 2015
Picon

How to change the install directory after applying wmb patch

Hi team,

I have installed wmb 8.0.0.0 on aix environment and the installation directory shows /opt/ibm/mqsi/8.0.0.0.

Now I have applied wmb patch 8.0.0.5 on the same installation directory.

Now mqsiservice  - v reflects the updated version 8.0.0.5.

But I don't how can the installation directory would change to 8.0.0.5.

Is it by renaming the directory?

Would you please help me.

Thanks
Kumar


List Archive - Manage Your List Settings - Unsubscribe

Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com

dhornby5 | 13 Mar 15:16 2015
Picon
Picon

my subscriptions stop working sometimes

so in my QM, I have an alias queue pointing to a topic, then I have two subscriptions to the topic pointing to a local queue and a remote queue (defs below) - my QMs are V7.5.0.3 on Linux and all apps are Java/JMS using MQ Client V7.5.0.3

 

This works great 99% of the time in the last 6 months, happily forwarding messages written to the alias queue on to the two "endpoint" queues, but sometimes it just stops working for “no obvious reason”, and doesn’t start working again until I delete and redefine the subscriptions… one time, this happened after a QM restart and I said “aha”, but another time it happened after no obvious event and I said “hmmm”, so if any of you have any ideas, that would be very helpful

 

AMQ8409: Display Queue details.

   QUEUE(TRADEPATH.BRS.ALADDIN.OUT)        TYPE(QALIAS)

   ALTDATE(2014-07-11)                     ALTTIME(11.15.01)

   TARGET(BRS.SAVE.DATA)                   CLUSNL( )

   CLUSTER( )                              CLWLPRTY(0)

   CLWLRANK(0)                             CUSTOM( )

   DEFBIND(OPEN)                           DEFPRTY(0)

   DEFPSIST(NO)                            DEFPRESP(SYNC)

   DEFREADA(NO)                            DESCR( )

   GET(ENABLED)                            PUT(ENABLED)

   PROPCTL(COMPAT)                         SCOPE(QMGR)

   TARGTYPE(TOPIC)

 

AMQ8633: Display topic details.

   TOPIC(BRS.SAVE.DATA)                    TYPE(LOCAL)

   TOPICSTR(BRS.SAVE.DATA)                 DESCR( )

   CLUSTER( )                              DURSUB(ASPARENT)

   PUB(ASPARENT)                           SUB(ASPARENT)

   DEFPSIST(ASPARENT)                      DEFPRTY(ASPARENT)

   DEFPRESP(ASPARENT)                      ALTDATE(2014-07-11)

   ALTTIME(11.16.30)                       PMSGDLV(ASPARENT)

   NPMSGDLV(ASPARENT)                      PUBSCOPE(ASPARENT)

   SUBSCOPE(ASPARENT)                      PROXYSUB(FIRSTUSE)

   WILDCARD(PASSTHRU)                      MDURMDL( )

   MNDURMDL( )                             MCAST(ASPARENT)

   COMMINFO( )                             USEDLQ(ASPARENT)

   CUSTOM( )

 

AMQ8409: Display Queue details.

   QUEUE(BRS.SAVE.DATA.ONE)                TYPE(QLOCAL)

   ACCTQ(QMGR)                             ALTDATE(2015-03-11)

   ALTTIME(16.54.37)                       BOQNAME( )

   BOTHRESH(0)                             CLUSNL( )

   CLUSTER( )                              CLCHNAME( )

   CLWLPRTY(0)                             CLWLRANK(0)

   CLWLUSEQ(QMGR)                          CRDATE(2014-07-11)

   CRTIME(11.10.47)                        CURDEPTH(133)

   CUSTOM( )                               DEFBIND(OPEN)

   DEFPRTY(0)                              DEFPSIST(YES)

   DEFPRESP(SYNC)                          DEFREADA(NO)

   DEFSOPT(SHARED)                         DEFTYPE(PREDEFINED)

   DESCR( )                                DISTL(NO)

   GET(ENABLED)                            HARDENBO

   INITQ( )                                IPPROCS(0)

   MAXDEPTH(50000)                         MAXMSGL(20971520)

   MONQ(QMGR)                              MSGDLVSQ(PRIORITY)

   NOTRIGGER                               NPMCLASS(NORMAL)

   OPPROCS(0)                              PROCESS( )

   PUT(ENABLED)                            PROPCTL(COMPAT)

   QDEPTHHI(80)                            QDEPTHLO(20)

   QDPHIEV(ENABLED)                        QDPLOEV(DISABLED)

   QDPMAXEV(ENABLED)                       QSVCIEV(NONE)

   QSVCINT(999999999)                      RETINTVL(999999999)

   SCOPE(QMGR)                             SHARE

   STATQ(QMGR)                             TRIGDATA( )

   TRIGDPTH(1)                             TRIGMPRI(0)

   TRIGTYPE(FIRST)                         USAGE(NORMAL)

 

AMQ8409: Display Queue details.

   QUEUE(BRS.SAVE.DATA.TWO)                TYPE(QREMOTE)

   ALTDATE(2015-03-11)                     ALTTIME(16.54.46)

   CLUSNL( )                               CLUSTER( )

   CLWLPRTY(0)                             CLWLRANK(0)

   CUSTOM( )                               DEFBIND(OPEN)

   DEFPRTY(0)                              DEFPSIST(YES)

   DEFPRESP(SYNC)                          DESCR( )

   PUT(ENABLED)                            RQMNAME(NBXGR1AD)

   RNAME(TRADEPATH.BRS.ALADDIN.OUT)        SCOPE(QMGR)

   XMITQ(NBXGR1AD)

 

AMQ8096: WebSphere MQ subscription inquired.

   SUBID(414D51204E42485030324244202020207462C954271E5820)

   SUB(BRS.SAVE.DATA.TWO)                  TOPICSTR(BRS.SAVE.DATA)

   TOPICOBJ(BRS.SAVE.DATA)                 DEST(BRS.SAVE.DATA.TWO)

   DESTQMGR(NBHP02BD)                      PUBAPPID( )

   SELECTOR( )                             SELTYPE(NONE)

   USERDATA( )

   PUBACCT(0335303100000000000000000000000000000000000000000000000000000006)

   DESTCORL(414D51204E42485030324244202020207462C954271E5820)

   DESTCLAS(PROVIDED)                      DURABLE(YES)

   EXPIRY(UNLIMITED)                       PSPROP(MSGPROP)

   PUBPRTY(ASPUB)                          REQONLY(NO)

   SUBSCOPE(ALL)                           SUBLEVEL(1)

   SUBTYPE(ADMIN)                          VARUSER(ANY)

   WSCHEMA(TOPIC)                          SUBUSER(mqm)

   CRDATE(2015-03-11)                      CRTIME(16:52:06)

   ALTDATE(2015-03-11)                     ALTTIME(16:53:18)

AMQ8096: WebSphere MQ subscription inquired.

   SUBID(414D51204E42485030324244202020207462C954FD065820)

   SUB(BRS.SAVE.DATA.ONE)                  TOPICSTR(BRS.SAVE.DATA)

   TOPICOBJ(BRS.SAVE.DATA)                 DEST(BRS.SAVE.DATA.ONE)

   DESTQMGR(NBHP02BD)                      PUBAPPID( )

   SELECTOR( )                             SELTYPE(NONE)

   USERDATA( )

   PUBACCT(0335303100000000000000000000000000000000000000000000000000000006)

   DESTCORL(414D51204E42485030324244202020207462C954FD065820)

   DESTCLAS(PROVIDED)                      DURABLE(YES)

   EXPIRY(UNLIMITED)                       PSPROP(MSGPROP)

   PUBPRTY(ASPUB)                          REQONLY(NO)

   SUBSCOPE(ALL)                           SUBLEVEL(1)

   SUBTYPE(ADMIN)                          VARUSER(ANY)

   WSCHEMA(TOPIC)                          SUBUSER(mqm)

   CRDATE(2015-03-11)                      CRTIME(16:49:46)

   ALTDATE(2015-03-11)                     ALTTIME(16:49:46)


List Archive - Manage Your List Settings - Unsubscribe

Instructions for managing your mailing list subscription are provided in the Listserv General Users Guide available at http://www.lsoft.com

T.Rob | 13 Mar 13:18 2015

Re: Pub/Sub MsgID

Nigel Deakin has replied to my query about the JMSMessageID.  He is the team lead for team lead for the JMS
Specification so it doesn't get any more authoritative than that.  As I, and some of you, suspected, the
intent of the spec is that the JMSMessageID is preserved from publish to subscribe and IBM's
implementation is non-compliant in that respect.

Anyone with support care to open a PMR?  Because this is now out of RFE territory and has become break/fix, and
I no longer have an account under which to request support.

Nigel replies:

==============
I think this is stated in Section 4.4.11 "How message header values are set". This states that the
JMSMessageID is set by the "JMS provider send method". The same section goes on to say that "Message header
fields that are defined as being set by the 'JMS provider send method' will be available on the sending
client as well as on the receiving client."

This means that after the call to send() or publish() has returned, the sending application can use the
method getJMSMessageID() to find the message ID that was assigned to that message. When this message is
received, the receiving application can use the same method, and get the same value.

Each message sent to a topic is delivered to every subscriber on that topic. These subscribers will receive
a separate copy of the same message, with the same body, properties and headers, including JMSMessageID value.
==============

His full answer is here: 
http://iopt.us/1BAv0KE

http://stackoverflow.com/questions/29001655/should-the-jmsmessageid-change-between-publish-and-subscribe/29031266#29031266 

Kind regards,
-- T.Rob

> -----Original Message-----
> From: T.Rob [mailto:t.rob@...]
> Sent: Thursday, March 12, 2015 0:44 AM
> To: 'MQSeries List'
> Subject: Pub/Sub MsgID (was: Beta testers needed for MQ Message
> Replication)
> 
> Hi Roger,
> 
> For all the people using MQ Pub/Sub as a distribution list, this solution
> would keep the Message ID intact.  It doesn't solve the general case for
> dynamic subscribers but it's a start.
> 
> Incidentally, I checked to see if MQ still assigns a new MessageID to each
> message instance in V8.0.  It does.  I believe this to be non-compliant
> with the spec but when this was last raised, IBM's reply was "working as
> designed" and the ambiguity in the spec allows for this behavior.  I am now
> taking a different approach by asking the spec maintainers to eliminate the
> ambiguity by stating explicitly that the message should or should not be
> preserved from publication to consumption by subscribers:
> http://stackoverflow.com/q/29001655/214668
> 
> Kind regards,
> -- T.Rob
> 
> I have availability! For a good time (with IBM MQ) call:
> T.Robert Wyatt, Managing partner
> IoPT Consulting, LLC
> +1 704-443-TROB (8762) Voice/Text
> +44 (0) 8714 089 546  Voice
> https://ioptconsulting.com
> https://twitter.com/tdotrob

To unsubscribe, write to LISTSERV@... and,
in the message body (not the subject), write: SIGNOFF MQSERIES

Gmane