WebSphere MQ Technical Support Documents and Information

This note contains links (URLs) to WebSphere MQ technical support documents and information that can help you get more value from your software. It is intended to help you to be proactive in your support and administration of WebSphere MQ. This note includes:

- In the spotlight- Planned maintenance- Education- General self-help resources

In the spotlight

1. Daylight Saving Time (DST) 2007 information for WebSphere MQ

Information about the impact of the US Energy Policy Act of 2005, which changes the effective dates of US Daylight Saving Time (DST) in 2007 for the US. Actions are required to address this issue in IBM WebSphere MQ.

http://www.ibm.com/support/docview.wss?rs=171&uid=swg21246616&acss=wmq121106

2. WebSphere MQ SupportPacs

MH03: WebSphere MQ SSL Configuration Checker

http://www.ibm.com/support/docview.wss?rs=171&uid=swg24014179&acss=wmq121106

MQ01: Using LDAP and SSL with WebSphere MQ and MQIPT

http://www.ibm.com/support/docview.wss?rs=171&uid=swg24014143&acss=wmq121106

3. WebSphere MQ Clustering - Cluster hints and tips

Provides answers to the most common problems and questions regarding WebSphere MQ Clustering.

http://www.ibm.com/support/docview.wss?rs=171&uid=swg21229905&acss=wmq121106

4. Data Conversion under WebSphere MQ

http://www.ibm.com/support/docview.wss?rs=171&uid=swg27005729&acss=wmq121106

5. Directions to start, end, and format trace

http://www.ibm.com/support/docview.wss?rs=171&uid=swg21174924&acss=wmq121106

6. Locating the WebSphere MQ Error logs

http://www.ibm.com/support/docview.wss?rs=171&uid=swg21172370&acss=wmq121106

Planned maintenance

1. Refresh Pack 6.0.2.0 for WebSphere MQ V6.0 is now available

http://www.ibm.com/support/docview.wss?rs=171&uid=swg24013482&acss=wmq121106

2. Planned Maintenance availability IBM WebSphere MQ

http://www.ibm.com/support/docview.wss?rs=171&uid=swg27006309&acss=wmq121106

3. WebSphere MQ Recommended fixes

http://www.ibm.com/support/docview.wss?rs=171&uid=swg27006037&acss=wmq121106

4. Detailed system requirements

Identifies the supported software options by operating system for the WebSphere MQ products.

http://www.ibm.com/support/docview.wss?rs=171&uid=swg27006467&acss=wmq121106

Education

1. WebSphere MQ Library

The WebSphere MQ library contains links to the Information Center, product manuals and other helpful learning material.

http://www.ibm.com/software/integration/wmq/library/?acss=wmq121106

2. Technical Exchange Webcasts

Take full advantage of your product. Join us as technical experts share their knowledge and then answer your questions. Visit this site often to see upcoming topics and to review previously recorded webcasts.

http://www.ibm.com/software/websphere/support/supp_tech.html?acss=wmq121106

General self-help resources

Here are some other ways that you can access IBM WebSphere MQ self-help support information on the Web:

1. Support Page

Primary support resources for WebSphere MQ

http://www.ibm.com/software/integration/wmq/support/?acss=wmq121106

2. Online resources for successful management of your software environment

Join a 60-minute learning session for a high-level overview of online tools and resources designed to improve your support experience, as well as step-by-step instructions to access and use the Electronic Service Request (ESR) tool to manage PMRs online.

http://www.ibm.com/software/websphere/support/d2w_schedule.html?acss=wmq121106

3. IBM Software Support Toolbar

This is a stand-alone application that allows you to easily search IBM.com for all types of software support content plus organizes the major areas of not only Software support, but the individual brand support sites into a concise application.

http://www.ibm.com/software/support/toolbar/?acss=wmq121106

4. IBM Software Support RSS Product feeds

These RSS feeds allow you to stay up-to-date with the latest content created for specific IBM Software products.

http://www.ibm.com/software/support/rss/websphere/171.xml?rss=s171&ca=rsswebsphere&acss=wmq121106

5. IBM Software Support Lifecycle page

The IBM Software Support Lifecycle policy specifies the length of time support will be available for IBM software.

http://www.ibm.com/software/info/supportlifecycle/?acss=wmq121106

