Updating target libraries: APPLY

When SMP/E applies a SYSMOD, SMP/E checks to see if that SYSMOD is currently in exception SYSMOD status by seeing if there are any HOLD reason ID subentries in the global zone SYSMOD entry. If so, SMP/E makes sure each reason ID is resolved before allowing the SYSMOD to be installed.

For an error reason ID to be resolved, at least one of the following conditions must be met:

The reason ID must be superseded by another SYSMOD being installed.
The reason ID must already exist as a SYSMOD entry in the target zone.
You must specify BYPASS(HOLDERROR) on the APPLY command to show that you are aware that an unresolved exception SYSMOD is being installed.
If there is a HOLD CLASS associated with the reason ID, you can specify BYPASS(HOLDCLASS) on APPLY to indicate that you are using an alternative way to resolve the reason ID.
For more information about the BYPASS operand, see the APPLY command section in i SMP/E for z/OS Commands.

Internal holds are considered resolved if any of the following conditions are met:

The SYSMOD ID specified on the ++HOLD defining the exception is found as a SYSMOD entry in the target zone
The SYSMOD ID specified on the ++HOLD defining the exception is being superseded by a SYSMOD being applied concurrently
The applicable BYPASS operand is specified.

You can resolve external system and user reason IDs by specifying BYPASS(HOLDSYSTEM) or BYPASS(HOLDUSER) on the APPLY command. If there is a HOLD CLASS associated with the reason ID, you can specify BYPASS(HOLDCLASS) on APPLY to indicate that you are using an alternative way to resolve the reason ID.

If you choose to resolve a reason ID by using the BYPASS operand, you must do any required processing at the appropriate time. Otherwise, errors related to the undone processing may occur, even though the reason ID was considered resolved.

Note: You may use the ++RELEASE statement for user category reason IDs if you want to unconditionally release the SYSMOD for all systems. Remember that, unlike BYPASS, ++RELEASE actually deletes the ++HOLD statement. If you plan to use the user category ++HOLD statement, see SMP/E for z/OS Reference for more information about the naming conventions for reason IDs.

If all reason IDs are resolved, SMP/E allows the SYSMOD to be applied. If any remain unresolved, SMP/E prevents the SYSMOD, and any other SYSMODs dependent on this one, from being installed.

SMP/E leaves the reason IDs in the global zone SYSMOD entry when the SYSMOD is applied, so if the SYSMOD is applied on another system later, the same checking is done on that system. If the information had been deleted during the first APPLY, SMP/E would not recognize the problem when the SYSMOD is applied to subsequent systems. Therefore, the ++RELEASE statement should not be used to install an exception SYSMOD with an unresolved reason ID. The appropriate BYPASS operand should be used instead.

In summary, SMP/E ensures that no known problems are introduced into your system by managing those problems at the level of the individual problem, rather than the SYSMOD level. It is, therefore, important that SMP/E have the most current information about exception SYSMODs. For more information about the importance of having current HOLDDATA and what you must do to provide that information to SMP/E, see How to process HOLDDATA.