IC96828: INTERCHANGECONTROLNUMBER TAG IN PROCESS DATA IS INCORRECT WHEN OUTBOUND ENVELOPE USES "LIMIT INTERCHANGE SIZE" OPTION.

si_52_build_5020500_hotfix_7
si_52_build_5020500_interimfix_8
si_52_build_5020500_interimfix_8
si_52_build_5020500_interimfix_8

APAR status

• Closed as program error.

Error description

• When an outbound envelope uses the "maximum number of
  documents per interchange" or "limit interchange size" option
  to create multiple interchanges, then uses the option to
  "invoke business process for each interchange,"
  this tag in the invoked process contains the wrong interchange
  number:
    <InterchangeControlNumber>3</InterchangeControlNumber>
  
  The interchange number in that tag is the last interchange
  number generated and not the correct number for the interchange
  in the invoked process.
  

Local fix

• No workaround available
  STRRTC 396092
  AE/AE
  

Problem summary

• Users Affected:
  All users who are invoking a BP per interchange
  on outbound enveloping, with multiple interchanges.
  Problem Description:
  When an outbound envelope creates multiple interchanges and then
  uses the option to "invoke business process for each
  interchange," process data for the invoked process contains the
  wrong interchange control number.
  Platforms Affected:
  ALL
  

Problem conclusion

• Resolution Summary:
  A fix has been provided that obtains the Control number from the
  info array of interchanges processed rather than from the static
  variable, which only contains the last control number processed.
  Delivered In:
  5020500_8
  5020600
  

Temporary fix

• _5020402_71118646706_BRANCH
  _5050401_54297_BRANCH
  

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

  STR B2B INTEGRA

• Fixed component ID

  5725D0600

Applicable component levels