CSC is among the Top 85 strategic IT vendors in Asia - MIS Asia Magazine Nov 06

Computer Sciences Corp
Global headquarters: El Segundo, California, US
Global CEO: Van Honeycutt
Top Asia-Pacific executives: George Bell, president, Asia operations/Mike Shove, managing director, Australia operations
Core activity: Outsourcing, IT services
Revenue: US$14.6 billion (FY 2006)
Profit: US$634 million (FY 2006)
Key clients in Asia-Pacific: Motorola, Maybank, Dupont, Air Products and Chemical Inc, United Technologies Corporation, Allianz Australia, Australian Department of Defence
No. of employees: 79,000

It never hurts to have friends in high places, and Computer Sciences Corp's (CSC) storied history as an IT provider to the US government has served it well, accounting for contracts worth some US$5 billion in fiscal 2006 alone. Still, few could accuse the firm of depending solely on Uncle Sam's patronage. CSC also recently renewed a contract worth US$37 million to provide IT services to Australia's OneSteel and also won deals to support the Asian operations of Air Products and Chemical and United Technologies.

Like many of its competitors, CSC is banking on targeted acquisitions and investments that deepen its expertise in certain areas or geographies. CSC claims particular strength in emerging areas like Web 2.0, software as a service, and service-oriented architecture, which allow complex applications to be constructed by linking individual components. The firm already boasts four "delivery centres" in India and is in the midst of establishing a Global Transformation Services organisation in Asia to provide applications management services to regional customers.

CSC's presence in Asia dates back to 1999, when it took a majority stake in Singapore's CSA Holdings. Last year, the firm decided to bring CSA completely into the CSC fold, and integration of the company's regional operations is ongoing. CSC is expecting a warmer reception for its managed service offerings in Asia as the market matures and is also planning to ratchet up collaboration with partners to find new channels for its offerings in specific sectors such as insurance.

2024 MQRC_SYNCPOINT_LIMIT_REACHED

Problem Description: 1200 cyl of DASD has been dedicated to CIF box (NCIF) in MBB1 & another 1200cyl in MBB5. However, during recent batch propagation, we were unable to send even 30,000 rec. The error is 2024 MQRC_SYNCPOINT_LIMIT_REACHED (refer below).

Please explain why we still experience this problem even 1200cyl has been dedicated to CIF?

This limitation is not acceptable as we are processing bulk data. We cannot afford to send 10,000 records at 1 time for 1.2 million customers. 10,000 recs at 1 time is as per previous environment (shared DASD with other application).

Explanation: An MQGET, MQPUT, or MQPUT1 call failed because it would have caused the number of uncommitted messages in the current unit of work to exceed the limit defined for the queue manager (see the MaxUncommittedMsgs queue-manager attribute). The number of uncommitted messages is the sum of the following since the start of the current unit of work:

• Messages put by the application with the MQPMO_SYNCPOINT option
• Messages retrieved by the application with the MQGMO_SYNCPOINT option
• Trigger messages and COA report messages generated by the queue manager
  for messages put with the MQPMO_SYNCPOINT option
• COD report messages generated by the queue manager for messages
  retrieved with the MQGMO_SYNCPOINT option
• On Compaq NonStop Kernel, this reason code occurs when the maximum
  number of I/O operations in a single TM/MP transaction has been exceeded.

Corrective action: Check whether the application is looping. If it is not, consider reducing the complexity of the application. Alternatively, increase the queue-manager limit for the maximum number of uncommitted messages within a unit of work.

Suggestion: If we are confident that the application is not looping and the application does not want to send these messages in smaller batches (reducing the complexity) then by all means increase this value to accommodate there predicted amounts.

Please also check that the Local Q these messages will be delivered to can handle the message total, by IBM default these are set to the highest value.

Maximum queue depth . . . . : 999999999 0 - 999999999

Also for performance you may want to increase the Buffers allocated to the PSID associated to the Local Q that these messages are sent to.

Closed APARs for IBM WebSphere MQ for z/OS 5.3.1

This link contains a list of all closed APARs for IBM® WebSphere® MQ 5.3.1 for z/OS®. Please refer to it if PTF needed on MQ problem. IBMID is required to download the PTF.

CSC Employees Personal Web Posting

