FJ Brandelik | 28 Jul 15:55 2015
Picon

Re: Azure MQ Premium Connector

As you are talking about the Microsoft MQ client I am thinking Azure is talking about MSMQ and not IBM MQ. MSMQ
is Microsoft's implementation of a messaging system (available with the enterprise flavor of your
Windows OS).

Can you be more specific or confirm that this is the case?

To unsubscribe, write to LISTSERV@... and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Roger Lacroix | 28 Jul 01:43 2015

MQTC v2.0.1.5 Early-bird ends tomorrow

All,

The early-bird price for MQ Technical Conference v2.0.1.5 (MQTC) expires 
tomorrow (July 28th) .

MQTC is the largest conference in the world solely dedicated to IBM MQ 
(aka WebSphere MQ & MQSeries).

For more information, please go to: http://www.mqtechconference.com

Regards,
Roger Lacroix
Capitalware Inc.

To unsubscribe, write to LISTSERV@... and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Phil Blake | 27 Jul 22:19 2015
Picon

GSS announces Topic Dashboard version 2.0.0

Grail Software Solutions are pleased to announce an update of 'GSS Topic Dashboard Starter Edition'
Version 1.0.0 to Version 2.0.0

This is an Eclipse™ RCP application designed to help educate end-users on IBM® MQ. An example of an
end-user could be a developer wanting to explore and become familiar with the features of IBM MQ pub/sub
before writing applications that use it.

'GSS Topic Dashboard' can be used as an education tool to learn about the various options for publishing and
consuming publications using IBM® MQ, and for an application developer or performance tester to
generate messages, watch activity on a selected destination and test topic wildcarding.

This version has the following enhancements:

1. Now an Eclipse™ RCP application, making it much easier to install/uninstall.

2. A message viewer has been added to view published messages and consumed publications.
   - Contents of the viewer can be paused
   - Messages can be cleared
   - Messages can be exported to a file

3. The published message size can be set.

4. New preferences to
   - Set message rate graphical type for each view
   - Show Message Viewer
   - Control contents of the Message Viewer
   - Control use of the default connection

5. Only 2 subscribers are now shown by default, but more can be added.

(Continue reading)

Phil Blake | 27 Jul 22:17 2015
Picon

GSS announces Topic Dashboard for IBM MQ Light version 2.0.0

Grail Software Solutions are pleased to announce an update of 'GSS Topic Dashboard for IBM MQ Light Starter
Edition' Version 1.0.0 to Version 2.0.0

This is an Eclipse™ RCP application designed to help educate end-users on IBM® MQ Light. An example of an
end-user could be a developer wanting to explore and become familiar with the features of IBM MQ Light
before writing applications that use it.

'GSS Topic Dashboard for IBM MQ Light' can be used as an education tool to learn about the various options for
sending and receiving messages using IBM® MQ Light, and for an application developer or performance
tester to generate messages, watch activity on a selected destination and test topic wildcarding.

This version has the following enhancements:

1. A message viewer has been added to view message data sent and received.
   - Contents of the viewer can be paused
   - Messages can be cleared
   - Messages can be exported to a file

2. The sent message size can be set.

3. New preferences to
   - Set message rate graphical type for each view
   - Show Message Viewer
   - Control contents of the Message Viewer

Using IBM® MQ 8.0.0.3 with an optional installable component for IBM® MQ Light, MQ Light applications
can be deployed into an existing MQ network along side your other MQ applications. 'GSS Topic Dashboard
for MQ Light' can be used with another of our products, 'GSS Topic Dashboard' to explore and test this
extended messaging environment. When both products are connected to the same IBM MQ queue manager
environment, messages sent by the GSS Sender view of 'GSS Topic Dashboard for MQ Light' can be seen in the
(Continue reading)

Phil Blake | 27 Jul 22:15 2015
Picon

GSS announces Queue Dashboard version 2.0.0

Grail Software Solutions are pleased to announce an update of 'GSS Queue Dashboard Starter Edition'
Version 1.0.0 to Version 2.0.0

This is an Eclipse™ RCP application and can be used as an education tool, and for an application developer
or performance tester to generate, watch and trigger event activity on a selected queue.

This version has the following enhancements:

1. Now an Eclipse™ RCP application, making it much easier to install/uninstall.

2. A message viewer has been added to view messages generated and consumed.
   - Contents of the viewer can be paused
   - Messages can be cleared
   - Messages can be exported to a file

