IBM Support

PK60105: Build Forge upgrade to 7.0.2 breaks existing CQ integration

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Upgrading Build Forge from 7.0.1 to 7.0.2 breaks the existing CQ
    configuration.  After the upgrade, builds using the CQ integrat
    ion will cause a error that an invalid build record was returned
     from CQ.  The upgrade should not break the CQ configuration, ra
    ther it should have a provision to work the same way or automati
    cally update the existing integration.
    

Local fix

Problem summary

  • upgrade to 7.0.2 causes CQ integration to return invalid
    build record.
    

Problem conclusion

  • the entity "dtrelease" is relied on in 7.0.2 and later.  a
    check was added to make sure it existed
    

Temporary fix

Comments

APAR Information

  • APAR number

    PK60105

  • Reported component name

    BUILD FORGE EE

  • Reported component ID

    5724Q6101

  • Reported release

    700

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2008-01-29

  • Closed date

    2009-06-29

  • Last modified date

    2009-06-29

  • 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

    BUILD FORGE EE

  • Fixed component ID

    5724Q6101

Applicable component levels

  • R700 PSN

       UP

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

Document Information

Modified date:
29 June 2009