IBM Support

PH08798: SOURCE CONFIG PLUGIN MIGRATOR DOES NOT CHECK A COMPONENT'S COMPONENT TEMPLATE'S PROPSHEET VALUES

Subscribe to this APAR

By subscribing, you receive periodic emails alerting you to the status of the APAR, along with a link to the fix after it becomes available. You can track this item individually or track all items by product.

Notify me when this APAR changes.

Notify me when an APAR for this component changes.

 

APAR status

  • Closed as program error.

Error description

  • When a user upgrades a source config plugin with a component
    that uses component template, the source config plugin will not
    read the propsheet values in the component template and throw a
    NPE because the component does not have a propsheet. The correct
    behavior should be that the migrator reads the propsheet values
    from the component template or just skip the migration process
    for components with component templates since component
    templates are migrated separately.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * All end users on all supported browsers.                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * When a user upgrades a source config plugin with a component *
    * that uses component template, the source config plugin will  *
    * not                                                          *
    * read the propsheet values in the component template and      *
    * throw a                                                      *
    * NPE because the component does not have a propsheet. The     *
    * correct                                                      *
    * behavior should be that the migrator reads the propsheet     *
    * values                                                       *
    * from the component template or just skip the migration       *
    * process                                                      *
    * for components with component templates since component      *
    * templates are migrated separately.                           *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Fixed in version 7.0.3.2                                     *
    ****************************************************************
    

Problem conclusion

  • Fix is provided in IBM UrbanCode Deploy 7.0.3.2
    

Temporary fix

Comments

APAR Information

  • APAR number

    PH08798

  • Reported component name

    UC DEPLOY

  • Reported component ID

    5725M5400

  • Reported release

    701

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2019-02-20

  • Closed date

    2019-08-06

  • Last modified date

    2019-08-06

  • 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

    UC DEPLOY

  • Fixed component ID

    5725M5400

Applicable component levels

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS4GSP","label":"IBM UrbanCode Deploy"},"Component":"","ARM Category":[],"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"701","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
06 August 2019