Usage notes

Certain conditions can cause SYSMODs to be considered ineligible for RESTORE processing. These conditions cause SMP/E to terminate processing of the ineligible SYSMODs and issue messages to inform you of the error conditions.
The following conditions cause SMP/E to consider a SYSMOD as ineligible for RESTORE processing:
- An element being restored has a MODID in the element entry on the distribution zone that does not have a corresponding SYSMOD entry on the target zone. This condition can occur if a SYSMOD has been accepted without being applied and, as a result, the distribution library is at a higher function or service level than the target system library.
- The service level of an element being restored is the same in the target library as it is in the distribution library. This condition can occur if a SYSMOD is both applied and accepted.
- A SYSMOD that should have been selected for RESTORE processing was not specified in the SELECT operand list. This condition can occur if one of the SYSMODs specified in the list is part of a RESTORE group that is not fully specified.
- The service level of an element in the distribution library is not the correct one. This can occur if several modifications to the same element are applied at different points in time, without being accepted, and the later modifications are the ones that are selected for RESTORE processing.
  Consider the following example. The distribution zone shows that an element was last replaced on the distribution libraries by PTF UZ00001, but the related target zone indicates that the last replacement to the element on the system was by PTF UZ00004. The element was also modified on the system by PTFs UZ00002 and UZ00003. The SYSMODs on the related target zone and distribution zone are listed in service order:
  TARGET ZONE SYSMODs
  
  DLIB ZONE SYSMODs
  
  UZ00001
  
  UZ00001
  
  UZ00002
  
  UZ00003
  
  UZ00004
  If you specified the following, PTFs UZ00002 and UZ00003 would not be considered part of the RESTORE processing group because they are not dependent on PTF UZ00004.
```
SET      BDY(TGT1)        /* Set to target zone.*/.
RESTORE  S(UZ00004)       /*                    */
         GROUP            /*                    */.
```
  To correct the error, specify:
```
SET      BDY(TGT1)        /* Set to target zone.*/.
RESTORE  S(UZ00002)       /*                    */
         GROUP            /*                    */.
```
  When this condition is detected, SMP/E issues messages to inform you of the SYSMODs that must be restored along with the specified SYSMOD or accepted before that SYSMOD is restored.
- The ineligibility of a member of a RESTORE group terminates processing for the entire group. This can occur both in GROUP and SELECT mode.
- A function SYSMOD containing a ++VER DELETE MCS cannot be restored if any of the specified SYSMODs were actually deleted when the function was applied. (Such a function is eligible for RESTORE processing if none of the specified SYSMODs had ever been applied, and were, therefore, not deleted when the function was installed.)
  Function SYSMODs containing a ++DELETE statement for a load module are not eligible for RESTORE processing.
If a function SYSMOD is terminated for any of these conditions, the RESTORE function is also terminated.
You can avoid certain error conditions that would terminate a SYSMOD by specifying the BYPASS(ID) operand on the RESTORE command. Then, error conditions in the ID validation checking do not cause SYSMOD termination, but are treated as warnings.
The first two conditions described earlier in the first special consideration (SYSMOD ineligibility) can be bypassed by using this option. However, in the first case, the distribution library contains a version of the element that is probably functionally superior to the version being removed. This can cause the executable code in the target system library to be inoperable. In addition, SMP/E updates the element entry on the target zone to reflect the UMID and RMID subentry contents from the element entry on the distribution zone. In this case, the SYSMOD entry might not exist on the target zone, because the BYPASS(APPLYCHECK) operand was probably used on the ACCEPT command; thus, the SYSMOD was never applied to the target system. You should avoid using the BYPASS(ID) option unless it is absolutely necessary.
Utility failures can cause the RESTORE command to fail. For details on handling x37 abends, see the description of the RETRY operand under Operands.
SYSMOD entries on the target zone have the ERROR and RESTORE status indicators set on before the target system libraries are updated. If processing fails during the updating, these indicators remain on and the updating for these entries is not completed. After you determine the cause of the termination, you can process these SYSMODs again by specifying them as operand values of the SELECT operand on the RESTORE command.
RESTORE processing relinks the nucleus, using the last version of modules accepted on the DLIBs.
When a selected SYSMOD contains an element that was deleted from the system by that SYSMOD, RESTORE processing reintroduces that element into the target system using information saved in the SMPSCDS BACKUP entries.
If you do not use SMP/E to recover after a failure and choose the option of restoring your system and the distribution libraries by means of system and DLIB RESTORE tapes, you must ensure that the SMPPTS, SMPCSI, SMPSCDS, SMPMTS, and SMPSTS data sets are also restored to their previous levels.
The exception SYSMOD data stored in the global zone SYSMOD entry is not purged when the SYSMOD is restored. If NOREJECT is not set in the OPTIONS entry that is in effect, the global zone entry is purged of all information except the exception SYSMOD data. (Having NOREJECT set off is the default.)