Only call PRD attention handling in resetPMComplex function at runtime.

HB can't call PRD handling after istep 16.4.  If this util function
happens to be called after that istep but before runtime, we may see
some unwanted PRD errors.

Change-Id: Ie4f9a55fe1e74f7835d9f30531b757a79d36b14e
CQ:SW448154
Reviewed-on: http://rchgit01.rchland.ibm.com/gerrit1/67621
Tested-by: Jenkins Server <pfd-jenkins+hostboot@us.ibm.com>
Tested-by: Jenkins OP Build CI <op-jenkins+hostboot@us.ibm.com>
Tested-by: Jenkins OP HW <op-hw-jenkins+hostboot@us.ibm.com>
Tested-by: FSP CI Jenkins <fsp-CI-jenkins+hostboot@us.ibm.com>
Reviewed-by: Nicholas E. Bofferding <bofferdn@us.ibm.com>

src/usr/isteps/pm/pm_common.C

@@ -958,11 +958,13 @@ namespace HBPM
                        "resetPMComplex: p9_pm_init(PM_RESET) succeeded "
                        "HUID=0x%08X", get_huid(i_target) );
 
+#ifdef __HOSTBOOT_RUNTIME
+
             // Explicitly call ATTN before exiting to ensure PRD handles
             // LFIR before TMGT triggers PM Complex Init, but only if
             // we aren't already in the middle of handling a core checkstop
             if( HB_INITIATED_PM_RESET_IN_PROGRESS != l_chipResetState )
-            {               
+            {
                 // set ATTR_HB_INITIATED_PM_RESET to IN_PROGRESS to avoid recursion
                 i_target->setAttr<ATTR_HB_INITIATED_PM_RESET>
                                 (HB_INITIATED_PM_RESET_IN_PROGRESS);
@@ -982,6 +984,9 @@ namespace HBPM
                     break;
                 }
             }
+
+#endif
+
         } while(0);
 
         if ((TARGETING::is_phyp_load()) && (nullptr != l_homerVAddr))