The management of exception SYSMODs is an important part of SMP/E. SMP/E's ability to manage exception SYSMODs, however, is limited by the quality and timeliness of the HOLDDATA made available to it. To gain the full advantage of this function, you must understand how SMP/E expects the three HOLDDATA input sources to be used and the times during which SMP/E expects them to be used.

The following steps summarize the process for managing exception SYSMOD data:

1. Receive all new products as you get them, or use UCLIN to add the FMIDs of the new products to the global zone. This allows you to process exception SYSMODs for them. Then receive any associated HOLDDATA shipped with the product.
2. Receive HOLDDATA from subsequent CBPDO or ESO tapes in service level order. Remember to do the following:
   • Receive all new products as you get them so you can process exception SYSMODs for them.
   • Receive HOLDDATA as soon as you get your CBPDO or ESO tapes.
3. Before doing preventive service, do the following:
   1. Get the PSP file associated with the last service level for which you processed HOLDDATA, and receive this additional HOLDDATA for your products.
   2. Get the CORPE PSP file. This contains PE PTFs that are available correctively, but are not yet available in a service level.
   3. List and review HOLDDATA for SYSTEM HOLDs and, if possible, handle the required special conditions. Then apply and accept these processed SYSMODs by specifying BYPASS(HOLDSYS) and listing the individual SYSMOD IDs on the SELECT operand. This step helps to make sure that all available service is installed when you do preventive service.

Be sure to review Example of processing HOLDDATA. This example shows why you should follow the procedures defined.