Fix Category HOLDDATA

SMP/E has been extended to help simplify the task of verifying required software fixes identified in Preventive Service Planning (PSP) buckets are installed. PSP buckets identify required software fixes for new hardware devices, toleration and coexistence of new software releases, and for enabling new functions. IBM consolidates the lists of required fixes from PSP buckets and produces new Fix Category (FIXCAT) HOLDDATA to identify those fixes. Some example fix categories are IBM.Device.z9-BC-2096 and IBM.Coexistence.z/OS.V1R10. SMP/E uses the new type of ++HOLD statement to identify APARs, their fix categories, and the PTF that resolves the APAR.

When FIXCAT HOLDDATA statements are received into a global zone, SMP/E assigns the fix category values as sourceids to the PTFs that resolve the APARs. These sourceids then simplify selecting and installing required fixes. During APPLY and ACCEPT command processing you can specify the assigned sourceids on the SOURCEID and EXSRCID operands to select the SYSMODs associated with a particular fix category.

In addition, for the APPLY and ACCEPT commands you can specify which Fix Categories are of interest using the new FIXCAT operand. This tells SMP/E to process only FIXCAT HOLDDATA for the categories you specify, and all others are ignored.

Finally, SMP/E uses the new FIXCAT HOLDDATA to identify what required fixes are missing. A new REPORT MISSINGFIX command analyzes the new FIXCAT HOLDDATA and determine which fixes (APARs) identified by the HOLDDATA are not yet installed. Only the fixes associated with the fix categories of interest to you, specified by you, are analyzed and identified. For example, you can identify only the missing fixes associated with a particular hardware device or coexistence for a specific new software release.

When change was introduced: SMP/E for z/OS V3R5 (z/OS V1R10).

Long Sourceids

SMP/E has increased the maximum length allowed for a sourceid value from 8 characters to 64 characters. In addition, the wildcard characters "*" and "%" can be used to implicitly select a list of sourceids for SMP/E commands that support their use. Sourceids can be defined on ++ASSIGN statements, on the SOURCEID operand of the RECEIVE command, and derived from fix categories specified on FIXCAT HOLDDATA statements.

When change was introduced: SMP/E for z/OS V3R5 (z/OS V1R10).

ZONEEDIT command enhancements

The ZONEEDIT command has been extended to allow wildcard specifications in the conditional CHANGE subcommand, and to allow the UNIT, VOLUME and WAITFORDSN subentries for DDDEF entries to be added if they do not already exist. Formerly the ZONEEDIT command only allowed existing subentries to be changed, but did not allow subentries to be added.

When change was introduced: SMP/E for z/OS V3R5 (z/OS V1R10).

HTTPS and FTP Reconnect and Retry support

SMP/E has added reconnect and retry capabilities for HTTPS and FTP operations that fail due to apparent network outages and anomalies. This will help prevent SMP/E RECEIVE command and GIMGTPKG service routine failures because of short lived network outages.

When change was introduced: SMP/E for z/OS V3R5 (z/OS V1R10).

RECEIVE ORDER command enhancements (Part 1)

The RECEIVE ORDER command has been extended to resubmit orders when the request cannot be satisfied. Specifically, if an order request for CRITICAL, RECOMMENDED, or ALL PTFs results in no applicable PTFs, SMP/E will resubmit the order to obtain the latest HOLDDATA.

When change was introduced: Integrated in SMP/E for z/OS V3R5 (z/OS V1R10) and available in SMP/E for z/OS V3R4 (z/OS V1R7) with PTF UO00335.

RECEIVE ORDER command enhancements (Part 2)

When you specify PTFs by name or you request PTFs to fix specified APARs but not all requested PTFs are found or available, SMP/E will resubmit the order to only obtain those requested PTFs that can be found by the server.

In addition, when a requested order cannot be fulfilled within the WAIT time specified (or defaulted), SMP/E will now end the RECEIVE command with a return code of 12 rather than 4. This helps differentiate a failing operation from a successful one.