3. The generated message size can be set.

4. New preferences to
   - Set message rate graphical type for each view
   - Show Message Viewer
   - Control contents of the Message Viewer
   - Control use of the default connection

For more information about 'GSS Queue Dashboard', see www.grailsoftwaresolutions.co.uk/products.html

To download 'GSS Queue Dashboard' and its user guide, see www.grailsoftwaresolutions.co.uk/download.html

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

Coombs, Lawrence | 24 Jul 17:12 2015

Re: Effect of DISCINT on SVRCONN channel

I define all my SVRCONN channels on V7.5 queue managers with a DISCINT of 0. The reason is that most if not all are being used by application servers that have defined connection pools that use them.

 

Usually there is a MIN and MAX number of connections you specify when you define the MQ connection pool. If you specify a DISCINT and allow the SVRCONN to disconnect, what effect will this have on the client side application server? Is this even a good idea to do this with SVRCONN channels that are tied to a connection pool, given the fact that creating these connections can be expensive on the client side application server.

 

Appreciate every comment.

This message, including any attachments, is the property of Sears Holdings Corporation and/or one of its subsidiaries. It is confidential and may contain proprietary or legally privileged information. If you are not the intended recipient, please delete it without reading the contents. Thank you.

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

Coombs, Lawrence | 22 Jul 02:51 2015

Re: TCP/IP error (X'68') with MQ Client Channel

I have a vendor package that uses the MQ client to connect to a V7.5.0.2 MQServer.

Occasionally I see an AMQ9209 message stating that the SVRCONN channel closed.

In the explanation, there is the error receiving data from host over TCP/IP message.

 

The return code from the TCP/IP read() call was 104 (X'68'). Record these

values and tell the systems administrator.

 

When I google this return code I get the

errno 68:                EADDRNOTAVAIL     68                Can't assign requested address

 

I think somehow the package might be doing  a reconnect without a wait and there is a stuck socket that the connection might be trying to reuse(remote address).

 

I am not a TCP/IP person and I am not getting much help from….

 

Has anyone seen this error in relation to a client channel?  How did you resolve this issue?

 

Any help is appreciated.

 

This message, including any attachments, is the property of Sears Holdings Corporation and/or one of its subsidiaries. It is confidential and may contain proprietary or legally privileged information. If you are not the intended recipient, please delete it without reading the contents. Thank you.

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

Ryan Finnesey | 21 Jul 08:14 2015

Azure MQ Premium Connector

I was wondering if anyone within the group has done any development work with the Azure MQ Premium
Connector?  In the limited documentation I can find it says it is using the Microsoft MQ Client?  I am
guessing this is different than the MQ Client released by IBM?  I did not know it was possible to have 3rd
party MQ Clients.  One major downside I see is that it can only be used with MQ 8

Cheers
Ryan

To unsubscribe, write to LISTSERV@... and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Jefferson Lowrey | 20 Jul 19:49 2015
Picon

Re: Help support MS0S: MQExplorer MQSC Editor

I've now gotten a lot of response to this, which is really great!

 In general, this is a project on github, so if you want to play around with it, or try to extend it or fix anything, please feel free.  I'll accept any pulls that don't seem to break things or vary from what I'm hoping to do.

I'm also happy to answer questions about how things work, or how to build this, or what questions about Eclipse and MQE plugins that I can answer.

Just please contact me off list...


Thank you,

Jeff Lowrey




From:        Jefferson Lowrey/Baltimore/IBM
To:        "MQSeries List" <MQSERIES-JX7+OpRa80QeFbOYke1v4oOpTq8/W97FXqFh9Ls21Oc@public.gmane.org>
Date:        07/09/2015 09:06 AM
Subject:        Re: Help support MS0S: MQExplorer MQSC Editor


Well.  I've gotten absolutely no response to this, which is a bit disappointing.

I'd like to provide a bit more information, that may have people holding back.  

First, I am much easier to work with than you might think from reading things I've written.

Second, there isn't any high degree of knowledge required.  Basic Java skills and a solid understanding of the UI components of Eclipse and MQExplorer.  I.e. You've used MQexplorer for more than 10 minutes... And have written at least a couple of Java programs.  


Thank you,

Jeff Lowrey





