PM62734: Build Forge sticky not being honored during runtime

APAR status

• Closed as program error.

Error description

• When sticky is set for a project all steps should run on the
  same server. Build Forge sticky not being honored during runtime
  and some steps use a different server.
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  Cause
  This is a regression defect since 7130. The sticky for all
  the dynamically generated steps are not being honored. This
  defect is about the while loop steps generated during
  execution. Before the project execution, only one loop step
  is populated for while step. All the other iteration steps
  are dynamically generated and those steps are not being
  honored for sticky.
  
  Fix
  Ensure the project and inline's sticky server is cached once
  it is selected and can be referred for dynamically generated
  steps
  

Problem conclusion

• Fixed in 7.1.3.3
  

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

  IBM INSTALL MGR

• Fixed component ID

  RATLIMG00

Applicable component levels

• R120 PSN

     UP