MQ V6 Fundamentals. Information Center. MQ 7.0 compat with previous. This document applies only to the following language version(s): English Question Is WebSphere MQ 7.0, 7.1 and 7.5 compatible with previous versions? Answer Compatibility statement: WebSphere MQ V7.0, V7.1 or V7.5 queue managers and clients interoperate with queue managers and clients from any previous level of the WebSphere MQ or MQSeries products. This means that ... A 7.0, 7.1 and 7.5 client can connect to all queue managers, non-version 7, as well as version 7.0, 7.1 and 7.5. MQ Client V6 / V7 compatibility The new features which are available for a version 7 client connected to a version 6.0 queue manager are: - Weighted selection on CLNTCONN channels. - Reconnecting via a previously used channel. - Maximum message length increased on MQSERVER environment variable.
The new feature which is available for a version 6.0 client connected to a version 7 queue manager is: - Instance limits on SVRCONN channels. Related information. Kernel config. Mustgather MQ. Problem(Abstract) If you are experiencing a problem with WebSphere MQ on an AIX, HP-UX, Linux, Solaris or Windows system, you need a way to collect and analyze data to find a solution.
This index links to directions for collecting and analyzing data (often called "MustGather" data) for a wide variety of WebSphere MQ issues. Resolving the problem Linux and UNIX Collect WebSphere MQ data as soon as you see a problem happening so that you can analyze the issue and involve IBM support if necessary. If your problem type is not listed, follow these instructions: Other, General, or Unknown Problems Windows Collect WebSphere MQ data as soon as you see a problem happening so that you can analyze the issue and involve IBM support if necessary. ConfigUNIX resources. You are planning to install or upgrade a WebSphere MQ server on a UNIX or Linux system and need to know how to tune the operating system, including user limits and kernel parameters for resources like shared memory and semaphores. IBM WebSphere MQ Tuning Recommendations The WebSphere MQ documentation provides the IBM recommended default values for a number of operating system tuning parameters: WebSphere MQ 7.5 Additional settings for AIX, HP-UX, Linux and Solaris WebSphere MQ 7.1 Additional settings for AIX, HP-UX, Linux and Solaris WebSphere MQ 7.0 System resource limits for AIX WebSphere MQ 7.0 Kernel configuration for HP-UX WebSphere MQ 7.0 Kernel configuration for Linux WebSphere MQ 7.0 Resource limit configuration for Solaris These default limits should be sufficient to run WebSphere MQ without exhausting any system resources.
However, if you have an extremely busy system, you might need to increase some limits beyond the IBM recommended defaults. Busy systems include: mqconfig. Disk space requirements for QM. Hi David, I went back and read your original mail more closely. The failing component is GetSemSet (Get Semaphore Set). The number of semaphore sets is determined by semmni, and is a system wide value. That is, it defines the maximum number of semaphore sets throughout the system (not just for a single process). Although the linux quick start guide doesn't specify a value for this, the Solaris one does (minimum 1024). semmni is the 4th value from /proc/sys/kernel/sem, so you have 128 On my Solaris systems which has several queue managers, I have 2221 specified.
A combination of WMQ 5.3 and Solaris 8 or 9 also requires that semmap must be >= (semmni + 2). I don't know about any Linux restrictions in that area.