IBM Support

PI95195: COMPONENT PROCESS PROPERTY VALUE SET AT THE APPLICATION LEVEL INTO WRAPPED COMPONENT PROCESS

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

  • There is a use cases where component process properties are not
    passed into child processes correctly. This will result in an
    error indicating that required properties are missing. This can
    be demonstrated with the following steps:
    
    1) Create an operational, no version needed, component process
    and add a component process property. This process can do as
    little as echo the property in a shell step.
    2) Create a second operational, no version needed, component
    process. This process should have a single activity which runs
    the first operational process. The value for the component
    process property should be left as 'Prompt for value on use' or
    'Set a value here' depending on if the legacy option 'Prompt for
    value on use' is enabled.
    3) Create an application process which runs the second, wrapper,
    component process. For the component process property which can
    be given a value specify one.
    4) Execute the application process
    expected: the process resolves in the shell step correctly
    actual: the application process fails because the property is
    not defined. If you examine the application property context and
    the property context of the wrapper component process you will
    see that neither have the property defined in the context.
    

Local fix

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Users on UrbanCode Deploy 6.2.7.0 and later                  *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Application process properties not being passed to child     *
    * processes.                                                   *
    ****************************************************************
    * RECOMMENDATION:                                              *
    ****************************************************************
    

Problem conclusion

  • The properties are now being passed down to the child processes.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI95195

  • Reported component name

    UC DEPLOY

  • Reported component ID

    5725M5400

  • Reported release

    627

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-03-14

  • Closed date

    2018-09-24

  • Last modified date

    2018-09-24

  • 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":"627","Edition":"","Line of Business":{"code":"LOB45","label":"Automation"}}]

Document Information

Modified date:
24 September 2018