GIM30206E — SMP/E APPLY failed: hold reason IDs not resolved

SMP/E refused to install a SYSMOD because it is held. The GIM359xx messages that follow name each hold and its type.

What happened

An SMP/E APPLY (or APPLY CHECK) ended with return code 12. The SMPOUT/SMPRPT shows GIM30206E for one or more SYSMODs, followed by messages naming holds, and possibly GIM37001S stopping processing because a FUNCTION failed.

APPLY CHECK output (illustrative)Illustrative example

GIM30206E ** APPLY PROCESSING FAILED FOR SYSMOD UJ10001. HOLD REASON IDS WERE NOT RESOLVED.
GIM35965I    SYSTEM HOLD DOC ORIGINATED BY SYSMOD UJ10001 WAS NOT RESOLVED.
GIM35901I    ERROR HOLD AA12345 WAS NOT RESOLVED.
GIM35907I    PREREQUISITE SYSMOD UJ09990 FAILED.

What it means

SMP/E could not process the SYSMOD because it is held and at least one reason ID was not resolved. Holds come from HOLDDATA (++HOLD) and are of several types:

ERROR — the SYSMOD is in error (for example a PTF in error, PE). The fix is another SYSMOD that resolves the APAR.
SYSTEM — an action is required around the install, such as documentation to read (DOC) or a restart.
USER — a hold your site added.
FIXCAT — the SYSMOD belongs to a fix category whose required fixes are missing.

Related messages explain each case: GIM35901I for an unresolved error hold, GIM35949I when a fix that would have superseded the held APAR also failed, GIM35955I when a conditional requisite is missing, and GIM35907I when a prerequisite failed.

Typical causes

HOLDDATA received after the PTFs: some of them are now in error (PE).
The fixing PTF for an error hold has not been RECEIVEd.
SYSTEM holds (DOC, restart actions) that need a decision before install.
A prerequisite or requisite SYSMOD that is missing or failed itself.

Symptoms

APPLY RC=12; some SYSMODs applied, others not.
A chain of GIM35907I for SYSMODs that depend on the held one.

Where to look

SMPOUT for GIM30206E and the GIM359xx lines below it.
SMPRPT reports — the SYSMOD status and causer reports.
The HOLDDATA text for each reason ID (comments often name the fixing PTF).
The CSI zones, to see what is RECEIVEd and APPLYd.

How to diagnose

List every GIM359xx message: reason ID and hold type.
For ERROR holds, find the fixing PTF named in the HOLDDATA comment and check whether it is received.
For SYSTEM holds, read the hold text and plan the action.
For FIXCAT holds, identify the missing fixes in that category.
Run REPORT ERRSYSMODS to list SYSMODs with outstanding errors.

How to fix

Receive current Enhanced HOLDDATA and the fixing PTFs (for example with RECEIVE ORDER CONTENT(HOLDDATA)), then rerun APPLY CHECK. For SYSTEM holds, perform the documented action and then bypass with the specific reason, e.g. BYPASS(HOLDSYS(DOC)). Bypass an ERROR hold, e.g. BYPASS(HOLDERROR(AA12345)), only when IBM or the vendor says it is safe. SMP/E then treats the reason as resolved, but the underlying problem is still yours.