Step 1.5 – Pre-Upgrade Exception Handling

During this step you must review the exception situations relevant to this ad hoc cycle.

These are divided into two groups:

• items that must be handled before step 1.7 – APPLY the PTFs
• items that require reviewing and planning, but must be handled after step 1.7 – APPLY the PTFs

1. Select Minor Step 5, Pre-Upgrade Exception Handling.

   The following groups of items are displayed:

   • Pre Installation Holds

     Review the list of Pre-APPLY exceptions relevant to your environment. These actions must be taken before running the APPLY the PTFs step.

   • HOLD ERRORs

     This item lists the unresolved PTF in ERROR conditions that were identified and brought to your attention during the RECEIVE and Analyze Target Environment step of this ad hoc cycle.

     The PTF(s) listed are HELD for the ERROR Reason indicated, and the HOLD condition is NOT resolved in this ad hoc cycle. Refer to the description in Handling PE PTFs or to Step 1.3 – RECEIVE and Analyze Target Environment for instructions on how to proceed.

     If you decide to mark this step Complete, and proceed with the APPLY step these conditions will remain unresolved.

   • Post Installation Holds

     Review the list of Post APPLY exceptions relevant to your environment. You are being alerted to these now so that you will be aware of them and can plan for them. These activities must be done after the APPLY the PTF during the Post APPLY Exception Handling step 1.11.

   • User Exits

     The RECEIVE and Analyze Target Environment step identified that new version(s) of exit samples, which are already implemented in your system, will be introduced by this ad hoc cycle.

     This will not affect your system, but you should consider reinstalling these exit(s) in order to take advantage of the updates. At this point you are only alerted to this situation. The actions required to handle this will be described later in the documentation of step 1.8.

     This item lists these user-exits.

   • Regressed Usermods

     The elements listed were previously installed or modified in this environment by a SMP/E USERMOD, and are being replaced in this ad hoc cycle, and so the modification made by the USERMOD is being regressed.

     Before the APPLY implementation, backup the locally modified version.

     Following the APPLY review your modified version of the affected elements together with the new version introduced by the PTF(s) in this ad hoc cycle, and consider re-adapting and re-installing some of these USERMODS.

     Note that there is a step in the 'Post APPLY Exception Handling' step that reminds you regarding this activity.

2. Each item, in both categories, must be selected and reviewed in order to continue with the ad hoc PTF installation process.
3. Once you have reviewed these, type CONFIRM to acknowledge your awareness of all required preinstallation and postinstallation activities and to assume responsibility for the SMP/E APPLY BYPASS options required to continue.

   When there are items in HOLD ERRORs, if you decide to confirm and proceed with the APPLY step, the listed errors will remain unresolved.