PK92106: MQCIH OUTPUT FIELDS IN A REPLY MESSAGE FOLLOWING AN ERROR IN THE CKBP BRIDGE TASK.

Obtain the fix for this APAR.

APAR status

• Closed as program error.

Error description

• You have an MQ DPL Bridge task get an error like, for instance,
  a PGMIDERR on the link to the target program.  In the reply
  message, the MQCIH fields  ReturnCode , CompCode , and Reason
  are all binary zeroes.  They should instead contain the codes
  indicating what the error was.  Also, following the CIH in
  the reply message would normally be an error message giving
  more details about the error.  But this area is all blanks.
  .
  Furthermore, you find that this MQCIH output field problem
  happens when you have started the Bridge Monitor with
  ROUTEMEM=Y .  When you don't start the Bridge Monitor with
  ROUTEMEM=Y, the MQCIH output fields are correct.
  .
  Here is an example of a reply message following an error when
  not using ROUTEMEM=Y:
  ----------------------------------------------------------------
  000                   C3C9C840 00000002         CIH ....
  008 000000B4 00000000 00000000 D4D8E2E3 ............MQST
  018 D9404040 00000000 00000007 0000001B R   ............
  028 00000003 00000110 FFFFFFFE 00000001 ................
  038 FFFFFFFF 00000000 00000000 00000000 ................
  048 00000000 00000000 00000000 F0F2F0F8 ............0208
  058 00404040 5C5C5C5C 5C5C5C5C 40404040 .   ********
  068 40404040 40404040 40404040 40404040
  078 40404040 40404040 40404040 40404040
  088 40404040 40404040 40404040 40404040
  098 40404040 40404040 40404040 00000000             ....
  0A8 00000000 00000000 00000000 C4C6C8D4 ............DFHM
  0B8 D8F0F7F5 F140C540 C9E8D5E7 C940C3D2 Q0751 E IYNXI CK
  0C8 C2D740F0 F0F1F4F4 40C5C9C2 D9C5E2D7 BP 00144 EIBRESP
  0D8 7EF2F740 C5C9C2D9 C5E2D7F2 7EF3404B =27 EIBRESP2=3 .
  0E8 E4958182 938540A3 9640D3C9 D5D240A3 Unable to LINK t
  0F8 96409799 96879981 9440D4D6 C3C9C2C2 o program MOCIBB
  108 D9E64B40 40404040 40404040 40404040 RW.
  --------------------------------------------------------
  In this example, at +X'20' the Return Code is 00000007
  meaning MQCRC_PROGRAM_NOT_AVAILABLE .  At +X'24' is 0000001B
  which is CompCode which is the EIBRESP PGMIDERR (decimal 27).
  And at +X'28' is 00000003 which is Reason or EIBRESP2 .
  .
  Here is an example of this same error when using ROUTEMEM=Y .
  .
  000 F0F0F3F2 F0407A40 C3C9C840 00000002 00320 : CIH ....
  008 000000B4 00000000 00000000 D4D8E2E3 ............MQST
  018 D9404040 00000000 00000000 00000000 R   ............
  028 00000000 00000111 FFFFFFFE 00000001 ................
  038 FFFFFFFF 00000000 00000000 00000000 ................
  048 00000000 00000000 00000000 40404040 ............
  058 40404040 40404040 40404040 40404040
  068 40404040 40404040 40404040 40404040
  078 40404040 40404040 40404040 40404040
  088 40404040 40404040 40404040 40404040
  098 40404040 40404040 40404040 00000000             ....
  0A8 00000000 00000000 00000000 40404040 ............
  0B8 40404040 40404040 40404040 40404040
  0C8 40404040 40404040 40404040 40404040
  0D8 40404040 40404040 40404040 40404040
  0E8 40404040 40404040 40404040 40404040
  0F8 40404040 40404040 40404040 40404040
  ....
  In this example ReturnCode and CompCode and Reason are
  all binary zeroes and there is no message.
  

Local fix

• Do not use ROUTEMEM=Y
  

Problem summary

• ****************************************************************
  * USERS AFFECTED: All                                          *
  ****************************************************************
  * PROBLEM DESCRIPTION: During backout processing with          *
  *                      ROUTEMEM=Y as a CICS Bridge start       *
  *                      parameter, reply messages do not        *
  *                      contain details of the error that       *
  *                      caused backout.                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  When a problem occurs either in the application linked to by
  DFHMQBP0 or in the EXEC CICS LINK command itself DFHMQBP0
  performs backout processing. As part of this processing a
  message should be PUT to the specified ReplyToQueue containing
  details of the error that caused backout to occur. However when
  the bridge is started with ROUTEMEM=Y error details are
  sometimes missing from the reply message. This happens due to a
  timing window in which the backed out request message can be
  reprocessed by the bridge monitor before the TSQ that tracks the
  message for ROUTEMEM processing is deleted.
  

Problem conclusion

• Module DFHMQBP0 is changed to delete the TSQ tracking a message
  once the message has been successfully gotten thereby ensuring
  it has no affect on possible subsequent backout processing.
  

Temporary fix

• FIX AVAILABLE BY PTF ONLY
  

Comments

APAR Information

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

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

  PM01359 UK52933

Modules/Macros

•    DFHMQBP0 DFHMQBP2 DFHMQP0@ DFHMQP1@ DFHMQP2@
  

Fix information

• Fixed component name

  CICSTS V3 Z/OS

• Fixed component ID

  5655M1500

Applicable component levels

• R503 PSY UK52933

     UP09/12/21 P F912

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.