From:        Jefferson Lowrey/Baltimore/IBM
To:        "MQSeries List" <MQSERIES-JX7+OpRa80QeFbOYke1v4oOpTq8/W97FXqFh9Ls21Oc@public.gmane.org>
Date:        07/01/2015 08:48 AM
Subject:        Help support MS0S: MQExplorer MQSC Editor


I'm looking for someone to help support and maintain and upgrade the supportPac MS0S.

This will include learning the code, learning the build process, learning how to modify things, and otherwise the entire software development life cycle.

All contributions and changes will be made to the github repository https://github.com/ibm-messaging/mq-mqsc-editor-plugin

I have a current report of a very very very small bug. This is an ideal opportunity to start this process, and work with someone to make the necessary change and learn the build process.

If you are interested, please contact me off list.

Thank you,

Jeff Lowrey


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

FJ Brandelik | 20 Jul 18:21 2015
Picon

Re: Multiple MQExplorer

Don't know much about installing MS0T as I usually install MQExplorer with the server installation.
Now if you have multiple installations (7.0.1.8, 7.5.0.2, 7.5.0.3, 8.0.0.3) like me on my laptop, you have
the MQE in the Versions installation directory.
Each MQE is version specific and will attempt to upgrade the local qmgrs. Local qmgrs at a different (lesser
/ greater) level are only visible as a server connection client. Makes sense as with the new version come
new and different capabilities...

This also changes my preferences about loading support packs. I generally use them as entries in the links directory.

Hope it helps F.J.

To unsubscribe, write to LISTSERV@... and,
in the message body (not the subject), write: SIGNOFF MQSERIES
Barton, Linda | 14 Jul 14:44 2015
Picon

MQ Put and Logsize/queue space question

Hi folks, I have a question regarding calculating the size of the midrange MQ logs when I have a Gateway QMgr that passes messages to a Backend QMGR.  Applications connect to the Gateway QMGR and do a PUT, and the message flows to the backend qmgr and local queue where another application does a GET. 
So I figure I would account for 750 bytes plus the message size for the PUT on the Gateway qmgr, assuming it is being logged here before going on the transmission queue to the backend, or in case the backend is not available.
Do I also have to add the PUT size to the Backend QMGR?  Or do I just calculate the Get there because the application is picking it up?  Where is the PUT logged? Both places for persistent messages?
 
I made this little spreadsheet to help me determine what I need for log space based on the number of messages and the size of the messages, plus the overhead of the calls. 
 
Am I over complicating this?  Should I just include PUT and GET on both qmgrs and be done with it?  What do you guys do?
 
When you have a large shared MQ infrastructure, how do you keep track of all the application queues/message sizes/throughput so you can make sure you have enough Log and Queue space? Especially when logs and queues are on the same filesystem (multi-instance NAS mount).
 
CDI Document Builder Action # of msgs per day Operation msg size App msgl bytes total msg bytes
(operation msg + app msg)*msgs per day
total msg GB 4 days, gig
360 documents Put                100,000 750                        30,720 3,147,000,000                          2.931  
Gateway Get                100,000 260                                -   26,000,000                         0.024  
VK.FS.360.DOCUMENT.REQ Sync cmt                100,000 750                                -   75,000,000                         0.070  
 Assume 10% failure
 
Sync rolb                  10,000 1012                                -   10,120,000                         0.009  
  Chkpt                          31 950                                -   29,450                         0.000  
                                            3                     12
 
Chkpt is done every 10000 recoverable operations
 
Operation Size
Put persistent message 750 bytes + message length
 
If the message is large, it is divided into segments of 15700 bytes, each segment adding an extra 300 bytes.
Get message 260 bytes
Sync point, commit 750 bytes
Sync point, rollback 1000 bytes + 12 bytes for each get or put to be rolled back
Create object 1500 bytes
Delete object 300 bytes
Alter attributes 1024 bytes
Record media image 800 bytes + image
 
The image is divided into segments of 260 000 bytes, each segment adding an extra 300 bytes.
Checkpoint 750 bytes + 200 bytes for each active unit of work + 380 bytes for each cluster-sender channel, if you are using multiple cluster transmission queues per queue manager.
 
Additional data might be logged for any uncommitted puts or gets that are buffered for performance reasons.
 
If you have cluster-sender channels, then at each checkpoint an extra 380 bytes is written to the log per cluster-sender channel
 
 
Linda Barton
 

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


Gmane