When change was introduced: SMP/E for z/OS V3R5 (z/OS V1R10).

HOLDDATA report changes

SMP/E has defined a new report destination, SMPHRPT, for HOLDDATA reports. If the SMPHRPT ddname is allocated (either by DD statement or DDDEF entry), the HOLDDATA reports produced by the RECEIVE, APPLY and ACCEPT commands will be written to this ddname while other reports are written to the SMPRPT ddname. If the SMPHRPT ddname is not allocated, all reports are written to SMPRPT. If you do not want to review the APPLY, ACCEPT or RECEIVE command HOLDDATA reports, you can define SMPHRPT as a DUMMY data set. For example: //SMPHRPT DD DUMMY

In addition, the Bypassed HOLD Reason Report for the APPLY and ACCEPT commands now includes only bypassed HOLDDATA for SYSMODs that are successfully applied or accepted. No longer will bypassed HOLDDATA for SYSMODs that fail command processing appear in the report. This eliminates clutter and limits the report to only the HOLDDATA that must be reviewed or acted upon.

Finally, suppressed reasonids will be consolidated and reported only once per FMID in the APPLY and ACCEPT command HOLDDATA reports. Formerly reasonids were reported once per SYSMOD and that contributed to the clutter and the large output. Reasonids to be suppressed are defined in the SUPPHOLD subentry of the active OPTIONS entry.

When change was introduced: SMP/E for z/OS V3R5 (z/OS V1R10).

BYPASS(HOLDSYS) message severity changes

During APPLY and ACCEPT command processing, SMP/E writes messages to identify SYSTEM HOLD conditions that have been bypassed. In prior SMP/E releases, these messages had a severity of Warning and resulted in a minimum overall return code for the command of 4. With SMP/E V3R5, informational messages will be written for bypassed SYSTEM HOLD conditions instead of warning messages. This change to use informational messages will result in a minimum overall return code for the command of 0 rather than 4 when SYSMOD HOLDs are bypassed.

To change APPLY and ACCEPT command processing to write warning messages for bypassed SYSTEM HOLD conditions, use the new COMPAT(WARNBYPASS) execution parameter for program GIMSMP.

When change was introduced: SMP/E for z/OS V3R5 (z/OS V1R10).

SMP/E dialog enhancements

The SYSMOD Management dialog now allows you to bypass all SYSTEM HOLDs with one action. Formerly, to accomplish the same result, you were required to select each unique reason id. In the Order Management dialog, when an ORDER entry is deleted from the global zone, the associated package directory within the SMPNTS is also deleted.

When change was introduced: SMP/E for z/OS V3R5 (z/OS V1R10).

UNIX utility input

SMP/E has been extended to allow definition side deck files residing as UNIX files to be easily included during link-edit operations. Specifically, relative UNIX file names will be allowed as utility input on INCLUDE statements defined in JCLIN link-edit steps, and SMP/E will instruct the binder to include those UNIX files during link-edit operations. Formerly only definition side deck files stored as members of a partitioned data set could be easily included during link-edit operations. This allows developers to easily utilize definition side deck files that reside in UNIX directories.

When change was introduced: SMP/E for z/OS V3R5 (z/OS V1R10).

Support FTP client parameters

SMP/E now allows user specified parameters to be passed to the FTP client program for SMP/E FTP operations during the RECEIVE command and the GIMGTPKG service routine. You can specify the new &ltFTPOPTIONS> tag in the CLIENT or SMPCLNT data set to identify any parameters that SMP/E should pass to the FTP client program. This is most useful when you need to override the FTP.DATA configuration file used by the FTP client program.

When change was introduced: SMP/E for z/OS V3R4 with PTF UO00558.

SMP/E resources

Contact IBM

Browse z/OS


What's new

| V3.6 | V3.5 | V3.4


V3.6 Book | PDF
V3.5 Book | PDF
V3.4 Book | PDF

Guide to fix category values and descriptions
Provides information on category values and how to use them.

Planning and Migration Assistant (PMA)
Helps you identify products currently installed on your system and can provide useful migration planning information.