When you apply maintenance, you typically encounter SMP/E HOLDDATA. We use HOLDDATA to notify your SMP/E system of SYSMODs that have errors or special conditions. We support system and external HOLDDATA.
System HOLDDATA indicates data that is an in-stream part of the SYSMOD, informing you of special conditions. The following reasons are used with SYSTEM HOLDDATA for your product.
- ActionIndicates that you must perform special processing before or after you apply this SYSMOD.
- AOAffects automated operations. It changes the message identifier or the displacement of a field inside the message.
- DB2BINDIndicates that DBRMs have changed and packages must be rebound.
- DDDEFIndicates that data sets and DDDEFs are being added or modified.
- DELETEDeletes the SYSMOD load module. You cannot reverse this type of SYSMOD with the SMP/E RESTORE command.
- DEPIndicates a dependency for this SYSMOD that you must externally verify.
- DOCIndicates a documentation change with this SYSMOD.
- DOWNLDIndicates that some or all the elements that this SYSMOD delivers are to be downloaded to a workstation.
- DYNACTDescribes the steps to dynamically activate this fix without performing an IPL.
- ECIndicates that this SYSMOD requires a hardware engineering change. An EC hold SYSMOD usually does not affect the product unless the EC is present on the hardware device.
- ENHIntroduces a small programming enhancement. The hold contains the instructions to implement the enhancement. If no action is required to implement the enhancement, give a summary of the enhancement.
- EXITIndicates that changes delivered by this SYSMOD require reassembly of user exits.
- EXRFIndicates that the SYSMOD must be installed in both the Active and Alternate Extended Recovery Facility Systems.
- IPLIndicates that an IPL is required for this SYSMOD to take effect. This option is used only when there is no alternative for dynamic activation.
- MSGSKELIndicates that the SYSMOD contains internationalized message versions that must be run through the message compiler for each language.
- MULTSYSApply this SYSMOD to multiple systems for pre-conditioning, coexistence, or exploitation.
- RESTARTIndicates that after applying this SYSMOD, the site must perform a special restart as opposed to a routine restart.
- SQLBINDIndicates that a bind is required for a database system other than DB2.
External HOLDDATA is not part of the PTF. The HOLDDATA resides in a separate file and contains both error and FIXCAT HOLDDATA. The error HOLDDATA is used for SYSMODs that have been distributed and later are discovered to cause problems. The FIXCAT HOLDDATA helps identify maintenance that is required to support a particular hardware device, software, or function.
Download the external HOLDDATA from Broadcom Support to a DASD file, and allocate the file to the SMPHOLD DD statement. To take care of the external HOLDDATA, receive it into your SMP/E environment. SMP/E receives the HOLDDATA from Broadcom-supplied jobs.
You can find JCL to download the external HOLDDATA in your SAMPJCL member. Open
<hlq>7RECH in an edit session and execute the
<hlq>SEDIT macro on the command line. Then, submit the JCL.
If a SYSMOD has unresolved error HOLDDATA, SMP/E does not install it unless you add a bypass to your APPLY command. You can bypass error HOLDDATA in situations that are not applicable to you. Error HOLDDATA that is not applicable to you can include a problem that happens only with a hardware device that you do not have or in a product feature that you do not use.
When Broadcom publishes a SYSMOD that resolves the error HOLDDATA, the resolving SYSMOD supersedes the error HOLDDATA. This action lets you apply the original SYSMOD with the fixing SYSMOD.
The only manual task is running a REPORT ERRSYSMODS. This report identifies the following:
- Any held SYSMODs already applied to your system
- Any resolving SYSMODs that are in RECEIVE status
Broadcom provides FIXCAT HOLDDATA to help identify maintenance that is required to support a particular hardware device, software, or function. Fix categories are supplied as SMP/E FIXCAT HOLDDATA statements. Each FIXCAT HOLDDATA statement associates an APAR and its related fixing PTF to one or more fix categories.