IT32965: MQ HEADER NODE IN ACE 11 OVERWRITES MESSAGE BODY IF NO PROPERTIES FOLDER IS PRESENT

APAR status

• Closed as program error.

Error description

• When the MQHeader node in ACE v11 is used to add an MQMD or
  MQDLH header to a message tree that does not have a Properties
  folder, then a blank MQMD or MQDLH header will be added as the
  first element in the message and the first element in the input
  message will be overwritten by a default MQMD or MQDLH in the
  output message.
  
  For example the following input message tree
  
  ( ['MQROOT' : 0x618000001080]
  (0x01000000:Object):JSON = ( ['json' : 0x61800000b880]
  (0x01000000:Object):Data = (
  (0x03000000:NameValue):Dummy = 'DATA' (CHARACTER)
  )
  )
  )
  
  will be incorrectly transformed to
  
  ( ['MQROOT' : 0x618000001080]
  (0x01000000:Name ):MQMD = ( ['MQHMD' : 0x619000700880]
  (0x03000000:NameValue):Format = '' (CHARACTER)
  )
  
  (0x01000000:Object):MQMD = ( ['json' : 0x61800000b880]
  (0x03000000:NameValue):SourceQueue = '' (CHARACTER)
  (0x03000000:NameValue):Transactional = FALSE (BOOLEAN)
  (0x03000000:NameValue):Encoding = 546 (INTEGER)
  (0x03000000:NameValue):CodedCharSetId = 0 (INTEGER)
  (0x03000000:NameValue):Format = ' ' (CHARACTER)
  (0x03000000:NameValue):Version = 1 (INTEGER)
  (0x03000000:NameValue):Report = 0 (INTEGER)
  (0x03000000:NameValue):MsgType = 8 (INTEGER)
  (0x03000000:NameValue):Expiry = -1 (INTEGER)
  (0x03000000:NameValue):Feedback = 0 (INTEGER)
  (0x03000000:NameValue):Priority = -1 (INTEGER)
  (0x03000000:NameValue):Persistence = 2 (INTEGER)
  (0x03000000:NameValue):MsgId =
  X'000000000000000000000000000000000000000000000000' (BLOB)
  (0x03000000:NameValue):CorrelId =
  X'000000000000000000000000000000000000000000000000' (BLOB)
  (0x03000000:NameValue):BackoutCount = 0 (INTEGER)
  (0x03000000:NameValue):ReplyToQ = '' (CHARACTER)
  (0x03000000:NameValue):ReplyToQMgr = '' (CHARACTER)
  (0x03000000:NameValue):UserIdentifier = '' (CHARACTER)
  (0x03000000:NameValue):AccountingToken =
  X'00000000000000000000000000000000000000000000000000000000000000
  00' (BLOB)
  (0x03000000:NameValue):ApplIdentityData = '' (CHARACTER)
  (0x03000000:NameValue):PutApplType = 0 (INTEGER)
  (0x03000000:NameValue):PutApplName = '' (CHARACTER)
  (0x03000000:NameValue):PutDate = '' (CHARACTER)
  (0x03000000:NameValue):PutTime = '' (CHARACTER)
  (0x03000000:NameValue):ApplOriginData = '' (CHARACTER)
  (0x03000000:NameValue):GroupId =
  X'000000000000000000000000000000000000000000000000' (BLOB)
  (0x03000000:NameValue):MsgSeqNumber = 1 (INTEGER)
  (0x03000000:NameValue):Offset = 0 (INTEGER)
  (0x03000000:NameValue):MsgFlags = 0 (INTEGER)
  (0x03000000:NameValue):OriginalLength = -1 (INTEGER)
  )
  )
  

Local fix

• Ensure that messages going into a MQHeader node have a
  Properties folder.
  

Problem summary

