IBM Support

JR42474: MATCH COMMAND PARAM 2 IS NOT BEING TREATED AS OPTIONAL CORRECTLY.

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • This a bug that impacts the processing of a match command which
    has an optional Param 2 when only Param 1 is specified,  An
    example of such a command is DELTA_PERCENT.
    
    The documentation states that if only Param 1 is specified, it
    represents the maximum percentage difference that can be
    tolerated for either reference source value greater than data
    source value or data source value greater than reference source
    value.  Due to this bug, the Param 2 is not optional and must be
    specified to represent the maximum percentage difference that
    can be tolerated when reference source value is less than data
    source value.
    
    The workaround is to apply the same percentage value in Param 2
    as is used for Param 1.
    
    Background:
    In QS 7.x a nonexistent Param 2 was not acknowledged in the
    internal Match Specification representation. In the example
    below, 10 is the Param 1 value. There is no Param 2 value so the
    internal Match Specification representation entry ends with the
    Param 1 value. However, starting with 8.x, a nonexistent Param 2
    is acknowledged with a value of 0 (see below). The server is not
    expecting this, so the 0 value gets incorporated in the match
    calculations, thereby distorting the results.
    7.x - MATCH1 DELTA_PERCENT DURATIO DURATIO 0.9 0.01 10
    8.x - MATCH1 DELTA_PERCENT DURATIO DURATIO 0.9 0.01 10 0
    

Local fix

  • Workaround is to always set Param 2 on those match commands
    for which the documention says Param 2 is optional.
    

Problem summary

  • ****************************************************************
    USERS AFFECTED:
    Users of Match Designer using a match command which has an
    optional Param 2 when only Param 1 is specified.
    ****************************************************************
    PROBLEM DESCRIPTION:
    This a bug that impacts the processing of a match command which
    has an optional Param 2 when only Param 1 is specified,  An
    example of such a command is DELTA_PERCENT.
    
    The documentation states that if only Param 1 is specified, it
    represents the maximum percentage difference that can be
    tolerated
    for either reference source value greater than data source value
    or data source value greater than reference source value.  Due
    to
    this bug, the Param 2 is not optional and must be specified to
    represent the maximum percentage difference that can be
    tolerated
    when reference source value is less than data source value.
    
    ****************************************************************
    RECOMMENDATION:
    Either use a version of program that has this fixed (9.1 or
    later)
    or apply the same percentage value in Param 2 as is used for
    Param 1.
    ****************************************************************
    

Problem conclusion

  • Fix forces both params to be provided to the server ie creates
    the missing Param 2
    

Temporary fix

Comments

APAR Information

  • APAR number

    JR42474

  • Reported component name

    WIS QUALITYSTAG

  • Reported component ID

    5724Q36QS

  • Reported release

    850

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2012-04-06

  • Closed date

    2012-08-08

  • Last modified date

    2012-08-08

  • 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

    WIS QUALITYSTAG

  • Fixed component ID

    5724Q36QS

Applicable component levels

  • R850 PSN

       UP

  • R870 PSN

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSVSBF","label":"InfoSphere QualityStage"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"8.5","Edition":"","Line of Business":{"code":"","label":""}}]

Document Information

Modified date:
08 August 2012