IBM Support

PI62273: PARAMETRIZED STUB CREATED INCORRECTLY WHEN DIFFERENT MESSAGE TYPES ARE USED

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • If you create a parametrized stub from a group of recorded
    messages that contains a single message of different type, the
    stub is created with reply sequencing.
    For example, one recorded message might have incorrect payload
    and returns a bad server HTTP status code.
    
    WORKAROUND:
    
    Inspect the events in Recording Studio and delete or deselect
    any incorrect request-reply messages you do not want to be
    included in the stub creation.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All users of Rational Integration Tester working with        *
    * parameterized stubs from a group of recorded messages that   *
    * contains a single message of a different type.               *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * If you create a parameterized stub from a group of recorded  *
    * messages that contains a single message of different type,   *
    * the stub is created with reply sequencing. For example, one  *
    * recorded message might have incorrect payload and returns a  *
    * bad server HTTP status code.                                 *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to Rational Integration Tester v9.0.1 which includes *
    * a fix for this issue                                         *
    ****************************************************************
    

Problem conclusion

  • A fix for this issue was provided in version 9.0.1 of Rational
    Integration Tester.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI62273

  • Reported component name

    RATL INTEGRA TE

  • Reported component ID

    5725G79IT

  • Reported release

    900

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2016-05-11

  • Closed date

    2016-09-20

  • Last modified date

    2016-09-20

  • 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

    RATL INTEGRA TE

  • Fixed component ID

    5725G79IT

Applicable component levels

  • R800 PSN

       UP

  • R801 PSN

       UP

  • R850 PSN

       UP

  • R851 PSN

       UP

  • R860 PSN

       UP

  • R870 PSN

       UP

  • R871 PSN

       UP

  • R900 PSN

       UP

  • R901 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSBLQQ","label":"Rational Test Workbench"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"900","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
17 October 2021