SMP/E APPLY CHECK reports HOLD actions - interpretation assistance

Hello,

During pre-production validation of a coordinated maintenance window, SMP/E APPLY CHECK reported multiple HOLD actions for a DB2 and z/OS function APAR bundle. Excerpt from the summary:

text
GRO HOLD1234 HOLD - REQUIRED BY FIX CAT123456
GRO HOLD5678 HOLD - PE RESOLVING FIX CAT789012

The SMP/E User's Guide explains:

HOLD actions indicate that specified elements were not applied because prerequisite conditions were not satisfied.

1. Should HOLD entries always block promotion when APPLY CHECK is clean otherwise?
2. Is there a recommended report command to list resolving FIXCAT relationships before we open a release management ticket?

Thank you for any pointers.
Bill

HOLD during CHECK is informational unless your change policy treats unresolved HOLD as a hard stop. We run REPORT MISSINGFIX and REPORT ERRORS before APPLY in QA.

For FIXCAT chains, QUERY FIXCAT (FIXCAT sourceid) on the held SYSMOD usually clarifies the dependency.

QUERY FIXCAT identified a missing prerequisite in the same bundle. We will reorder the receive order and re-run CHECK. Appreciate the command reference.