Operands

MISSINGFIX

requests a report about missing FIXCAT APARs. That is, fixes for APARs that have an applicable and interesting fix category value.

MISSINGFIX is a required operand for the REPORT MISSINGFIX command.

FIXCAT

identifies the list of fix categories of interest to be reported on. This list determines which missing FIXCAT APARs are to be included in the report. SMP/E reports only the missing FIXCAT APARs identified by FIXCAT type ++HOLD statements with these fix categories.

The values specified on the FIXCAT operand will override the list of values, if any, defined by the FIXCAT subentry in the active OPTIONS entry.

Fix category values can be 1 to 64 characters in length and contain any nonblank character in the range X'41' - X'FE'except single quotation marks, commas, left parentheses, and right parentheses. The value can be specified in one of two ways:

Explicitly, by fully specifying a particular fix category value, such as IBM®.Device.zIIP, for example. In this case, all HOLDDATA associated with this fix category will be applicable to command processing.
Implicitly, by partially specifying a fix category value using any number of asterisks (*) as global characters and percent signs (%) as placeholders.
- A single asterisk indicates that zero or more characters can occupy that position. For example, IBM.Device* implies that all HOLDDATA associated with a fix category that begins with the character string IBM.Device are applicable *z/OS implies that all HOLDDATA associated with a fix category that ends with the character string z/OS® are applicable. Finally, IBM*z/OS implies that all HOLDDATA associated with a fix category that begins with the character string IBM and ends with the character string z/OS are applicable.
- A single percent sign indicates that any one single character can occupy that position. For example, IBM.Device.20%4 implies that HOLDDATA associated with any of the following fix categories is applicable: IBM.Device.2084, IBM.Device.2094, and IBM.Device.20t4. HOLDDATA associated with the fix category IBM.Device.20914, however, is not applicable.

Fix category values can contain mixed case alphabetic characters. However, SMP/E ignores the case when identifying matches for a specified Fix category value. For example, a specified value of IBM.FUNCTION.HEALTHCHECKER matches the value of IBM.Function.HealthChecker.

The following examples are acceptable fix category values:

IBM.Device.zIIP
*
IBM.Function* 
IBM.Device.20%4.*
IBM.HealthChecker

FORFMID

specifies the FMIDs used to limit which missing FIXCAT APARs are included in the report. This list can include FMIDs, FMIDSET names, or both. If FORFMID is specified, SMP/E reports only the missing APARs identified by ++HOLD statements with these FMIDs. If FORFMID is not specified, SMP/E reports all the missing FIXCAT APARs in the specified zones.

NOPUNCH

indicates that SMP/E should not write any output to SMPPUNCH. If NOPUNCH is not specified, sample SMP/E commands for installing the missing SYSMODs are written to SMPPUNCH. In addition, a sample RECEIVE command is created for ordering and receiving resolving SYSMODs that are not found in the global zone.

ZONES

specifies which zones SMP/E should report on. This list can include zone names, ZONESET names, or both. You can specify target zones, distribution zones, or any combination of these. SMP/E produces a separate report for each zone it checks.

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.