IBM Support

PI17682: UNABLE TO TELL WHICH COMPONENT TEMPLATE PROCESS PROPERTY WILL GO TO WHICH COMPONENT

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • To recreate this:
    
    1) Create a component Template.  Add a property to the process
    (ex:  templateProp). Give the property a label value.  Create a
    process that calls a shell step to echo the process property.
    
    2) Create a component from this component template.
    
    3) Create another component from the component template.
    
    4) Add these components to an application and install these
    components in an application process.
    
    5) Add an environment and map the components.
    
    5) Select the Request Process link:
    
    RESULTS:
    
    The property from the template, "templateProp", will appear
    twice - once for each component.  However, you cannot tell which
    property will go to which component.
    

Local fix

  • Create an application process property for each component.  Then
    edit the application process step that contains the component
    template process property and hard code the value to ${p:<the
    application process property created for the component>}
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Any                                                          *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Issues associating component templates with components       *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • A fix is provided in IBM UrbanCode Deploy 6.0.1.5
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI17682

  • Reported component name

    UDEPLOY

  • Reported component ID

    5725M7700

  • Reported release

    500

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt

  • Submitted date

    2014-05-09

  • Closed date

    2014-05-28

  • Last modified date

    2014-05-28

  • 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

    UDEPLOY

  • Fixed component ID

    5725M7700

Applicable component levels

  • R500 PSN

       UP

  • R500 PSY

       UP

[{"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SS4JV8","label":"IBM uDeploy"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"500","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
17 October 2021