Blogs, wikis and podcasts are fairly new mainstream communications methods that can improve interaction between individuals who have a common interest, but the use of such tools without guiding principles could severely impact our company. In particular, blogging is growing in popularity and is already considered a conventional and commonly used communication tool. While blogging is a powerful broadcasting tool, it can pose significant risks to CSC’s enterprise information security when not controlled. The main risks to CSC are inadvertent (or intentional) disclosure of CSC or client intellectual property, confidential information and damage to CSC credibility in the market place.

A Personal Blog (short for weblog) is a personal online journal that is frequently updated and intended for general public consumption. Blogs are defined by their format: a series of entries posted to a single page in reverse-chronological order. Blogs generally represent the personality of the author or reflect the purpose of the Web site that hosts the blog.

A Wiki is a is a web site that makes it simple for anyone to create and share web pages, images, and much more in an instant. Similar to a blog in structure and logic, a wiki allows anyone to edit, delete or modify content that has been placed on the Web. In contrast, a blog, typically authored by an individual, does not allow visitors to change the original posted material; only add comments to the original content.

A Podcast is a multimedia file distributed over the Internet for playback on mobile devices and personal computers.

Employees run a personal risk if they post fallacious or slanderous information that could leave them vulnerable to defamation lawsuits. The improper use of blogs, wikis and podcasts can also lead to proprietary information being obtained by CSC’s competitors or create a public relations incident. The concern grows with the popularity of image-ready cell phones and online sites that allow users to post videos.

There are also legal issues that personal blogs raise. These include the potential loss of CSC or customer intellectual property and copyright infringement issues. In addition, the disclosure of a third party's trade secrets can expose a blogger to liability for misappropriation.

CSC views personal websites and weblogs positively, and it respects the right of employees to use them as a medium of self-expression and research. However, all CSC employees must follow the guidelines below when developing and broadcasting blogs, wikis or podcasts:

• Make it clear that the views expressed in the blog, wiki or podcast are yours alone and do not necessarily represent the views of CSC.
• Respect CSC’s sensitive and proprietary information and ensure that such information is not published in unauthorized or public forums.
• Seek CSC managerial approval if there are any questions as to what is appropriate to included in a blog, wiki or podcast.
• Be respectful to CSC, other employees, customers, partners, and competitors.
• Understand and fully comply when CSC identifies topics should not be discussed outside of the company for confidentiality or legal compliance reasons.
• Ensure that any bogging, wiki or pod casting activity does not interfere with work requirements.

GNS is in the process of constructing a more detailed security guideline on the use of blogs, wikis and podcasts that will be published within the next two months. The availability of this guideline will be announced through future security awareness bulletins.

AMQ9213: A communications error for CPI-C occurred.

Problem Description: User getting AMQ9213 when starting sender channel.

Reference: Woloc user

Effected User: Sender channel with SNA protocol in retry status. All sender channels with TCP/IP protocol are in running state.

MQ Version: 5.3 CSD12

OS: Unix

Action: Check /var/mqm/qmgrs/BPDS11/errros/AMQERR01.LOG. The error reads as follows:

-------------------------------------------------------------------------------
11/27/06 13:24:57
AMQ9213: A communications error for CPI-C occurred.

EXPLANATION:An unexpected error occurred in communications.ACTION:The return code from the CPI-C (cmrcv) call was 6 (X'6'). Record these valuesand tell the systems administrator.
-------------------------------------------------------------------------------
11/27/06 13:25:14
AMQ9213: A communications error for CPI-C occurred.

EXPLANATION:An unexpected error occurred in communications.ACTION:The return code from the CPI-C (cmrcv) call was 27 (X'1B'). Record these valuesand tell the systems administrator.
-------------------------------------------------------------------------------
11/27/06 13:25:14
AMQ9999: Channel program ended abnormally.

EXPLANATION:Channel program 'MQS1.BPDS11.INQ.01' ended abnormally.ACTION:Look at previous error messages for channel program 'MQS1.BPDS11.INQ.01' in theerror files to determine the cause of the failure.
-------------------------------------------------------------------------------

The only thing that I'm not sure in the log are 6 (X'6') and 27 (X'1B'). If anyone can let me know the link please post it here. Then I did a google search using "AMQ9213 6 (X'6')" keyword and found the answer in SJG Enterprise Integration.