PI06172: APPLICATION PROCESS RUNS INDEFINITELY AFTER REJECTING MANUAL TASK

APAR status

• Closed as program error.

Error description

• Environment:
  IBM uDeploy 4.8.5
  IBM UrbanCode 6.0
  
  Steps to reproduce:
  
  Environment:
  IBM uDeploy 4.8.5
  IBM UrbanCode 6.0
  
  Problem description
  Attempts to run a particular application process result in the
  process remaininf indeifinitely in "Running" state.
  This occurs after rejecting Manual task.
  
  Steps to reproduce:
  
  1. Create 4 Components that use Shell scripts:
  RunShellScript1 - This must always suceed, e.g.
  echo ${p:component.name}
  RunShellScript2 - This must always fail, e.g.
  exit 1
  RunShellScript3 - This must always suceed, e.g
  echo ${p:component.name}
  RunShellScript3 - This must always suceed, e.g.
  echo ${p:component.name}
  
  2. Create an Application and add the 4 components
  
  3. Create an Application process that installs the 4 Components.
  For simplicity, name each Application Installation Step as the
  corresponding Component. Create an Application process with the
  following edges:
  
  Start -> RunShellScript1
  
  RunShellScript1 -> RunShellScript2 on SUCCESS
  
  RunShellScript1 -> RunShellScript4 on SUCCESS
  
  RunShellScript4 -> Finish on SUCCESS
  
  RunShellScript2 -> Manual Task on FAIL
  
  RunShellScript2 -> RunShellScript3 on either FAIL or SUCCESS
  
  RunSgellScript3 -> RunShellScript4 on SUCCESS
  
  4. Execute the above process.
  
  5. When the process reached the Manual Task, Reject
  
  Result:
  
  RunShellScript1 : Success
  RunShellScript2 : Failed
  Manual Task     : Failed (Rejected by user)
  RunShellScript3 : Not Started
  RunShellScript4 : Not Started
  Total Execution : Running
  

Local fix

• The process remains Running until it is canceled by the user.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All end users                                                *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Processes sometimes hang indefinitely when encountering      *
  * complex join scenarios.                                      *
  *                                                              *
  * Internal cause: When a step failed, it was marking it's      *
  * outgoing edges as NOT NEEDED, but that status did not        *
  * cascade through child steps.                                 *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Fix is provided in IBM UCD 6.0.1                             *
  ****************************************************************
  

Problem conclusion

• Processes now complete as intended.
  

Temporary fix

Comments

APAR Information

• 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

• R600 PSY

     UP