Processing

The REPORT MISSINGFIX command checks the zones specified on the ZONES operand to determine if there are any missing fixes based on the fix categories of interest.
SMP/E then verifies that each target and distribution zone specified on the ZONES operand is defined in the global zone as either a ZONESET entry or as a zone with a ZONEINDEX subentry. The zones and ZONESETs specified on the ZONES operand (including the global zone) are used to create a list of zones to be reported on. For each specified value, SMP/E first checks for a ZONESET with the same name. If none is found, SMP/E checks for a zone with the same name. If a ZONESET and a zone both exist with the same name, then the ZONESET is used.
Only target and dlib zones may be reported on. The global zone is ignored if specified within a ZONESET.
If NOPUNCH was not specified, the SMPPUNCH data set is allocated. In addition, if FORFMID was specified, the FMIDs and FMIDSETs specified on the FORFMID operand are used to create a list of FMIDs to be reported on.
The purpose of the REPORT MISSINGFIX command is to analyze only the FIXCAT type HOLDDATA that has a fix category of interest. If the FIXCAT operand was specified on the command, the values specified are used as the active fix category list. Otherwise, the values in the FIXCAT subentry of the active OPTIONS entry are used.
FIXCAT HOLDDATA entries identify APARs associated with one or more fix categories for a held SYSMOD. SMP/E makes a list of FIXCAT type HOLDDATA entries to be reported on by analyzing all FIXCAT type HOLDDATA entries found in the global zone. HOLDDATA entries will be considered for the report if one or more of the entry's fix category values matches one or more category values in the active interest list, and the FORFMID operand was not specified, or the FORFMID operand was specified and the entry's FMID matches a value in the FMID list.
For each target or dlib zone in the zone list, SMP/E processes the list of FIXCAT type HOLDs to determine which APARs to report as missing. For each FIXCAT type HOLD, SMP/E determines if the held SYSMOD is installed in the target or dlib zone. If the held SYSMOD is installed, then SMP/E determines if the APAR reason ID is installed or superseded. If the APAR SYSMOD is not installed or superseded, then it is "missing" and included in the report.
After SMP/E identifies all missing APARs, SMP/E must then find in the global zone all SYSMODs that may resolve the missing APAR. A resolving SYSMOD is the fixing PTF identified by the RESOLVER operand on the FIXCAT ++HOLD statement (if specified), and any SYSMOD in the global zone that supersedes the missing APAR. SMP/E includes each resolving SYSMOD it finds in the report.
In addition, for each resolving SYSMOD, SMP/E determines if the SYSMOD is received in the global zone and if it is held for one or more ERRORs. If a SYSMOD entry exists in the global zone and the entry is not in Error status, then SMP/E considers the resolving SYSMOD as received and reports it as such. If the SYSMOD has one or more HOLDERR subentries in the global zone, SMP/E reports its status as HELD. Otherwise, SMP/E reports SYSMOD status as GOOD.
If any resolving SYSMODs are reported with a status of HELD, SMP/E produces the second part of the Missing FIXCAT SYSMOD reportt, Fixes for Held Resolving SYSMODs.
More specifically, SMP/E reports each unique ERROR HOLD for the held resolving SYSMODs (each unique APAR). For each ERROR HOLD, SMP/E must find in the global zone all SYSMODs that may resolve the ERROR HOLD. Resolving SYSMODs are the fixing PTF identified by the FIX operand in the SMRTDATA of the ++HOLD ERROR statement (if specified), and any SYSMOD in the global zone that supersedes the ERROR HOLD reason ID. SMP/E includes each resolving SYSMOD found in the report.

In addition, for each resolving SYSMOD, SMP/E determines if the SYSMOD is received in the global zone and if it is also held for one or more ERRORs. If a SYSMOD entry exists in the global zone and the entry is not in Error status, then the resolving SYSMOD is considered received and reported as such. If the SYSMOD has one or more HOLDERR subentries in the global zone, then its status in the report is HELD. Otherwise, its status in the report is GOOD. If a resolving SYSMOD is reported with a status of HELD, then it too will be reported as a HELD SYSMOD in this part 2 of the report.
After all reports are produced and if the NOPUNCH operand is NOT specified, then SMP/E generates the sample commands and writes them to the SMPPUNCH data set.