IBM Support

PK92519: Not all end-states are taken into account for parent/child check.

A fix is available

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • A parent CR/PR can not be concluded if a child CR/PR is set
    to?the duplicate_not_reproducible or duplicate_rejected state.
    
    This is not the desired behavior as both duplicate states have
    to be considered as a valid end-state.?
    
    To fix it?we needed to modify the child
    verification?pre-condition trigger (checkRelatedAttr.pl)?being
    used in the lifecycle?. In the script, a list of valid end
    states is supplied to the script in command argument3 as per the
    commented description in the file itself...
    
    #??????????????????????? ?description?
    #?????????????????????????The allowed values of the attribute.If
    there is more than one value,
    #?????????????????????????use semicolon as a separator
    
    In?this specific case, this argument would have to include the
    above mentioned rejected states.
    

Local fix

  • To fix it we needed to modify the child verification
    pre-condition trigger (checkRelatedAttr.pl) being used in the
    lifecycle . In the script, a list of valid end states is
    supplied to the script in command argument3 as per the commented
    description in the file itself...
    
    #                        <description>
    #                         The allowed values of the attribute.If
    there is more than one value,
    #                         use semicolon as a separator
    
    In this specific case, this argument would have to include the
    abovementionedrejected states.
    

Problem summary

  • Not all end-states are taken into account for parent/child
    check.
    

Problem conclusion

  • Fixed in Rational Change 5.3.
    
    The pre-condition trigger verify.js for the transition
    evaluated2concluded has been updated to allow parent CR to
    transition to concluded state if child CR is set to
    duplicate_not_reproducible or duplicate_rejected state.
    

Temporary fix

  • Update the pre-trigger to evaluated2concluded in ECP_process.xml
    as follows:
    
    verify: bsf verify.js -ifattr
    "crstatus=probreject,forwarded,duplicate,concluded,duplicate_con
    cluded,rejected,not_reproducible,duplicate_not_reproducible,dupl
    icate_rejected" -rel child_problem
    verify: bsf verify.js -ifattr
    "crstatus=rcr_applied,rcr_rejected" -rel associated_rcr
    

Comments

APAR Information

  • APAR number

    PK92519

  • Reported component name

    TLOGIC CHANGE

  • Reported component ID

    5724V87CG

  • Reported release

    520

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2009-07-28

  • Closed date

    2011-06-14

  • Last modified date

    2011-06-14

  • 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

    TLOGIC CHANGE

  • Fixed component ID

    5724V87CG

Applicable component levels

  • R530 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSYQQ2","label":"Rational Change"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"5.2","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
14 June 2011