Fixes are available
Rational Build Forge Fix Pack 3 (8.0.0.3) for 8.0
Rational Build Forge Fix Pack 4 (8.0.0.4) for 8.0
Rational Build Forge Fix Pack 5 (8.0.0.5) for 8.0
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 a MJC based build using an adaptor link, any subsequent step that fails will cause the build to immediately purge as if the adaptor link step had failed. Steps to reproduce: - Create sample adaptor to perform simply echo command. <?xml version="1.0"?> <!-- (c) Copyright by IBM Corp. and other(s) [2003], 2007 All Rights Reserved. --> <!DOCTYPE PROJECT_INTERFACE SYSTEM "interface.dtd"> <PROJECT_INTERFACE IFTYPE="Source" INSTANCE="7.021"> <interface> <run command="echo" params="" server="$BF_SERVER" dir="/" timeout="360"/> <onstep result="fail"> </onstep> <onstep result="pass"> </onstep> <onproject result="pass"> </onproject> </interface> <command name="echo"> <execute> echo "Echoing" </execute> </command> </PROJECT_INTERFACE> - Create sample project that will fail the step. ie: Project: Test_Project - Step1: Echo Hello: echo hello - Step2: Fail the step: exit 1 - Link adaptor to Test_Project - Execute Test_Project with adaptor link Expected result: Build is marked as failed after executing step 2. Build is not immediately purged and the build number reverted. Actual result: Build is marked as failed after executing step 2. Step 2 is marked as adaptor link step. Build is immediately purged and the build number reverted.
Local fix
Use the .lock/.unlock dot commands at beginning and end of project to prevent build purging.
Problem summary
**************************************************************** * USERS AFFECTED: * * ALL * **************************************************************** * PROBLEM DESCRIPTION: * * MJC BUILD USING ADAPTOR LINK WILL PURGE IMMEDIATELY IF ANY * * STEP * * FAILS * **************************************************************** * RECOMMENDATION: * ****************************************************************
Problem conclusion
The issue was fixed in Build Forge 8.0.0.3 release
Temporary fix
Comments
APAR Information
APAR number
PI49355
Reported component name
BUILD FORGE EE
Reported component ID
5724S2701
Reported release
711
Status
CLOSED PER
PE
NoPE
HIPER
NoHIPER
Special Attention
NoSpecatt / Xsystem
Submitted date
2015-09-24
Closed date
2016-02-22
Last modified date
2016-02-22
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
5724S2701
Applicable component levels
R711 PSN
UP
Document Information
Modified date:
04 May 2022