PI80507: MQ: CHANNEL EXIT INFORMATION NOT BEING PROPOGATED FROM THE QUEUE MANAGER TO THE CHIN. ALSO UNEXPECTED ERROR CSQX203E.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• After migrating  from MQ V8 to V9 in
  V8 compatibility mode on z/OS platform,
  the exits were no longer converting the
  messages from ASCII (cc 819) to EBCDIC (cc 500).
  There were no error messages in either the
  MSTR or CHIN logs.
  .
  Channel exit information is not being propogated
  from the queue-manager to the CHIN in the case where
  the channel was originally defined prior to MQ V530
  (which means that the MCHL object does not include an
  MCHLEXTV2 extension; changes to rrxReadChannelDef
  and CSQXRCDX at V9 result in this problem occurring).
  .
  This problem may also result in CSQX203E unexpectedly issued
  for a channel, with the connection-name in the message given as
  blanks.
  Additional Symptom(s) Search Keyword(s):
  

Local fix

• We modified the channel definition to remove the
  message exit, and then modified the channel to
  put the exit back, then the messages now began
  translating  properly.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All users of IBM MQ for z/OS Version 9       *
  *                 Release 0 Modification 0.                    *
  ****************************************************************
  * PROBLEM DESCRIPTION: After migrating to V9, a message exit   *
  *                      on a receiver channel is not being      *
  *                      invoked. Additionally message CSQX203E  *
  *                      may be seen when trying to start a      *
  *                      sender channel.                         *
  ****************************************************************
  In V9, rrxReadChannelDef changed to use CSQXRCDX to retrieve
  message exit information from the MCHLEXTV2 extension of the
  MCHL control block. However channels created before MQ V530 do
  not have this version 2 extension thus the exit information is
  not found.
  Another symptom of the changes made at V9 is that for a sender
  channel an incorrect conname is copied into the MQCD from the
  MCHL, resulting in CSQX203E when trying to start the channel.
  These problems can be circumvented by performing an ALTER
  command on the channel.
  

Problem conclusion

• Code has been changed in CSQMICLU to cope with channels defined
  pre MQ V530 which have the older MCHL format.
  

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:

  UI51016

Modules/Macros

• CSQ7CBM  CSQ7CHND CSQ7VTBL CSQMICLU CSQMJCLU CSQXRCDX
  

Fix information

• Fixed component name

  MQ Z/OS V9

• Fixed component ID

  5655MQ900

Applicable component levels

• R000 PSY UI52881

     UP18/02/01 P F801

Fix is available

• Select the PTF appropriate for your component level. You will be required to sign in. Distribution on physical media is not available in all countries.