PI54110: BF_TAG VARIABLE IS SET AFTER PROJECT ENVIRONMENT VARIABLES

Rational Build Forge Fix Pack 6 (8.0.0.6) for 8.0
Rational Build Forge Fix Pack 7 (8.0.0.7) for 8.0
Rational Build Forge Fix Pack 8 (8.0.0.8) for 8.0
Rational Build Forge Fix Pack 9 (8.0.0.9) for 8.0
Rational Build Forge Fix Pack 10 (8.0.0.10) for 8.0
Rational Build Forge Interim Fix 1 for 8.0.0.10
Rational Build Forge Fix Pack 11 (8.0.0.11) for 8.0
Rational Build Forge Interim Fix 1 for 8.0.0.11
Rational Build Forge Fix Pack 12 (8.0.0.12) for 8.0
Rational Build Forge Fix Pack 13 (8.0.0.13) for 8.0
Rational Build Forge Fix Pack 14 (8.0.0.14) for 8.0
Rational Build Forge Fix Pack 15 (8.0.0.15) for 8.0
Rational Build Forge Interim Fix 1 for 8.0.0.15
Rational Build Forge Fix Pack 16 (8.0.0.16) for 8.0
Rational Build Forge Fix Pack 17 (8.0.0.17) for 8.0
Rational Build Forge Fix Pack 19 (8.0.0.19) for 8.0
Rational Build Forge Fix Pack 18 (8.0.0.18) for 8.0
Rational Build Forge Fix Pack 20 (8.0.0.20) for 8.0
Rational Build Forge Fix Pack 21 (8.0.0.21) for 8.0
Rational Build Forge Fix Pack 22 (8.0.0.22) for 8.0

APAR status

• Closed as program error.

Error description

• Under Build Forge 7.1.3.6 and 8.0.0.2, the BF_TAG variable is
  set after the project configured environment variables, and thus
  cannot be reference by project environment variables. As the
  BF_TAG variable is undefined when a build is executed and the
  project environment variable is listed as the "BF_TAG".
  
  Steps to reproduce:
  - Create an environment with Name "ProjectEnv"
  - Make a new standard variable in ProjectEnv with Name "TAG" and
  Value "MyBuildTag_${BF_TAG}" (leave all other settings at
  default).
  - Make a new Project with Name "ProjectEnvBeforeBF_TAG", with
  Environment "ProjectEnv" and every other setting default (with
  the choice of Selector being at your discretion)
  - Add new step with Name "echo hello" and the Command being
  "echo hello" (this is just a placeholder step so we can observe
  the build step logs)
  - Click 'Start Project' then 'Execute', then look at the build
  step log for the 'echo hello' by clicking on the step's name.
  - In the filter text box, type "BF_TAG" and click the Filter
  button.
  
  Expected result:
  When TAG is set, it should be assigned a value of
  MyBuildTag_BUILD_1
  (BUILD_1 could end with a different number depending on how many
  builds were run before it, i.e. it could be BUILD_2, BUILD_3,
  ...)
  
  Actual result:
  When TAG is set, it is assigned a value of MyBuildTag_BF_TAG
  Also, the line before TAG being set says 'Reference to undefined
  variable: BF_TAG'
  

Local fix

• If possible, you can use the BF_TAG_PHYS variable instead of
  BF_TAG.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * The issue occurs on all supported platforms while using the  *
  * Perl Engine.                                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * BF_TAG variable is not set (available for use) until the     *
  * project environment is set.                                  *
  ****************************************************************
  * RECOMMENDATION:                                              *
  ****************************************************************
  

Problem conclusion

• The fix is available in Build Forge 8.0.0.6. Please note that
  Build Forge 7.1.3 is out of support. So the fix is delivered
  only on Build Forge 8.0
  

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

  BUILD FORGE EE

• Fixed component ID

  5724S2702

Applicable component levels

• R713 PSY

     UP