Fix targeting binary creation bug

Missed the associated change in the targeting binary creation
that was required with the addition of 2 new association
entries.
Disable fapiGetOtherEnd testcases temporarily

Change-Id: Iddaa20a90140a61333bc40801b6d87b38bff0450
Reviewed-on: http://ralgit01.raleigh.ibm.com/gerrit1/22969
Reviewed-by: Martin Gloff <mgloff@us.ibm.com>
Tested-by: Jenkins Server
Tested-by: FSP CI Jenkins
Reviewed-by: Christian R. Geddes <crgeddes@us.ibm.com>
Reviewed-by: Daniel M. Crowell <dcrowell@us.ibm.com>

1 files changed, 3 insertions, 3 deletions

diff --git a/src/usr/targeting/common/xmltohb/xmltohb.pl b/src/usr/targeting/common/xmltohb/xmltohb.pl
index bf675a58e..597517af6 100755
--- a/src/usr/targeting/common/xmltohb/xmltohb.pl
+++ b/src/usr/targeting/common/xmltohb/xmltohb.pl
@@ -5787,9 +5787,9 @@ sub generateTargetingImage {
 
                     # Each target is 4 bytes # attributes, 8 bytes pointer
                     # to attribute list, 8 bytes pointer to attribute pointer
-                    # list, 4 x 8 byte pointers to association lists, for total
-                    # of 20 + 32 = 52 bytes per target
-                    $index *= (20 + 32); # length(N + quad + quad + 4x quad)
+                    # list, 6 x 8 byte pointers to association lists, for total
+                    # of 20 + 48 = 68 bytes per target
+                    $index *= (20 + 48); # length(N + quad + quad + 6x quad)
                     $attrhash{$attributeId}->{default} = $index + $firstTgtPtr;
                 }