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 may be used with SYSTEM HOLDDATA for CA Dispatch:
Indicates that you must perform special processing before or after you apply this SYSMOD.
This SYSMOD may affect automated operations. It may change either the message identifier or the displacement of a field inside the message.
Indicates that data sets and DDDEFs are being added or modified.
Deletes the SYSMOD load module. You cannot reverse this type of SYSMOD with the SMP/E RESTORE command.
Indicates a dependency for this SYSMOD that you must externally verify.
Indicates a documentation change with this SYSMOD.
Describes the steps to dynamically activate this fix without performing an IPL.
Indicates 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.
This SYSMOD introduces a small programming enhancement. The hold contains the instructions to implement the enhancement. If no action is needed to implement the enhancement, give a summary of the enhancement.
Changes delivered by this sysmod may require reassembly of user exits.
Indicates that the sysmod must be installed in both the Active and Alternate Extended Recovery Facility Systems.
Indicates that an IPL is required for this SYSMOD to take effect. This is used only when there is no alternative for dynamic activation.
Indicates that the sysmod contains internationalized message versions which must be run through the message compiler for each language.
Apply this sysmod to multiple systems for either pre-conditioning, coexistence, or exploitation.
Indicates that after applying this SYSMOD, the site must perform a special restart as opposed to a routine restart.
Indicates that a bind is required for a database system other than DB2.
Some or all of the elements delivered by this sysmod are to be downloaded to a workstation.
Code a bypass operand on your APPLY command to install SYSMODs that have internal holds. Only code the bypass operand after you have performed the required action, or if you are performing the action after the APPLY, if that is appropriate.
External HOLDDATA is not part of the PTF. It resides in a separate file. It is commonly used for SYSMODs that have been distributed and later are discovered to cause problems.
Download the external HOLDDATA from CA 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 CA supplied jobs.
If a SYSMOD has an unresolved hold error, SMP/E does not install it unless you add a bypass to your APPLY command. You can bypass an error hold in situations that are not applicable to you. Error holds that are 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 CA publishes a SYSMOD that resolves the hold, the resolving SYSMOD supersedes the hold error. This action lets you apply the original SYSMOD in conjunction with the fixing SYSMOD.
A special HOLDDATA class called ERREL exists. We have determined that the problem fixed by the SYSMOD is more important than the one that it causes. We recommend that you apply these SYSMODs.
The only manual task is running a REPORT ERRSYSMODS. This report identifies the following:
SMP/E identifies the SYSMOD to apply to correct the situation.
|
Copyright © 2011 CA.
All rights reserved.
|
|