IBM Support

PI33802: CONFUSION SURROUNDING DELETED PROCESSES RUNNING OUTSIDE OF SNAPSHOTS

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as Permanent restriction.

Error description

  • When you run an application process, you might see
    the incorrect number of process steps running in the child
    component process.  This is due to the application process
    calling a
    previously deleted component process with the same name.  The
    correct behavior would be for the process to fail or for the
    system to display an error message. The process previously
    deleted should not still  be available to run within an
    application
    process.
    
    Steps to reproduce:
    1. Create a component process
    2. Create an application process that contains only the previous
    component process
    3. Delete the component process
    4. Create a new component process with the same name
    5. Run the application process
    
    Actual results: the deleted component process is run instead of
    the
    new process with no warning or
    error.
    

Local fix

  • Change the application process design to use the new process
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * Any user who deletes a component process                     *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * Customer was confused when deleted processes were being run  *
    * as part of application processes that contained them         *
    * (expected/intended behavior).                                *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Upgrade to UCD 6.1.1.3                                       *
    ****************************************************************
    

Problem conclusion

  • Customers will now be presented with a more informative
    confirmation dialog when they delete a component process that
    informs them of this possibly counter-intuitive behavior and are
    provided with a list of affected application processes that are
    using the deleted component process. This change will be in UCD
    6.1.1.3.
    

Temporary fix

Comments

APAR Information

  • APAR number

    PI33802

  • Reported component name

    UC DEPLOY

  • Reported component ID

    5725M5400

  • Reported release

    610

  • Status

    CLOSED PRS

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2015-01-29

  • Closed date

    2015-03-27

  • Last modified date

    2015-03-27

  • APAR is sysrouted FROM one or more of the following:

  • APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

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

Document Information

Modified date:
17 October 2021