IC58216: Clarification of client documentation to state that conversion of internal WebSphere MQ data is performed on the queue manager

WebSphere MQ V7.0 for i5/OS Fix Pack 7.0.0.2
WebSphere MQ V7.0 Fix Pack 7.0.0.2
WebSphere MQ V7.0 Fix Pack 7.0.1.1
WebSphere MQ V7.0.1 for i5/OS Fix Pack 7.0.1.1
WebSphere MQ V7.0 Fix Pack 7.0.1.2
WebSphere MQ V7.0.1 for i5/OS Fix Pack 7.0.1.2

APAR status

• Closed as documentation error.

Error description

• The client documentation has an ambiguous statement which can
  lead to confusion as to whether conversion of internal
  WebSphere MQ data is performed on the client or the queue
  manager.
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users who are attempting to understand where the conversion of
  internal WebSphere MQ data is performed for client connections.
  
  Platforms affected:
   All Distributed (iSeries, all Unix and Windows) +Java
  ****************************************************************
  PROBLEM SUMMARY:
  The following line in the client documentation is ambiguous:
  If the connected queue manager requires the data to be
  converted, this is done by the client support code.
  
  This is found in the following location:
  Clients -> Application Programming -> Using the message queue
  interface (MQI) -> Choosing client or server coded character
  set identifier (CCSID)
  

Problem conclusion

• The v6 and v7 client documentation is updated:
  If the connected queue manager requires the data to be
  converted, this is done by the queue manager.
  
  The v7 client documentation has the additional sentence added
  to indicate the difference between the C and Java client:
  The Java client in v7, however, is capable of doing the
  conversion if the queue manager is unable to do so.
  Please see Connection differences section in the v7 Using Java
  documentation.
  
  The Connection differences section in the v7 Using Java
  documentation has an additional bullet added:
  If connecting to a queue manager that requires character data
  to be converted, the v7 Java client is now capable of doing the
  conversion if queue manager is unable to do so. The client JVM
  must support the conversion between the CCSID of the client and
  that of the queue manager.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels