Skip to main content

Websphere MQ Versions 6 News - Middleware News

  • Improved Usability
    • Simple File Transfer (Windows & Linux) - a simple application that works "out-of-the-box", command line and GUI. No need to write own test programs.
    • Quick Tour (Windows & Linux)
    • New cross-platform configuration tooling (Windows & Linux)
  • Improvements to manageability
    • Find out what the system is doing, and influence it
      • DISPLAY QSTATUS
      • DISPLAY CHSTATUS
      • DISPLAY CONN(*) ALL
      • TRACEROUTE
    • Easier problem determination and problem avoidance
  • Enhanced Availability
    • Exploiting z/OS services
  • Extended performance, capacity and scalability
    • Exploiting 64-bit address space
  • Eclipse configuration tool - can configure WMQ on all platforms
    (including WMQ V6 for z/OS - but not earlier versions on z/OS)
  • Trace Route
  • IPV6
  • zOS : messages (in Shared queues) larger than 63 KB are now supported (using DB2) - up to 100 MB.
  • AIX : 64-bit support
Platform coverage :
  • AIX 5 (64-bit systems only)
  • Solaris (64-bit Sparc systems only)
  • HP-UX 11i (64-bit PA-RISC only)
  • Linux/Intel (32-bit), Linux/pSeries (64-bit distros only), Linux/zSeries
  • z/OS 1.4
    DB2 v 7.1 with PQ71179, IMS v 7.1, Coupling Facility Level 9.
  • Windows 2000, XP, 2003
  • OS/400
  • Other platforms/environments (eg 64-bit) under consideration for a later GA2

Labels

Labels:

Comments

Post a Comment

adsrerrapop

Popular posts from this blog

IBM Websphere MQ interview Questions Part 5

MQ Series: - It is an IBM web sphere product which is evolved in 1990’s. MQ series does transportation from one point to other. It is an EAI tool (Middle ware) VERSIONS:-5.0, 5.1, 5.3, 6.0, 7.0(new version). The currently using version is 6.2 Note: – MQ series supports more than 35+ operating systems. It is platform Independent. For every OS we have different MQ series software’s. But the functionality of MQ series Default path for installing MQ series is:- C: programfiles\BM\clipse\SDK30 C: programfiles\IBM\WebsphereMQ After installation it will create a group and user. Some middleware technologies are Tibco, SAP XI. MQ series deals with two things, they are OBJECTS, SERVICES. In OBJECTS we have • QUEUES • CHANNELS • PROCESS • AUTHENTICATION • QUERY MANAGER. In SERVICES we have LISTENERS. Objects: – objects are used to handle the transactions with the help of services. QUEUE MANAGER maintains all the objects and services. QUEUE: – it is a database structure ...
139 comments
Read more

IBM Websphere MQ Reason code list / mq reason codes / websphere mq error codes / mq error messages

Reason code list ================= The following is a list of reason codes, in numeric order, providing detailed information to help you understand them, including: * An explanation of the circumstances that have caused the code to be raised * The associated completion code * Suggested programmer actions in response to the code * 0 (0000) (RC0): MQRC_NONE * 900 (0384) (RC900): MQRC_APPL_FIRST * 999 (03E7) (RC999): MQRC_APPL_LAST * 2001 (07D1) (RC2001): MQRC_ALIAS_BASE_Q_TYPE_ERROR * 2002 (07D2) (RC2002): MQRC_ALREADY_CONNECTED * 2003 (07D3) (RC2003): MQRC_BACKED_OUT * 2004 (07D4) (RC2004): MQRC_BUFFER_ERROR * 2005 (07D5) (RC2005): MQRC_BUFFER_LENGTH_ERROR * 2006 (07D6) (RC2006): MQRC_CHAR_ATTR_LENGTH_ERROR * 2007 (07D7) (RC2007): MQRC_CHAR_ATTRS_ERROR * 2008 (07D8) (RC2008): MQRC_CHAR_ATTRS_TOO_SHORT * 2009 (07D9) (RC2009): MQRC_CONNECTION_BROKEN * 2010 (07DA) (RC2010): MQRC_DATA_LENGTH_ERROR * 2011 (07DB) (RC2011): MQRC_DYNAMIC_Q_NAME_ERROR * 2012 (07DC) (RC201...
2 comments
Read more

Adding SSL certificates to a mixed z/OS and Unix queue manager environment - Middleware News

Adding SSL certificates to a mixed z/OS and Unix queue manager environment - Middleware News 1. Security Considerations IBM advises customers who are using SSL, that the most secure way to do this is to use recognized Certification Authorities to sign their certificates. Ensuring secure transfer of information is the main purpose of SSL. This integrity must be properly observed when setting up SSL. You should always be certain who has signed each of your SSL certificates, who has had and who continues to have access to them. The first secure way to generate certificates is to generate a certificate request, on each system or machine that uses SSL. This request has to be signed by an external Certification Authority before it can be used. Getting certificate requests signed by a CA is secure, because during the signing process at no point do any files contain the certificate's Private Keys. This principle is vital to SSL security. Signing certificates in this way is covered...
38 comments
Read more