• ****************************************************************
  USERS AFFECTED:
  All users of the MQHeader node in IBM App Connect Enterprise
  v11.
  
  
  Platforms affected:
  MultiPlatform
  
  ****************************************************************
  PROBLEM DESCRIPTION:
  When the MQHeader node in ACE v11 is used to add an MQMD or
  MQDLH header to a message tree that does not have a Properties
  folder, then a blank MQMD or MQDLH header will be added as the
  first element in the message and the first element in the input
  message will be overwritten by a default MQMD or MQDLH in the
  output message.
  
  For example the following input message tree
  
  ( ['MQROOT' : 0x618000001080]
      (0x01000000:Object):JSON = ( ['json' : 0x61800000b880]
          (0x01000000:Object):Data = (
              (0x03000000:NameValue):Dummy = 'DATA' (CHARACTER)
          )
      )
  )
  
  will be incorrectly transformed to
  
  ( ['MQROOT' : 0x618000001080]
      (0x01000000:Name ):MQMD = ( ['MQHMD' : 0x619000700880]
          (0x03000000:NameValue):Format = '' (CHARACTER)
      )
  
      (0x01000000:Object):MQMD = ( ['json' : 0x61800000b880]
          (0x03000000:NameValue):SourceQueue = '' (CHARACTER)
          (0x03000000:NameValue):Transactional = FALSE (BOOLEAN)
          (0x03000000:NameValue):Encoding = 546 (INTEGER)
          (0x03000000:NameValue):CodedCharSetId = 0 (INTEGER)
          (0x03000000:NameValue):Format = ' ' (CHARACTER)
          (0x03000000:NameValue):Version = 1 (INTEGER)
          (0x03000000:NameValue):Report = 0 (INTEGER)
          (0x03000000:NameValue):MsgType = 8 (INTEGER)
          (0x03000000:NameValue):Expiry = -1 (INTEGER)
          (0x03000000:NameValue):Feedback = 0 (INTEGER)
          (0x03000000:NameValue):Priority = -1 (INTEGER)
          (0x03000000:NameValue):Persistence = 2 (INTEGER)
          (0x03000000:NameValue):MsgId =
  X'000000000000000000000000000000000000000000000000' (BLOB)
          (0x03000000:NameValue):CorrelId =
  X'000000000000000000000000000000000000000000000000' (BLOB)
          (0x03000000:NameValue):BackoutCount = 0 (INTEGER)
          (0x03000000:NameValue):ReplyToQ = '' (CHARACTER)
          (0x03000000:NameValue):ReplyToQMgr = '' (CHARACTER)
          (0x03000000:NameValue):UserIdentifier = '' (CHARACTER)
          (0x03000000:NameValue):AccountingToken =
  X'00000000000000000000000000000000000000000000000000000000000000
  00' (BLOB)
          (0x03000000:NameValue):ApplIdentityData = '' (CHARACTER)
          (0x03000000:NameValue):PutApplType = 0 (INTEGER)
          (0x03000000:NameValue):PutApplName = '' (CHARACTER)
          (0x03000000:NameValue):PutDate = '' (CHARACTER)
          (0x03000000:NameValue):PutTime = '' (CHARACTER)
          (0x03000000:NameValue):ApplOriginData = '' (CHARACTER)
          (0x03000000:NameValue):GroupId =
  X'000000000000000000000000000000000000000000000000' (BLOB)
          (0x03000000:NameValue):MsgSeqNumber = 1 (INTEGER)
          (0x03000000:NameValue):Offset = 0 (INTEGER)
          (0x03000000:NameValue):MsgFlags = 0 (INTEGER)
          (0x03000000:NameValue):OriginalLength = -1 (INTEGER)
      )
  )
  
  Note that the second MQMD element is actually an (invalid) JSON
  tree.
  

Problem conclusion

• The MQHeader node now correctly handles messages that do not
  have a Properties parser present.
  
  ---------------------------------------------------------------
  The fix is targeted for delivery in the following PTFs:
  
  Version    Maintenance Level
  v11.0      11.0.0.10
  
  The latest available maintenance can be obtained from:
  http://www-01.ibm.com/support/docview.wss?rs=849&uid=swg27006041
  
  If the maintenance level is not yet available,information on
  its planned availability can be found on:
  http://www-1.ibm.com/support/docview.wss?rs=849&uid=swg27006308
  ---------------------------------------------------------------
  

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

• Fixed component name

  APP CONNECT ENT

• Fixed component ID

  5724J0550

Applicable component levels